All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Supply Chain SecurityProtect a project and its users from compromised dependencies, publishing credentials, and build pipelines. Use when publishing packages or auditing what your build actually trusts.Votes: 0GitHub stars: 7
- Vulnerability DisclosureReceive, triage, fix, and announce security reports on a coordinated timeline that protects users. Use when running a project that could have security issues, or when you receive a report.Votes: 0GitHub stars: 7
- Failed Payment RecoveryRecover revenue from failed recurring charges with retries, clear notice, and a graceful path back, without harassing customers. Use when involuntary churn from card failures is material.Votes: 0GitHub stars: 7
- Invoicing And ReceiptsProduce invoices and receipts that are accurate, immutable, and contain what tax authorities and customers require. Use when billing businesses or operating where invoices are legally regulated.Votes: 0GitHub stars: 7
- Payment IdempotencyMake payment operations safe to retry so a network timeout never charges a customer twice. Use when calling a payment API, processing webhooks, or building any money-moving endpoint.Votes: 0GitHub stars: 7
- Payment IntegrationIntegrate a payment provider so charges are authorised, confirmed, and recorded correctly even when the customer closes the tab. Use when adding checkout or moving to a new payment provider.Votes: 0GitHub stars: 7
- Payment ReconciliationMatch provider settlements against your own records so every charge, fee, refund, and payout is accounted for. Use when closing books, chasing a discrepancy, or building financial reporting.Votes: 0GitHub stars: 7
- Pci Scope ReductionKeep card data out of your systems so compliance obligations stay minimal, and know what remains in scope when it cannot. Use when handling card payments or preparing for a compliance assessment.Votes: 0GitHub stars: 7
- Pricing Change MigrationChange prices or plan structure without breaking trust or billing, deciding who moves, when, and with what notice. Use when raising prices, restructuring plans, or retiring a legacy tier.Votes: 0GitHub stars: 7
- Refunds And DisputesHandle refunds, chargebacks, and disputes with evidence, deadlines, and a policy applied consistently. Use when building refund flows or responding to a chargeback.Votes: 0GitHub stars: 7
- Revenue Recognition BasicsUnderstand why cash collected is not revenue earned, and record deferred revenue so financial reporting reflects delivery. Use when building billing data models or reporting on a subscription business.Votes: 0GitHub stars: 7
- Subscription BillingModel recurring plans, cycles, upgrades, and cancellations so what a customer is charged always matches what they agreed to. Use when building or changing recurring billing.Votes: 0GitHub stars: 7
- Tax CalculationDetermine, apply, and record sales tax or VAT correctly by jurisdiction, product type, and customer status. Use when selling across borders or when tax handling is currently a flat assumption.Votes: 0GitHub stars: 7
- Usage Based MeteringMeter consumption accurately enough to bill on it, with reconciliation, limits, and transparency the customer can verify. Use when charging by usage rather than a flat subscription.Votes: 0GitHub stars: 7
- Algorithmic OptimizationReplace a hot algorithm with one of better complexity, a fitter data structure, or memoized results instead of micro-tuning the slow one. Use when a profiler points at a function whose cost is inherent to its approach, not to constant-factor waste.Votes: 0GitHub stars: 7
- Async Io PatternsStructure async code so the event loop stays free, slow producers apply backpressure, and blocking calls never stall unrelated work. Use when writing or debugging async IO and throughput is low, latency is spiky, or the loop appears to hang.Votes: 0GitHub stars: 7
- Batching And DebouncingCoalesce 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. Use when high-frequency triggers each do expensive work: per-keystroke queries, per-event writes, per-scroll handlers.Votes: 0GitHub stars: 7
- Benchmark DesignWrite benchmarks that do not lie, controlling warmup, isolation, and statistics so the number reflects the code and not the environment. Use when comparing implementations, defending a performance claim, or a microbenchmark result looks too good.Votes: 0GitHub stars: 7
- Big O In PracticeApply complexity analysis where input size actually makes it decide performance, and ignore it where constant factors dominate. Use when choosing an algorithm or data structure and you need to know whether asymptotic cost or the real constant is what bites.Votes: 0GitHub stars: 7
- Bundle SizeShrink JavaScript bundles by analyzing what ships, enabling real tree shaking, splitting heavy code, and putting the dependency list on a diet. Use when the initial JS payload is large, slow to parse, or growing unchecked.Votes: 0GitHub stars: 7
- Cache InvalidationKeep cached data correct as the source changes using write-through, event-driven eviction, and versioned keys. Use when a cache exists and stale reads are a risk, or when users report seeing old data after a write.Votes: 0GitHub stars: 7
- Caching StrategyDecide what to cache and where by choosing layers, key shapes, and TTLs against the read pattern and freshness need. Use when reads are hot and repeated and you are deciding whether and where to add a cache before writing invalidation code.Votes: 0GitHub stars: 7
- Cdn StrategyPush work to the edge so requests never touch your origin, using cache headers, invalidation, and origin shielding. Use when origin load is high, global latency is uneven, or a CDN sits in front of your app but barely caches.Votes: 0GitHub stars: 7
- Compression TradeoffsChoose a compression codec and level by weighing size reduction against CPU cost, and place compression where the bytes are actually scarce. Use when deciding whether and how to compress payloads, logs, or stored data, or when compression is burning CPU for little gain.Votes: 0GitHub stars: 7
- Concurrency TuningSize worker pools, queue depths, and batch widths against the real bottleneck so parallelism adds throughput instead of contention. Use when a parallel job stops scaling, saturates a resource, or spends more time coordinating than working.Votes: 0GitHub stars: 7
- Connection PoolingSize connection pools from throughput and latency math, then monitor for saturation and set timeout policy so a slow dependency fails fast instead of hanging. Use when a service exhausts database connections, requests queue for a connection, or pool size was picked by guess.Votes: 0GitHub stars: 7
- Cpu OptimizationSpeed up a CPU-bound hot path by fixing its algorithm and memory access first, then applying micro-optimization only where the profiler still points. Use when a function dominates CPU time and you need it faster without changing what it computes.Votes: 0GitHub stars: 7
- Font LoadingLoad web fonts without layout shift by subsetting the file, setting font-display, preloading first-paint weights, and matching fallback metrics. Use when custom fonts cause invisible text, a flash of restyle, or a CLS spike.Votes: 0GitHub stars: 7
- Gc TuningCut garbage-collection pauses and overhead by lowering allocation rate, sizing the heap, and reading pause logs before touching a flag. Use when a managed-runtime service shows latency spikes, high CPU in GC, or out-of-memory errors under load.Votes: 0GitHub stars: 7
- Http CachingUse HTTP caching correctly with etags, max-age, and stale-while-revalidate so clients and proxies reuse responses without serving stale data. Use when responses lack cache headers, a bad deploy served stale content, or revalidation traffic is heavy.Votes: 0GitHub stars: 7
- Image OptimizationServe right-sized images by encoding modern formats, generating responsive srcset widths, and deferring offscreen decode while prioritizing the hero. Use when images are the heaviest bytes on a page or the LCP element loads slowly.Votes: 0GitHub stars: 7
- Io OptimizationReduce input/output cost by cutting round trips, moving fewer bytes, and turning random access into sequential access. Use when a workload is IO-bound: disk, network, or syscall overhead dominates while the CPU sits idle.Votes: 0GitHub stars: 7
- Lazy LoadingDefer expensive work until the moment it is actually needed, so startup stays fast and unused paths cost nothing. Use when initialization is slow, a page ships code it never runs, or a list renders far more rows than the screen shows.Votes: 0GitHub stars: 7
- Materialized ViewsPrecompute expensive read queries into materialized views and pick a refresh strategy that fits a stated staleness budget. Use when an aggregate or join is read far more than the underlying data changes and recomputing it per request is too slow.Votes: 0GitHub stars: 7
- Memory OptimizationCut a program's memory footprint by fixing data layout, reusing allocations, and streaming input instead of buffering it whole. Use when a process is killed by the OOM killer, garbage collection dominates the profile, or heap growth tracks input size.Votes: 0GitHub stars: 7
- N Plus One QueriesFind and eliminate N+1 database access where one query per row replaces one query for the set, using eager loading, batching, or a dataloader. Use when a list endpoint is slow, query counts scale with result size, or an ORM lazy-loads inside a loop.Votes: 0GitHub stars: 7
- Pagination PerformancePaginate large result sets so page cost stays constant by using keyset (cursor) pagination instead of OFFSET, with a stable, encoded cursor. Use when deep pages get slow, an infinite scroll drifts or duplicates rows, or OFFSET grows with page depth.Votes: 0GitHub stars: 7
- Performance BudgetsSet numeric performance budgets and enforce them in CI so regressions fail the build instead of reaching users. Use when performance keeps sliding release over release or a team wants to hold a latency or bundle target.Votes: 0GitHub stars: 7
- Performance OptimizationMake code measurably faster by profiling first and fixing the actual bottleneck. Use when something is slow, uses too much memory, or needs to handle more load.Votes: 0GitHub stars: 7
- Serialization PerformanceCut the CPU and bytes spent turning objects into wire or disk format by choosing the right format, reusing schemas and buffers, and avoiding copies. Use when serialization shows up in the profile, payloads are large, or encode/decode latency dominates a hot request path.Votes: 0GitHub stars: 7
- Startup TimeCut startup latency by deferring heavy imports, precompiling ahead of time, and pruning the dependency tree that loads before first useful work. Use when CLI launch, serverless cold start, or dev-loop boot time is too slow.Votes: 0GitHub stars: 7
- Web VitalsImprove LCP, CLS, and INP by measuring field data, tracing each metric to its specific cause, and applying the fixes known to move that number. Use when Core Web Vitals are failing or a page feels slow to load, settle, or respond.Votes: 0GitHub stars: 7
- Build System DesignDesign builds that are fast, reproducible, and cacheable, so developers wait less and CI costs less. Use when builds are slow, flaky, or produce different results locally and in CI.Votes: 0GitHub stars: 7
- Developer Productivity MetricsMeasure the system's throughput and stability rather than individual output, and use the numbers to remove friction. Use when improving engineering effectiveness or justifying platform work.Votes: 0GitHub stars: 7
- Environment ProvisioningCreate development, preview, and staging environments that resemble production closely enough to be useful, and clean them up automatically. Use when environments drift, cost too much, or block testing.Votes: 0GitHub stars: 7
- Golden Path TemplatesProvide starting templates that encode the organisation's defaults so new services are consistent without anyone reading a standards document. Use when new services vary widely in structure and quality.Votes: 0GitHub stars: 7
- Internal Developer PlatformBuild a platform that lets product teams ship without filing tickets, treating the platform as a product with users. Use when infrastructure work is a bottleneck or every team solves the same problems differently.Votes: 0GitHub stars: 7
- Local Development SetupMake a working local environment reachable in minutes from a clean machine, and keep it close to production. Use when onboarding takes days or developers cannot run the system locally.Votes: 0GitHub stars: 7
- Paved Road AdoptionGet teams onto the supported path through incentives and migration support rather than mandates. Use when a better platform exists and teams are not moving to it.Votes: 0GitHub stars: 7
- Platform AbstractionsChoose the level of abstraction a platform exposes so it hides complexity without hiding what teams need to control. Use when designing platform interfaces or when teams keep bypassing them.Votes: 0GitHub stars: 7