Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkills › Authors › Amey-Thakur › Page 12

Amey-Thakur

@Amey-Thakur on GitHub →

733 Claude Code skills authored by Amey-Thakur.

updated 2026-11-15 · showing 661–720 of 733 by quality score

Average Pro QualityScore: 64.1/100

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

Move user-facing text out of code into catalogs with stable keys and context, so translation becomes possible without touching logic.
Handle cookies and similar storage so non-essential ones only load after consent and the banner reflects reality.
Structure game loops with fixed-timestep simulation, interpolated rendering, and spiral-of-death protection.
Have an agent produce a plan before implementing, and review it as the cheapest intervention point in the work. Use before any non-trivial agent task.
Plan scalability from a load model and bottleneck math, designing for realistic growth without premature over-engineering.
Operate as a principal architect who owns the boundaries between systems, curates the technology set, and spends veto power sparingly.
Provide filters that narrow results honestly, with counts that reflect what is actually available and a clear way back out.
Stop trusting wall clocks for ordering and expiry across machines; use logical clocks and single-writer timestamps.
End a project deliberately, with handover, documentation, and a decision about what happens to what was built. Use when a project reaches its goal or is being stopped.
Minimize, classify, mask, and expire personal data so any leak or legal request reaches as little of it as possible.
Operate as a product data scientist who frames falsifiable hypotheses, analyzes experiments, and reports results without flattering the launch.
Get output in exactly the structure downstream code expects, using schemas, examples, and validation rather than hope.
Turn raw sensor readings into trustworthy data with correct sampling, filtering, calibration, and timestamped batching.
Write emails that get read and acted on: one clear purpose, the ask up front, and only what the reader needs.
Capture the current output of untested legacy code as a recorded baseline so a refactor can prove it changed nothing.
Support the recurring people function with agents that maintain onboarding paths, keep policy documents current, prepare review inputs, and flag gaps, while every human decision…
Review model errors by hand, discover failing slices, and decide whether data or model fixes pay more.
Configure automated dependency and vulnerability scanning at a cadence people will actually act on. Use when dependencies drift or vulnerabilities go unnoticed.
Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.
Run user interviews that surface past behavior instead of polite predictions, recruited and synthesized honestly. Use when gathering qualitative evidence for product decisions.
Write TypeScript generics that infer well and stay readable, and know when a generic is not worth it.
Improve LCP, CLS, and INP by measuring field data, tracing each metric to its specific cause, and applying the fixes known to move that number.
Run a lab of researcher agents that search in parallel, verify sources independently, and synthesize a cited answer.
Build lazy pipelines with generators and itertools, trading materialized lists for constant memory, and know when eager evaluation is the right call.
Implement OAuth 2.0 and OpenID Connect flows that bind the request end to end with PKCE, state, and exact redirect allowlists.
Define what a project includes, excludes, and depends on before work starts, so scope disagreements surface early. Use when starting a project or when a project keeps growing.
Trust your cross-validation over the public leaderboard, avoid overfitting it, and select final submissions wisely.
Write unit tests that document behavior through explicit arrange-act-assert phases and a single assertion of intent.
Connect MCP servers into an application with lifecycle management, capability negotiation, and graceful degradation when a server is unavailable.
Use JSON Web Tokens safely by pinning the algorithm, keeping lifetimes short, and pairing them with a revocation path.
Produce preview images for files of every type, consistently sized and generated without blocking the user. Use when a file list or gallery needs visual previews.
Version and share seed datasets so they stay small, realistic, and reproducible across a team. Use when tests or local environments depend on fixture data that is drifting,…
Store, compare, and bucket timestamps with explicit time zones so reports do not drift by a day and ranges do not miss rows.
Report progress in a form that surfaces problems early and lets a reader act, rather than reassuring. Use when reporting to sponsors or across teams.
Use when designing Internal Developer Platforms (IDPs), building platform teams, or improving developer experience.
Run retention as a standing function with agents that watch usage signals, spot churn risk early, prepare account reviews, and hand humans a specific reason to reach out.
Pair every generating agent with an independent verifier whose only job is to refute the output, so plausible-but-wrong work is caught before it ships.
Translate company objectives into desk-level goals and weekly work, keeping the line from a task to the objective visible.
Size functions to one clear job, extracting when they blur and leaving them long when the logic is linear. Use when a function grows hard to name or scan.
Pair a product-manager agent with engineer agents through spec, pushback, scope negotiation, and acceptance so the build matches intent.
Decide between patching upstream, forking, and vendoring a dependency, and carry the ongoing cost knowingly.
Choose which browsers, versions, and devices to test from real usage data instead of habit or a vendor's full grid.
Apply a code of conduct consistently, with a reporting path, proportionate responses, and records, so it protects people rather than decorating the repository.
Understand how text becomes tokens, and why token boundaries explain model behaviour on numbers, code, and non-English text.
Use formatting rules to surface exceptions and patterns automatically, without turning the sheet into a colour chart. Use when readers need to spot outliers or status at a glance.
Explain a technical idea by starting from what the learner knows, one concept at a time, with a concrete example before the abstraction.
Protect a mobile app by storing secrets in the platform keystore, pinning certificates only where rotation is controlled, and treating obfuscation as delay rather than defense.
Coalesce a flood of small operations into fewer larger ones with batch windows, debounce, or throttle, chosen by whether you need the last event or a steady rate.
Document chunking strategies for RAG systems. Use when implementing document processing pipelines to determine optimal chunking approaches based on document type and retrieval…
Patterns and strategies for cache invalidation - one of the two hardest problems in computer science.
Match data to object, block, or file storage tiers by access pattern, consistency, and cost per operation.
Pass App Store and Play review on the first attempt and recover fast from rejections. Use when preparing a mobile submission, writing store metadata, or responding to a review…
Keep TODO comments actionable by requiring an owner, a ticket, and an expiry, or deleting them. Use when writing, reviewing, or sweeping in-code TODO, FIXME, and HACK markers.
Split services along business capabilities with clear data ownership, avoiding the distributed monolith.
Read code metrics as smoke that points at where to look, not as verdicts that rank code good or bad. Use when triaging a large codebase for refactoring targets or reviewing…
Model game objects as entities with data components processed by systems, and know when ECS complexity pays.
Reason about rounding, precision limits, and comparison in floating point so numerical results are predictable.
Run a performance calibration meeting so ratings across a group rest on comparable evidence and a consistent bar, not one manager's advocacy.
Python performance profiling and optimization: bottleneck detection, memory tuning, benchmarking
Run a security audit as agents that map the attack surface, review each surface in parallel, skeptic-test every finding, and assemble one report.
Search all 733 skills by Amey-Thakur →