recipe-template
Template for commands that implement a structured recipe: validate preconditions, then execute numbered steps. Fork this and replace the placeholder content. The 'Context Validation Checkpoints' section is the key pattern, forcing Claude to verify preconditions before starting.
What this skill does
# Recipe Command Template > This is a template. Replace all `[placeholder]` content with your specifics. ## When to Use - [Describe the exact situation where this command applies] - [Describe when NOT to use it, with a common misuse case] ## Context Validation Checkpoints Before executing any step, verify all of these are true. If any checkpoint fails, stop and explain why to the user. * [ ] [Precondition 1: e.g., "The target branch exists and is up to date with main"] * [ ] [Precondition 2: e.g., "No uncommitted changes in the affected files"] * [ ] [Precondition 3: e.g., "Required config file exists at path X"] * [ ] [Precondition 4: e.g., "Necessary permissions or credentials are available"] ## Recipe Steps ### Step 1: [Action name] [Clear instructions for this step. Be specific about what to read, what to check, what to write.] Validation: [How Claude verifies this step completed correctly before moving to Step 2] --- ### Step 2: [Action name] [Instructions] Validation: [How to verify] --- ### Step 3: [Action name] [Instructions] Validation: [How to verify] --- ### Step 4: Confirm Completion Summarize what was done: - [Item 1 completed] - [Item 2 completed] - Files modified: [list] - Next action for the user (if any): [instruction] ## Error Handling | Situation | Response | |-----------|----------| | [Error condition 1] | [What to do: retry / stop / ask user] | | [Error condition 2] | [What to do] | | Precondition checkpoint fails | Stop. Explain which checkpoint failed and what the user needs to fix before re-running | ## Arguments If `$ARGUMENTS[0]` was provided: [how to use it] If no argument was provided: [default behavior] --- > The "Context Validation Checkpoints" section is the key pattern from this template. > It forces Claude to verify preconditions explicitly rather than discovering failures mid-execution. > Inspired by recurring patterns in [Packmind commands](https://github.com/packmind/packmind) (Apache 2.0).
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.