agentleFS
Sign inStart free
purpleeddypurpleeddy/cladding/.cursor/skills/cladding-init/SKILL.md

cladding-init

Skill16 starsChanged 4 months agoMITView on GitHub

Use only when the user explicitly names Cladding and asks to initialize, adopt, or refresh it; never use for an ordinary project creation or implementation request. Scaffold from an idea, planning document, or existing project through the MCP prepare/apply flow.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this workflow only when the user explicitly asks to initialize, adopt, or refresh Cladding.

    line 8
  2. Very specific:

    If the current user message itself matches APPLY CLADDING XXXXXX, do not call prepare or stage again.

    line 12
  3. Distinctive:

    If a greenfield request has no project intent, ask for one short description.

    line 14
  4. Very specific:

    Call clad_prepare_init with exactly one starting mode:

    line 15
  5. Very specific:

    Do not run clad init in a shell from an AI-host onboarding session.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cladding init

Use this workflow only when the user explicitly asks to initialize, adopt, or refresh Cladding. Opening a repository alone is not consent to initialize it.

Required host workflow

If the current user message itself matches APPLY CLADDING XXXXXX, do not call prepare or stage again. Call clad_init once and copy the entire user message, including the APPLY CLADDING prefix, into confirmation.

  1. If a greenfield request has no project intent, ask for one short description.
  2. Call clad_prepare_init with exactly one starting mode:
    • idea with the user's description.
    • document with a project-relative planning-document path.
    • existing for an existing codebase; include an optional adoption goal.
  3. Read the returned prompt and observations. Draft the structured object required by clad_init using the current host model, then call clad_stage_init with the preparation token and that draft. Staging validates the draft and stores only ignored runtime state under .cladding/host/; it does not modify authored project files.
  4. Show plannedChanges, the staged confirmationQuestion, and its one-time approvalChallenge to the user, then stop and wait for a separate reply. The original initialization request is not confirmation.
  5. Only when the user's separate reply exactly matches approvalChallenge, call clad_init with the entire reply verbatim as confirmation—never strip the APPLY CLADDING prefix. Include the draft and token when the host retained them; process-per-turn hosts may omit both because Cladding resolves the exact staged draft from its short-lived machine-local cache. Questions, paraphrases, and generic acknowledgements are not approval.
  6. If nextQuestion is present, show it verbatim and end the assistant turn immediately. Never answer it, infer an answer, or call either clarify tool during the initialization-approval turn. Continue with the Cladding clarify workflow only after a new user message supplies the answer. If no question remains, report that ordinary development can begin.

Do not run clad init in a shell from an AI-host onboarding session. Do not use MCP sampling. If the MCP tools are absent, tell the user to run clad setup, restart the AI host in the project directory, and stop without writing project files.

clad_prepare_init does not modify the workspace, and clad_stage_init writes only ignored runtime state. Never call stage and apply in the same assistant turn. Only clad_init writes authored artifacts, after explicit user confirmation plus schema and freshness validation. A stale, malformed, or replayed apply request must be prepared again.

The raw CLI remains available for terminal, CI, offline, and explicitly configured SDK automation; it is not the primary host onboarding path.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. qwerfunch/cladding★ 14100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository17 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free