cladding-init
Use only when the user explicitly names Cladding and asks to initialize, adopt, or refresh it; never use for an ordinary project…
Boot cladding as an MCP server over stdio. Use only when the user wants to expose cladding's tools, resources, and persona prompts to a separate MCP client. Most users don't run this directly — the plugin's .mcp.json launches it automatically. Activate only when the connected
Claude Code
$ npx -y skills add purpleeddy/cladding --skill serve --agent claude-code
Codex
$ npx skills add purpleeddy/cladding --skill serve -a codex -y
Cursor
$ npx skills add purpleeddy/cladding --skill serve -a cursor -y
Gemini CLI
$ npx skills add purpleeddy/cladding --skill serve -a gemini-cli -y
GitHub Copilot
$ npx skills add purpleeddy/cladding --skill serve -a github-copilot -y
OpenCode
$ npx skills add purpleeddy/cladding --skill serve -a opencode -y
Windsurf
$ npx skills add purpleeddy/cladding --skill serve -a windsurf -y
description: Boot cladding as an MCP server over stdio. Use only when the user wants to expose cladding's tools, resources, and persona prompts to a separate MCP client. Most users don't run this directly — the plugin's .mcp.json launches it automatically. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.
Run `clad serve` from the project root. Boots an MCP server over stdio that exposes:
Registers itself in cladding's sampling context so the host adapters (`generic-mcp`, `claude-code`) route LLM dispatch through `McpSamplingTransport` instead of the Mock fallback.
clad serve --cwd /path/to/project
**Most users don't run this directly.** Cladding's plugin manifest (`.mcp.json`) launches `clad serve` automatically when the plugin is enabled. Invoke this skill only for debugging the MCP server in isolation.
For an organization to trust AI with its code, three things must hold — trust, traceability, and stability at scale. cladding wraps your AI coding agent: your intent goes in before it writes, and the result is verified against your spec after, so those three are earned, not assumed. First L4 implementation of the Ironclad standard.
Use only when the user explicitly names Cladding and asks to initialize, adopt, or refresh it; never use for an ordinary project…
Impl-blind test/oracle author — writes conformance tests from a spec-only brief. Tool-restricted by definition (no…
Render release notes / a changelog from the cladding spec. Use when the user asks for release notes, a changelog, 릴리즈 노트, 변경 이력,…
Run every Iron Law stage and the drift detector suite. Use when the user wants the full project health snapshot, a CI gate, or to…
Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact…
Advance Cladding onboarding after the user answers a pending product question. Use the MCP prepare/apply flow, preserve the…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.