All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- E2e TestingWrite end-to-end tests that earn their cost by covering complete user journeys against stable selectors. Use when protecting a critical path like signup or checkout across the full stack.Votes: 0GitHub stars: 7
- Exploratory TestingRun structured unscripted testing with charters, tours, and timeboxed sessions to find bugs scripted tests never imagined. Use when probing a new or risky feature for problems no one thought to write a test for.Votes: 0GitHub stars: 7
- Fuzz TestingFuzz a parser or protocol handler with a coverage-guided fuzzer, seed the corpus with real inputs, and triage crashes to unique root causes. Use when code consumes untrusted or complex bytes and hand-written cases cannot reach the states that break it.Votes: 0GitHub stars: 7
- Golden MasterCapture the current output of untested legacy code as a recorded baseline so a refactor can prove it changed nothing. Use when about to restructure code whose behavior you must preserve but cannot yet specify.Votes: 0GitHub stars: 7
- Integration TestingTest the seams between modules with real dependencies where they are cheap and containerized ones where they are not. Use when verifying that components wired together honor the contracts unit tests assume in isolation.Votes: 0GitHub stars: 7
- Load TestingSimulate realistic multi-user load with ramp profiles, think time, and pacing, then find where the system saturates. Use when validating capacity or headroom for a service before a launch or expected traffic spike.Votes: 0GitHub stars: 7
- Mocking TimeControl the clock in tests through an injectable time source so "now" is frozen and timezone behavior is explicit. Use when code reads the wall clock and a flaky or time-dependent test needs deterministic results.Votes: 0GitHub stars: 7
- Mutation TestingMeasure how strong a test suite is by mutating the code and checking the tests notice, exposing assertions that never actually fail. Use when coverage is high but you doubt the tests would catch a real regression.Votes: 0GitHub stars: 7
- Pact VerificationVerify a provider against its consumers' recorded pacts in CI so a breaking API change fails before it ships. Use when independently deployed services share an HTTP contract and you want to catch breaks without end-to-end staging.Votes: 0GitHub stars: 7
- Performance TestingBenchmark code so the numbers mean something: warm up, fix inputs, report variance, and gate regressions in CI. Use when measuring the speed of a function or comparing two implementations.Votes: 0GitHub stars: 7
- Property Based TestingGenerate many inputs to test invariants that must hold across a whole domain, and let shrinking reduce failures to a minimal case. Use when a rule should hold for all inputs, not just the few examples you would think to write.Votes: 0GitHub stars: 7
- Regression TestsPin every fixed bug with a test that fails before the fix and passes after, kept beside the code it guards. Use when closing a bug so the same defect cannot return silently through a later refactor or merge.Votes: 0GitHub stars: 7
- Seed Data ManagementVersion 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, ballooning, or diverging between developers.Votes: 0GitHub stars: 7
- Smoke TestsDefine the short, stable suite of critical-path checks that runs after every deploy and blocks promotion the instant it fails. Use when a deploy has no fast gate and breakage is found by users instead of the pipeline.Votes: 0GitHub stars: 7
- Snapshot TestingUse snapshot tests for serialized output only, with disciplined review of every diff and hard limits on snapshot size. Use when pinning stable rendered output like markup or an API response shape.Votes: 0GitHub stars: 7
- Tdd RhythmRun red-green-refactor honestly with the smallest failing test first, refusing test-after backfill dressed up as TDD. Use when building code with a clear behavioral spec and you want the tests to drive the design.Votes: 0GitHub stars: 7
- Test Data BuildersConstruct test objects through builders and factories with valid defaults so each test states only the fields it cares about. Use when shared fixture files couple unrelated tests and drift as the schema grows.Votes: 0GitHub stars: 7
- Test DoublesChoose stubs, fakes, and mocks deliberately and default to verifying state over interaction so tests survive refactors. Use when a test needs to stand in for a slow, external, or nondeterministic dependency.Votes: 0GitHub stars: 7
- Test Environment ParityClose the gaps between test and production by matching versions, data shape, and configuration paths so a passing suite actually predicts prod behavior. Use when tests are green but production breaks in ways staging never showed.Votes: 0GitHub stars: 7
- Test Flakiness BudgetCap flaky tests with a measured budget, quarantine them off the merge gate, and burn them down under named owners and deadlines. Use when re-runs are how the team gets green and no one owns the flakes.Votes: 0GitHub stars: 7
- Test IsolationMake tests order-independent by resetting state, banning shared globals, and giving each worker its own resources. Use when tests pass in one order but fail when reordered, sharded, or run in parallel.Votes: 0GitHub stars: 7
- Test MaintenanceRefactor test code with the same care as production: extract helpers, remove duplication, and delete tests that no longer earn their place. Use when the test suite has become slow to change, repetitive, or full of tests nobody trusts.Votes: 0GitHub stars: 7
- Test NamingName tests as full behavior sentences so the suite reads as a specification of what the system guarantees. Use when naming a new test or renaming vague tests like test1 or testWorks.Votes: 0GitHub stars: 7
- Test Pyramid AuditRebalance a top-heavy test suite toward fast unit tests without dropping the coverage the slow tests provide. Use when end-to-end tests dominate the suite and CI is slow, flaky, or expensive to run.Votes: 0GitHub stars: 7
- Test ReviewReview tests with the same rigor as production code, checking that assertions truly constrain behavior, that error and edge cases exist, and that no safety was quietly deleted. Use when reviewing a pull request that adds, changes, or removes tests.Votes: 0GitHub stars: 7
- Test SpeedKeep the suite fast enough to run on every change by measuring the slow tests, shaping the pyramid, cutting IO from the fast tier, and sharding. Use when the suite is slow enough that developers skip it or batch changes to avoid the wait.Votes: 0GitHub stars: 7
- Test TaggingTag tests by speed and scope so CI can run the right slice at the right time. Use when the suite is one undifferentiated blob and you need fast feedback on pull requests without dropping slow coverage.Votes: 0GitHub stars: 7
- Testing In ProductionVerify changes against real traffic without risking users, using canaries, shadow traffic, and feature gates with automatic rollback. Use when a behavior cannot be trusted from staging alone and needs production load or data to prove out.Votes: 0GitHub stars: 7
- Testing StrategyDecide what to test, at which level, and what to skip, so tests catch real regressions without freezing the design. Use when writing tests or planning coverage for a change.Votes: 0GitHub stars: 7
- Unit Test DesignWrite unit tests that document behavior through explicit arrange-act-assert phases and a single assertion of intent. Use when writing or repairing a unit test that has grown hard to read.Votes: 0GitHub stars: 7
- Visual Regression TestingCatch unintended UI changes by diffing rendered screenshots against approved baselines with tuned thresholds and flake control. Use when protecting a component or page from visual drift across code changes.Votes: 0GitHub stars: 7
- Empty And Error StatesDesign the empty, loading, error, and edge states that most designs skip but users constantly hit. Use when designing any screen that can be empty, loading, or fail, which is nearly all of them.Votes: 0GitHub stars: 7
- Information ArchitectureOrganize a product's content and navigation around how users think, so they can find things and know where they are. Use when structuring an app's navigation, a site's sections, or a feature's information.Votes: 0GitHub stars: 7
- Interaction DesignDesign how users act and the interface responds: affordances, feedback, states, and forgiving flows. Use when designing controls, flows, and interactive behavior, or fixing an interface that confuses or frustrates.Votes: 0GitHub stars: 7
- Onboarding UxDesign a first-run experience that gets users to their first success fast, teaching by doing rather than by tour. Use when designing signup, first-run, or activation flows for a product.Votes: 0GitHub stars: 7
- Usability HeuristicsEvaluate and design interfaces against established usability heuristics to catch the common, predictable UX failures. Use when reviewing a UI for problems or designing one to avoid them.Votes: 0GitHub stars: 7
- Usability TestingWatch real users attempt real tasks to find where a design fails, with few participants and honest tasks. Use when validating a design or diagnosing why users struggle, before or after building.Votes: 0GitHub stars: 7
- User FlowsMap and design the paths a user takes to complete a goal, minimizing steps and dead ends. Use when designing a multi-step task, checkout, signup, or any flow, or diagnosing where users drop off.Votes: 0GitHub stars: 7
- Ux WritingWrite the words inside an interface (labels, buttons, errors, empty states, microcopy) so they are clear, concise, and helpful. Use when writing or reviewing any text a user reads while using a product.Votes: 0GitHub stars: 7
- Visual HierarchyGuide the eye to what matters through size, contrast, spacing, and grouping so a screen reads at a glance. Use when a design feels cluttered, flat, or hard to scan, or when laying out any interface or page.Votes: 0GitHub stars: 7
- Wireframing PrototypingUse low- and high-fidelity wireframes and prototypes to test ideas cheaply before building. Use when exploring a design, aligning stakeholders, or validating a flow before committing engineering time.Votes: 0GitHub stars: 7
- Audience AdaptationAdapt what you write, how much, and how you frame it to the specific reader's knowledge, needs, and stakes. Use when the same content must reach different audiences, or when writing is missing its reader.Votes: 0GitHub stars: 7
- Clear WritingWrite so the reader understands on the first pass: plain words, concrete nouns, one idea per sentence. Use when drafting or editing any prose that must be understood without effort.Votes: 0GitHub stars: 7
- Concise WritingCut writing to its essential words so every one earns its place, without losing meaning or voice. Use when a piece is too long, dense, or padded, or whenever brevity respects the reader's time.Votes: 0GitHub stars: 7
- Editing And RevisionTurn a rough draft into finished writing through structured revision passes: cut, clarify, then polish. Use when improving your own or others' writing after the first draft exists.Votes: 0GitHub stars: 7
- Narrative CraftTell a story that holds attention and makes a point, through character, tension, and concrete scenes. Use when using storytelling in writing: an essay, a talk, a case study, a brand story, a personal account.Votes: 0GitHub stars: 7
- Persuasive WritingMake a case in writing that changes minds through a clear claim, real evidence, and honest handling of objections. Use when writing to convince: a proposal, a pitch, an argument, an opinion piece.Votes: 0GitHub stars: 7
- Strong OpeningsWrite openings that earn the next sentence: hook the reader, promise value, and get to the point fast. Use when a piece's beginning is slow, generic, or buries what matters.Votes: 0GitHub stars: 7
- Structure And FlowOrganize writing so the reader is carried from point to point without friction: logical order, transitions, and signposting. Use when a piece feels disorganized, jumpy, or hard to follow despite clear sentences.Votes: 0GitHub stars: 7
- Voice And ToneDevelop a consistent writing voice and adjust tone to the context without sounding generic or robotic. Use when writing needs personality, a brand voice, or a register matched to the situation.Votes: 0GitHub stars: 7