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

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. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 119 edited versions we read keep these.

  • 1

    Distinctive

    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 measured: kept by at least 6 in 10 of the 119 edited versions of this file we could read. “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 onboarding is complete and that the next step is to author the first feature's spec — its acceptance criteria and the files it will cover — before writing any code; the feature cycle starts there, not with scaffolding.

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.

Initialization also creates or appends spec/index.yaml merge=union in .gitattributes. It preserves every existing attribute and never assigns a merge driver to spec/attestation.yaml; the strict gate rewrites that verification record canonically after an ordinary merge.

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 versions131 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 131

    1. microsoft/vscode★ 194ksame name
    2. mcollina/skills★ 2ksame name
    3. skyllwt/OmegaWiki★ 1.7ksame name
    4. DAIR-AutoResearch/AutoSci★ 1.7ksame name
    5. PKU-DAIR/AutoSci★ 1.7ksame name
    6. skyllwt/AutoSci★ 1.7ksame name
    7. TokenRollAI/cc-plugin★ 483same name
    8. pipecat-ai/gradient-bang★ 420same name
    9. AlexPEClub/ai-coding-starter-kit★ 382same name
    10. dannysmith/tauri-template★ 312same name

    121 more not listed

    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.

  • Used alongsideProjects with it also use daily-arxiv, exp-eval and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • LambenthanSkill

      daily-arxiv

      每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

      Also in 5 projects that use this

    • LambenthanSkill

      exp-eval

      实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

      Also in 5 projects that use this

    • skyllwtSkill

      exp-pilot-eval

      Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

      Also in 4 projects that use this

    • skyllwtSkill

      exp-pilot-run

      Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

      Also in 4 projects that use this

    • gaebalaiSkill

      codex-system

      PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

      Also in 3 projects that use this

    • +6 more from Lambenthan
    • +1 more from skyllwt
  • 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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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