From Strata
Captures reusable procedures, workflows, checklists, and recipes as structured markdown files. Useful for documenting onboarding, release runbooks, migration guides, and debugging flows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/strata:procedureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The "how" notes. Distinct from domain (the "what") and decisions (the "why").
The "how" notes. Distinct from domain (the "what") and decisions (the "why"). A procedure tells a future engineer (or future Claude) the sequence of Steps to reproduce something.
What does NOT belong:
/strata:decide/strata:domain/strata:saveUser runs /strata:procedure <title> or you autonomously identify a
Workflow worth capturing. You:
recall(query="<title>", scope="procedural", layer=1).
If a near-duplicate already exists (e.g. "shipping a hotfix" vs "hotfix
release runbook"), extend that one instead of adding a second.cat <<'EOF' | "${CLAUDE_PLUGIN_ROOT}/bin/strata" procedure \
--title "<title>"
# <Title>
## Prerequisites
- ...
## Steps
1. ...
2. ...
## Verify
- ...
## When to use this procedure
<one sentence>
EOF
Lands in <vault>/<repo>/procedural/<slug>.md.
Always: title, prerequisites, numbered steps, verification, applicability. The verification step is what makes it executable, without it, the Procedure is just narrative.
If a step references code, use backticks (OrderAggregate.cs), those get
Verified against the code graph in /strata:review.
npx claudepluginhub gideondk/strata --plugin strataProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.