Test
Holds the two testing disciplines this package learned by paying for them, and points at the rest. Use when writing or changing a test under tests/, touching a golden snapshot, or fixing a user-reported bug. Do NOT use for tier conventions, the vitest projects, doubles, fixtures or how to run a suite — those live in `aidd_docs/memory/testing.md`. Do NOT use for writing production code — use the context skill that owns the concept (`tools`, `translate`, `distribution`, `framework`).
Install
/plugin marketplace add ai-driven-dev/frameworkThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add ai-driven-dev/framework --skill testgit clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p ~/.claude/skills
cp -r /tmp/framework/cli/.claude/skills/test ~/.claude/skills/testPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test The tiers, the four vitest projects, the doubles, the fixtures and the run commands are in `aidd_docs/memory/testing.md`; read that first and do not restate it here. This skill exists for the two failure modes that cost this package a shipped bug each, and that a convention page states as a rule without saying how to satisfy it. ## Read before you touch one - `references/golden-machine-independence.md` — a golden that snapshots a value derived from an absolute path passes locally and fails on another machine. The rule is in `testing.md`; this is the symptom, the root cause and the two fixes, plus the proof to run afterwards. - `references/bug-empirical-reproduction.md` — a fix for a user-reported bug is not done until the reported scenario has been reproduced end to end against the real binary, before and after. Green unit and E2E tests have shipped an unfixed bug here; the transcript format is what catches that. ## The order Write the failing test first and watch it fail for the reason its name gives — a bug fix starts there, never with the production edit. That discipline is stated for the whole repository in `aidd_docs/memory/coding-assertions.md`.
Details
- Skill name
test- Repository
- ai-driven-dev/framework
- Path
cli/.claude/skills/test/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Test skill do?
Holds the two testing disciplines this package learned by paying for them, and points at the rest. Use when writing or changing a test under tests/, touching a golden snapshot, or fixing a user-reported bug. Do NOT use for tier conventions, the vitest projects, doubles, fixtures or how to run a suite — those live in `aidd_docs/memory/testing.md`. Do NOT use for writing production code — use the context skill that owns the concept (`tools`, `translate`, `distribution`, `framework`).
How do I install the Test skill?
Claude Code plugin: /plugin marketplace add ai-driven-dev/framework. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test popular?
It lives in ai-driven-dev/framework, which has 564 GitHub stars and 65 forks.
Related skills
00 Async Dev
564ai-driven-dev/framework
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
00 Init
564ai-driven-dev/framework
Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.
00 Onboard
564ai-driven-dev/framework
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Ue Testing Debugging
468quodsoler/unreal-engine-skills
Use when writing or running Unreal Engine tests, adding logging, or profiling a build. Also use when the user mentions 'UE_LOG', 'log category', 'DEFINE_LOG_CATEGORY', 'UE_LOGFMT', 'verbosity', 'check', 'ensure', 'ensureMsgf', 'verify', 'IMPLEMENT_SIMPLE_AUTOMATION_TEST', 'automation test', 'TEST_CLASS', 'CQTest', 'AFunctionalTest', 'latent command', 'Unreal Insights', 'TRACE_CPUPROFILER_EVENT_SCOPE', 'TRACE_BOOKMARK', 'stat unit', 'SCOPE_CYCLE_COUNTER', 'memreport', 'DrawDebugLine', 'UE_VLOG', 'gameplay debugger', 'ShowDebug', 'console command', 'CVar', or 'why is my frame time bad'. For modu
Grill
593haowjy/creative-writing-skills
Use to stress-test a plan or direction with the human: zoom out to what it is for, then walk down its decision tree, each question with a recommended answer.
Plaid
221BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.