[WHAT IT DOES — one sentence, imperative, third-person. Start with a verb: "Manages", "Tracks", "Generates".] Use when [SPECIFIC CONTEXT — what situation calls for this skill, what the user is trying to accomplish]. Trigger on: '[EXACT PHRASE 1]', '[EXACT PHRASE 2]', '[EXACT PHRASE 3]'. Even if the user just says '[CASUAL SHORTHAND]', use this skill. Do NOT use for [ADJACENT DOMAIN that could be confused] — use [other-skill-name] instead.
From tandemnpx claudepluginhub binatrixai/tandem-marketplace --plugin tandemThis skill uses the workspace's default tool permissions.
README.mdevals/evals.jsonreferences/frontmatter-fields.mdEnforces strict TDD workflow: Red (failing test), Green (minimal code), Refactor for features, bugfixes, refactors. Includes examples and verification steps.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
[One paragraph overview: what does this skill do and why does it exist? Write for Claude, not humans — imperative tone, no "you can" language.]
[Optional. Add here only if trigger context doesn't fit in description. Delete this section if redundant with description.]
[Replace with your skill's primary workflow steps. Use numbered lists for sequences, bullets for options. Imperative style: "Extract X. Return Y." not "You should extract X."]
[Add as many sections as needed. When a section grows beyond ~50 lines, move it to references/ and link from here.]