All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Dashboard BuildingBuild dashboards that answer specific questions at a glance, rather than displaying every available metric. Use when a team needs shared visibility into an ongoing situation.Votes: 0GitHub stars: 7
- Documentation SiteStructure a documentation site so readers find answers by task, with working examples and a maintenance path. Use when documenting a product or library for external users.Votes: 0GitHub stars: 7
- Form DesignDesign forms people complete, with the fewest fields, clear labels, and error handling that helps rather than punishes. Use when collecting any information from users.Votes: 0GitHub stars: 7
- Newsletter ProductionProduce a recurring newsletter with a sustainable format, a clear reason to open, and rendering that survives email clients. Use when publishing regularly to a subscribed audience.Votes: 0GitHub stars: 7
- Pdf GenerationProduce PDFs programmatically with correct fonts, page breaks, and accessibility, from templates that survive content changes. Use when generating invoices, reports, certificates, or statements.Votes: 0GitHub stars: 7
- Print Ready OutputPrepare documents for physical printing with correct colour, bleed, resolution, and fonts, so what prints matches what you designed. Use when producing anything that will be professionally printed.Votes: 0GitHub stars: 7
- Proposal WritingWrite a proposal that states the client's problem, your approach, and the commercial terms clearly enough to be accepted or declined quickly. Use when bidding for work or pitching a project.Votes: 0GitHub stars: 7
- Report WritingWrite a report that leads with findings, supports them with evidence, and states its own limitations. Use when presenting analysis, results, or an investigation in writing.Votes: 0GitHub stars: 7
- Slide Deck CreationBuild a deck that supports a spoken argument, with one idea per slide and visuals that carry meaning. Use when presenting to an audience rather than sending a document.Votes: 0GitHub stars: 7
- Spreadsheet ModelingBuild spreadsheet models that are auditable and hard to break, separating inputs, calculations, and outputs. Use when modelling finances, forecasts, or scenarios.Votes: 0GitHub stars: 7
- Technical DiagramsDraw system, sequence, and flow diagrams that clarify rather than decorate, at a consistent level of abstraction. Use when explaining a system to people who did not build it.Votes: 0GitHub stars: 7
- Website BuildingBuild and ship a small site that loads fast, reads well, and can be updated, choosing the simplest stack that fits. Use when creating a marketing site, portfolio, documentation site, or landing page.Votes: 0GitHub stars: 7
- Artifact VersioningBuild immutable, provenance-tracked artifacts promoted unchanged through environments. Use when designing a build pipeline or fixing "works in staging, breaks in prod" from rebuilt binaries.Votes: 0GitHub stars: 7
- Blue Green DeploymentsDeploy with two swappable environments for instant cutover and rollback, handling database compatibility. Use when zero-downtime releases matter or designing a low-risk deploy mechanism.Votes: 0GitHub stars: 7
- Capacity PlanningForecast load, size headroom, discover scaling limits before they bite, and track cost curves. Use when planning capacity for growth or a known traffic event, or after a saturation incident.Votes: 0GitHub stars: 7
- Ci CdBuild CI/CD pipelines that are fast, trustworthy, and safe to deploy from. Use when creating or fixing continuous integration, delivery workflows, or release automation.Votes: 0GitHub stars: 7
- Config ManagementSeparate config from code and secrets, keep environments at parity, and change config safely. Use when wiring application configuration for deployment or fixing environment-specific bugs and config drift.Votes: 0GitHub stars: 7
- ContainerizationWrite container images and compose setups that are small, reproducible, and safe to run. Use when writing Dockerfiles, docker-compose files, or debugging container behavior.Votes: 0GitHub stars: 7
- Dependency ManagementChoose, add, upgrade, and remove dependencies with the long-term cost in view. Use when adding a library, resolving version conflicts, or auditing a dependency tree.Votes: 0GitHub stars: 7
- Deployment PipelinesDesign deploy pipelines with staged gates, environment promotion, and speed budgets that keep releases safe and frequent. Use when building a CD pipeline or fixing slow, flaky, or unsafe deploys.Votes: 0GitHub stars: 7
- Docker Image OptimizationBuild small, fast, secure container images with layer caching, multi-stage builds, and a minimal base policy. Use when images are bloated, slow to build, or failing security scans.Votes: 0GitHub stars: 7
- Gitops WorkflowManage deployments declaratively from git as the source of truth, with reconciliation, secrets handling, and drift alerts. Use when adopting GitOps or fixing config drift and untracked cluster changes.Votes: 0GitHub stars: 7
- Incident PostmortemWrite a blameless postmortem that finds systemic causes and produces actions that actually prevent recurrence. Use after an outage, data incident, or serious bug reaches users.Votes: 0GitHub stars: 7
- Infrastructure MonitoringMonitor systems with the golden signals and USE method, alerts that page only on user impact, and runbook-linked responses. Use when instrumenting infrastructure or fixing alert fatigue.Votes: 0GitHub stars: 7
- Rollback StrategyDecide rollback versus fix-forward, handle migrations safely, and rehearse rollbacks so they work under pressure. Use when planning deploy safety or during an incident deciding how to recover.Votes: 0GitHub stars: 7
- Runbook WritingWrite runbooks with executable steps, decision points, and per-step verification that a stressed responder can follow. Use when documenting operational procedures or reducing 3am guesswork.Votes: 0GitHub stars: 7
- BackpressureBound every queue and propagate overload upstream so systems degrade by shedding instead of collapsing. Use when designing high-throughput paths or diagnosing latency spirals under load.Votes: 0GitHub stars: 7
- Clock SkewStop trusting wall clocks for ordering and expiry across machines; use logical clocks and single-writer timestamps. Use when timestamps decide ordering, uniqueness, or expiry in a distributed system.Votes: 0GitHub stars: 7
- Consensus BasicsUnderstand what Raft and Paxos actually provide, quorum arithmetic, and when you need consensus at all. Use when deploying replicated coordination systems or deciding whether a problem truly requires consensus.Votes: 0GitHub stars: 7
- Consistency ModelsChoose the weakest consistency model each use case tolerates, from linearizable to eventual. Use when designing replicated data paths or explaining anomalies users report as bugs.Votes: 0GitHub stars: 7
- CqrsSplit read and write models when their shapes genuinely diverge, and manage the sync lag honestly. Use when one data model cannot serve both commands and queries well, or when reviewing an over-engineered CQRS setup.Votes: 0GitHub stars: 7
- Delivery GuaranteesReason honestly about at-most-once, at-least-once, and effectively-once semantics end to end. Use when specifying messaging behavior or auditing where a pipeline can lose or duplicate data.Votes: 0GitHub stars: 7
- Distributed LocksUse leases with fencing tokens for mutual exclusion across machines, or restructure to need no lock at all. Use when serializing distributed work or reviewing lock code that must not double-execute.Votes: 0GitHub stars: 7
- Event SourcingPersist state as an append-only event log with projections and snapshots, and know when the pattern is overkill. Use when audit history is a first-class requirement or evaluating event sourcing against CRUD.Votes: 0GitHub stars: 7
- Idempotent ConsumersMake message consumers safe under at-least-once delivery with natural idempotency or a transactional dedup store. Use when building queue/stream consumers or debugging duplicate side effects.Votes: 0GitHub stars: 7
- Leader ElectionRun one active node with lease-based election, split-brain prevention, and clean handoff. Use when exactly one instance must do a job (scheduler, migrator, singleton consumer) across a fleet.Votes: 0GitHub stars: 7
- Partition ToleranceDecide per operation what happens during a network partition, and design degraded modes that fail safe. Use when planning multi-node or multi-region behavior under network failure.Votes: 0GitHub stars: 7
- Saga PatternCoordinate multi-service transactions as a sequence of local steps with compensations, timeouts, and an observable state machine. Use when a business flow spans services and two-phase commit is not on the table.Votes: 0GitHub stars: 7
- Api Reference DocsProduce API reference docs that blend generation with curation, an example per endpoint, and documented errors. Use when documenting an API or SDK for external or internal consumers.Votes: 0GitHub stars: 7
- Changelog WritingWrite changelogs for humans, grouped by change type, with breaking changes called out and versions dated. Use when maintaining a changelog or replacing raw commit dumps with useful release notes.Votes: 0GitHub stars: 7
- Code DocumentationWrite code comments and API docs that carry what the code cannot say, and nothing it already does. Use when documenting functions, modules, or tricky passages.Votes: 0GitHub stars: 7
- Docs As CodeTreat documentation like code: in the repo, in pull requests, CI-checked, with preview builds. Use when docs drift from reality or the docs workflow is separate from the code workflow.Votes: 0GitHub stars: 7
- Docs Information ArchitectureOrganize documentation with the Diataxis four-quadrant model, navigable structure, and searchability. Use when structuring a docs site or when readers cannot find what they need.Votes: 0GitHub stars: 7
- Docs MaintenanceKeep documentation from rotting through staleness detection, ownership, doc tests, and deliberate deprecation. Use when docs have drifted from reality or no process keeps them current.Votes: 0GitHub stars: 7
- Onboarding DocsWrite onboarding docs that get a new contributor to a verified working setup and a first contribution fast. Use when new joiners struggle to get started or setup instructions keep breaking.Votes: 0GitHub stars: 7
- Readme WritingWrite READMEs that deliver value on the first screen, quickstart before reference, and stay maintainable. Use when creating or fixing a project's front-door documentation.Votes: 0GitHub stars: 7
- Technical WritingWrite documentation, READMEs, and guides that respect the reader's time and answer their actual question. Use when drafting or editing any technical document.Votes: 0GitHub stars: 7
- Tutorial WritingWrite tutorials that take a learner from zero to a working result through tested steps with checkpoints and recovery. Use when creating learning-oriented documentation or onboarding guides.Votes: 0GitHub stars: 7
- Clear EmailsWrite emails that get read and acted on: one clear purpose, the ask up front, and only what the reader needs. Use when writing any email that must be understood and answered without back-and-forth.Votes: 0GitHub stars: 7
- Difficult EmailsWrite the hard emails (bad news, saying no, complaints, corrections) so they are clear, kind, and preserve the relationship. Use when an email must deliver something unwelcome without making it worse.Votes: 0GitHub stars: 7