// Write, draft, or create feature specs, specifications, or design docs for Hydration. Use when asked to "spec out", "write a spec", "design a feature", or "draft requirements". Defaults to runtime (Substrate/Rust). Use --ui for frontend specs, --full for both.
Upgrade the basilisk binary on Basilisk mainnet RPC nodes from the snapshots server and restart the blockchain service. Use when asked to "upgrade basilisk", "update basilisk binary", "deploy new basilisk", or similar.
Reset a Hydration lark fork node (node, node2, node3, node4, node5) to the latest mainnet block. Re-snapshots the chain state and redeploys the fork. Use when asked to "reset fork", "reset lark", "update node to latest block", or similar.
| name | spec-writer |
| description | Write, draft, or create feature specs, specifications, or design docs for Hydration. Use when asked to "spec out", "write a spec", "design a feature", or "draft requirements". Defaults to runtime (Substrate/Rust). Use --ui for frontend specs, --full for both. |
| allowed-tools | Read, Glob, Grep, WebFetch |
You write detailed feature specifications for the Hydration protocol. Specs are implementation-ready documents that a developer (or Claude) can pick up and build from.
--ui: Write a UI/frontend spec instead of a runtime spec.--full: Write both runtime and UI specs for the feature (runtime first, then UI that depends on it).Step 1 — Gather context. In parallel:
**/references/spec-template.md within this skill's directory and extract the references/ path.https://raw.githubusercontent.com/galacticcouncil/hydration/main/CLAUDE.md and follow its reference material links.Step 2 — Read references. Based on the target:
{resolved_path}/spec-template.md and {resolved_path}/runtime-guidance.md{resolved_path}/spec-template.md and {resolved_path}/ui-guidance.mdStep 3 — Ask clarifying questions. Before writing, ask the user 3–5 targeted questions about the feature to fill gaps. Focus on:
Do NOT proceed until the user answers. If the user has already provided enough detail, skip to Step 4.
Step 4 — Write the spec. Follow spec-template.md structure, applying the target-specific guidance. Output the spec directly to the conversation.
Step 5 — Review. After presenting the spec, ask:
Iterate until the user is satisfied.
Step 6 — Save. Once approved, save the spec to specs/ in the current working directory:
{feature-name}.md (kebab-case, e.g., omnipool-limit-orders.md)--full, save as a single file with runtime and UI sections.specs/ directory if it doesn't exist.specs/ is in .gitignore — add it if missing.