[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79A488VSWFNEBAJ5SP3EQ5V":3,"skill-same:01M79A488VSWFNEBAJ5SP3EQ5V":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79A488VSWFNEBAJ5SP3EQ5V","cli-architecture",null,"The single source of truth for what \"production-grade\" means for every CLI this plugin generates, in any of the 12 languages plus the POSIX sh dialect. Load this doctrine BEFORE any paradigm skill (cli-scaffold-compiled, cli-scaffold-interpreted, cli-scaffold-shell) generates a scaffold. Defines the five-pillar architecture, the frozen 0\u002F1\u002F2 exit-code contract, and the discoverability, composability, stability, and distribution requirements that the cli-scaffold-verifier checks. Never duplicate this doctrine into paradigm skills — reference it.","Anselmoo\u002Fwerkstoff","Anselmoo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13209783?v=4","01M799YTB3D7RZ4P3B8CSR2X85","Anselm Hahn","01M799YTBRAM6719D9V0NRGB4R",1,"MIT","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Fplugins\u002Fcli-scaffold\u002Fskills\u002Fcli-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cli-architecture\ndescription: The single source of truth for what \"production-grade\" means for every CLI this plugin generates, in any of the 12 languages plus the POSIX sh dialect. Load this doctrine BEFORE any paradigm skill (cli-scaffold-compiled, cli-scaffold-interpreted, cli-scaffold-shell) generates a scaffold. Defines the five-pillar architecture, the frozen 0\u002F1\u002F2 exit-code contract, and the discoverability, composability, stability, and distribution requirements that the cli-scaffold-verifier checks. Never duplicate this doctrine into paradigm skills — reference it.\n---\n\n# CLI Architecture Doctrine\n\nThis is the **only** place the plugin defines \"production-grade.\" Every paradigm\nskill loads this before generating anything, and the `cli-scaffold-verifier`\nagent checks generated scaffolds against it. Paradigm skills and per-language\nreference files **reference** these rules; they never restate them. (The repo\nself-check `scripts\u002Fcheck_doctrine_isolation.py` fails the build if a paradigm\nskill duplicates the contract or re-enumerates the pillars.)\n\nThe numeric bounds and enumerations below are mirrored in\n`scripts\u002Fconstants.py`, which asserts them at import time. That module — not this\nprose — is the enforcement. This document explains the intent; the scripts refuse\nviolations.\n\n## The Five Pillars\n\nEvery generated CLI, regardless of language, must satisfy all five. The\n`cli-scaffold-verifier` maps each finding back to one pillar.\n\n1. **UX \u002F discoverability.** `--help` prints a structured help block, and the\n   CLI ships shell completions through a first-party mechanism where one exists.\n2. **Backend \u002F core separation.** Business logic lives in a core module\u002Flibrary\n   with **zero** CLI-framework imports; the entry point is a thin wrapper.\n3. **Stability.** A frozen exit-code contract, NO_COLOR support, fail-fast\n   non-interactive behavior, and a snapshot-tested `--help`.\n4. **Idiomatic distribution.** Real packaging metadata for the one idiomatic\n   distribution channel of that ecosystem — never a \"zip the files\" fallback.\n5. **Unix composability.** Results to stdout, diagnostics to stderr, and a\n   `--json` structured-output mode.\n\n## The Frozen Exit-Code Contract\n\nIdentical in all 12 languages plus the POSIX sh dialect, no exceptions. Enforced by\n`EXIT_SUCCESS`\u002F`EXIT_RUNTIME_ERROR`\u002F`EXIT_USAGE_ERROR` in `scripts\u002Fconstants.py`\nand checked by `verify_scaffold.py`:\n\n| Outcome | Code |\n|---|---|\n| Successful invocation with valid arguments | `0` |\n| Runtime error (failed operation, caught exception) | `1` |\n| Usage error (bad flags, missing required arg, type mismatch) | `2` |\n\n`--no-input` set **and** required input missing ⇒ exit `2` rather than blocking.\nRunning non-interactively (no TTY \u002F piped \u002F CI) without `--no-input` ⇒ **fail\nfast**, never hang.\n\n## Discoverability: the `--help` structure\n\n`--help` (and the bare-invocation convention) prints, in order:\n\n1. **Usage** summary — always first.\n2. **Arguments** \u002F **Positional** section — when the CLI takes positional args,\n   each with a description.\n3. **Options** section — when the CLI takes flags, every flag with its short\n   form (if any), long form, and a one-line description.\n\n## Composability & output discipline\n\n- **stdout** carries result data a downstream pipeline consumes. Nothing purely\n  diagnostic may land there.\n- **stderr** carries diagnostics, progress, logs, warnings. Nothing a consumer\n  must parse as data may land there.\n- **`--json`** (or the ecosystem-idiomatic equivalent) switches results to\n  structured JSON via the ecosystem's standard serializer.\n- **`--no-input`** (or `-n` \u002F `--no-interaction`) disables interactive prompts.\n- **NO_COLOR**: when set to any non-empty value, emit no ANSI color\u002Fstyling\n  (per https:\u002F\u002Fno-color.org).\n\n## Stability: testing & the exit contract\n\nEvery scaffold ships a **snapshot test** that captures its own `--help` output\nand compares it to a stored golden file using that language's idiomatic\nsnapshot-testing tool.\n\n## Distribution\n\nEvery scaffold ships packaging metadata (manifest \u002F spec file \u002F project file)\nconfigured for the **single** idiomatic distribution channel of that language.\nThe per-language reference file names that one channel.\n\n## How generation works (freeform, converging)\n\nScaffolds are generated **freeform** — from these idioms, never from stored\nboilerplate. Identical requests converge on the same structure because the\ndoctrine and per-language reference constrain the shape, not because a template\nis copied.\n\n## The scaffold manifest (gating fields, first-class keys)\n\nBecause the verifier decides pass\u002Ffail on structured keys — never on prose — each\ngenerated scaffold includes a `cli-scaffold.manifest.json` at its root declaring\nthe file roles the verifier needs:\n\n```json\n{\n  \"language\": \"rust\",\n  \"app_name\": \"myapp\",\n  \"core_files\": [\"src\u002Flib.rs\"],\n  \"entry_file\": \"src\u002Fmain.rs\",\n  \"distribution_file\": \"Cargo.toml\",\n  \"snapshot_test\": \"tests\u002Fhelp_snapshot.rs\",\n  \"help_file\": \"tests\u002Fhelp.golden\",\n  \"flags\": [\n    {\"long\": \"--json\", \"short\": null, \"description\": \"emit JSON\"},\n    {\"long\": \"--no-input\", \"short\": \"-n\", \"description\": \"disable prompts\"}\n  ],\n  \"positional_args\": [{\"name\": \"target\", \"description\": \"thing to process\"}],\n  \"completion\": {\"mechanism\": \"clap_complete\", \"file\": null}\n}\n```\n\nFor a language with no native completion mechanism, declare it honestly:\n`\"completion\": {\"supported\": false, \"note\": \"Perl has no native completion mechanism\"}`.\n\n## The 12 languages plus the POSIX sh dialect, and 3 paradigms\n\n- **compiled** → Rust, Go, .NET — handled by `cli-scaffold-compiled`\n- **interpreted** → Python, TypeScript, JavaScript, Ruby, PHP, Perl — handled by\n  `cli-scaffold-interpreted`\n- **shell** → Bash, Zsh, PowerShell, and the POSIX sh dialect — handled by\n  `cli-scaffold-shell`\n\n`scaffold-cli` resolves a language to its paradigm via\n`scripts\u002Flang_router.py`, which refuses unsupported or ambiguous names rather\nthan guessing.\n","# CLI Architecture Doctrine\n\nThis is the **only** place the plugin defines \"production-grade.\" Every paradigm\nskill loads this before generating anything, and the `cli-scaffold-verifier`\nagent checks generated scaffolds against it. Paradigm skills and per-language\nreference files **reference** these rules; they never restate them. (The repo\nself-check `scripts\u002Fcheck_doctrine_isolation.py` fails the build if a paradigm\nskill duplicates the contract or re-enumerates the pillars.)\n\nThe numeric bounds and enumerations below are mirrored in\n`scripts\u002Fconstants.py`, which asserts them at import time. That module — not this\nprose — is the enforcement. This document explains the intent; the scripts refuse\nviolations.\n\n## The Five Pillars\n\nEvery generated CLI, regardless of language, must satisfy all five. The\n`cli-scaffold-verifier` maps each finding back to one pillar.\n\n1. **UX \u002F discoverability.** `--help` prints a structured help block, and the\n   CLI ships shell completions through a first-party mechanism where one exists.\n2. **Backend \u002F core separation.** Business logic lives in a core module\u002Flibrary\n   with **zero** CLI-framework imports; the entry point is a thin wrapper.\n3. **Stability.** A frozen exit-code contract, NO_COLOR support, fail-fast\n   non-interactive behavior, and a snapshot-tested `--help`.\n4. **Idiomatic distribution.** Real packaging metadata for the one idiomatic\n   distribution channel of that ecosystem — never a \"zip the files\" fallback.\n5. **Unix composability.** Results to stdout, diagnostics to stderr, and a\n   `--json` structured-output mode.\n\n## The Frozen Exit-Code Contract\n\nIdentical in all 12 languages plus the POSIX sh dialect, no exceptions. Enforced by\n`EXIT_SUCCESS`\u002F`EXIT_RUNTIME_ERROR`\u002F`EXIT_USAGE_ERROR` in `scripts\u002Fconstants.py`\nand checked by `verify_scaffold.py`:\n\n| Outcome | Code |\n|---|---|\n| Successful invocation with valid arguments | `0` |\n| Runtime error (failed operation, caught exception) | `1` |\n| Usage error (bad flags, missing required arg, type mismatch) | `2` |\n\n`--no-input` set **and** required input missing ⇒ exit `2` rather than blocking.\nRunning non-interactively (no TTY \u002F piped \u002F CI) without `--no-input` ⇒ **fail\nfast**, never hang.\n\n## Discoverability: the `--help` structure\n\n`--help` (and the bare-invocation convention) prints, in order:\n\n1. **Usage** summary — always first.\n2. **Arguments** \u002F **Positional** section — when the CLI takes positional args,\n   each with a description.\n3. **Options** section — when the CLI takes flags, every flag with its short\n   form (if any), long form, and a one-line description.\n\n## Composability & output discipline\n\n- **stdout** carries result data a downstream pipeline consumes. Nothing purely\n  diagnostic may land there.\n- **stderr** carries diagnostics, progress, logs, warnings. Nothing a consumer\n  must parse as data may land there.\n- **`--json`** (or the ecosystem-idiomatic equivalent) switches results to\n  structured JSON via the ecosystem's standard serializer.\n- **`--no-input`** (or `-n` \u002F `--no-interaction`) disables interactive prompts.\n- **NO_COLOR**: when set to any non-empty value, emit no ANSI color\u002Fstyling\n  (per https:\u002F\u002Fno-color.org).\n\n## Stability: testing & the exit contract\n\nEvery scaffold ships a **snapshot test** that captures its own `--help` output\nand compares it to a stored golden file using that language's idiomatic\nsnapshot-testing tool.\n\n## Distribution\n\nEvery scaffold ships packaging metadata (manifest \u002F spec file \u002F project file)\nconfigured for the **single** idiomatic distribution channel of that language.\nThe per-language reference file names that one channel.\n\n## How generation works (freeform, converging)\n\nScaffolds are generated **freeform** — from these idioms, never from stored\nboilerplate. Identical requests converge on the same structure because the\ndoctrine and per-language reference constrain the shape, not because a template\nis copied.\n\n## The scaffold manifest (gating fields, first-class keys)\n\nBecause the verifier decides pass\u002Ffail on structured keys — never on prose — each\ngenerated scaffold includes a `cli-scaffold.manifest.json` at its root declaring\nthe file roles the verifier needs:\n\n```json\n{\n  \"language\": \"rust\",\n  \"app_name\": \"myapp\",\n  \"core_files\": [\"src\u002Flib.rs\"],\n  \"entry_file\": \"src\u002Fmain.rs\",\n  \"distribution_file\": \"Cargo.toml\",\n  \"snapshot_test\": \"tests\u002Fhelp_snapshot.rs\",\n  \"help_file\": \"tests\u002Fhelp.golden\",\n  \"flags\": [\n    {\"long\": \"--json\", \"short\": null, \"description\": \"emit JSON\"},\n    {\"long\": \"--no-input\", \"short\": \"-n\", \"description\": \"disable prompts\"}\n  ],\n  \"positional_args\": [{\"name\": \"target\", \"description\": \"thing to process\"}],\n  \"completion\": {\"mechanism\": \"clap_complete\", \"file\": null}\n}\n```\n\nFor a language with no native completion mechanism, declare it honestly:\n`\"completion\": {\"supported\": false, \"note\": \"Perl has no native completion mechanism\"}`.\n\n## The 12 languages plus the POSIX sh dialect, and 3 paradigms\n\n- **compiled** → Rust, Go, .NET — handled by `cli-scaffold-compiled`\n- **interpreted** → Python, TypeScript, JavaScript, Ruby, PHP, Perl — handled by\n  `cli-scaffold-interpreted`\n- **shell** → Bash, Zsh, PowerShell, and the POSIX sh dialect — handled by\n  `cli-scaffold-shell`\n\n`scaffold-cli` resolves a language to its paradigm via\n`scripts\u002Flang_router.py`, which refuses unsupported or ambiguous names rather\nthan guessing.\n",{"name":5,"description":7},"main","6158c1e4e112c06af2c7ac01b13b2ed7214c0fcf","plugins\u002Fcli-scaffold\u002Fskills\u002Fcli-architecture",0,"https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff","https:\u002F\u002Fanselmoo.github.io\u002Fwerkstoff\u002F","https:\u002F\u002Fgithub.com\u002FAnselmoo","Likes to Develop","2026-11-02 04:20:59",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Anselmoo\u002Fwerkstoff --skill cli-architecture",{"tool":39,"command":40},"bunx","bunx skills add Anselmoo\u002Fwerkstoff --skill cli-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Anselmoo\u002Fwerkstoff --skill cli-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Fplugins\u002Fcli-scaffold\u002Fskills\u002Fcli-architecture\u002FSKILL.md",true,[],[48,55,62,67,72,77],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M79AJTRBNBX03WWKYJ8ENM45","toy-check","A skill that checks things in the repository and reports what it finds.","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fworkflows\u002Ffixtures\u002Ftoy-plugin\u002Fskills\u002Ftoy-check\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79AJS292F3HTDRXWZVRSN5B","demo-check","Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-uncompleted-run\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":63,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79AJP4TFQXKT1AAK1WC1JYK","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-stale-lock\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":68,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79AJM6Y50WP3G2BR4H0M60Z","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-preflight-mixed\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":73,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79AJGR6DMT8KCCK071V78XM","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Ftest\u002Fplugins\u002Ffixtures\u002Fnacharbeit-hooks-shape\u002Fplugins\u002Fdemo\u002Fskills\u002Fdemo-check\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79AJBJ4CHC4PZVWKERWF3HF","zirkel-verify-assumptions","Checks exactly ONE named assumption against real evidence in at most 3 steps and reports one outcome: confidence raised (>=90), reading changed, or still unresolved. Use to resolve a single load-bearing uncertainty — typically a blocking entry surfaced by zirkel-clarify-scope: \"verify this one assumption\", \"is it actually true that X\", \"check this before we rely on it\". For multiple uncertainties, invoke once per uncertainty — the step budget is never shared.","https:\u002F\u002Fgithub.com\u002FAnselmoo\u002Fwerkstoff\u002Fblob\u002Fmain\u002Fplugins\u002Fzirkel\u002Fskills\u002Fzirkel-verify-assumptions\u002FSKILL.md",[],[]]