Adopt a typed spec for your hand-written CLAUDE.md
Start a typed CLAUDE.md.spec.ts from your existing hand-written instructions — faithful, non-destructive, reversible, and never an upgrade in disguise
- What
- Start a typed CLAUDE.md.spec.ts from your existing hand-written instructions — faithful, non-destructive, reversible, and never an upgrade in disguise
- Cost
- Free
- Needs
- node/npm and a hand-written CLAUDE.md or AGENTS.md you want to type-check going forward (install vigiles with npm install -D vigiles first) — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @zernie's adopt-spec skill for the vigiles tooling: adopt a typed .spec.ts for an existing hand-written CLAUDE.md (or AGENTS.md) — starting from the file you already have, non-destructively. The adoption rules are non-negotiable: faithful (preserve every rule, command, key file and prose section as-is — the spec must compile back to ~your existing file), non-destructive (never edit the original; only write the new .spec.ts; switching to spec-managed is a separate explicit step), don't escalate enforcement (keep guidance() as guidance() — upgrading to enforce() is the separate strengthen skill), reversible (vigiles eject hands the file back as plain markdown anytime), and ask before writing (present the generated spec and summary first; write only on yes). The workflow: read the existing file (and check vigiles is installed — suggest npm install -D vigiles if not), parse the structure (commands, key files, rules with **Enforced by:** or **Guidance only** annotations, prose), classify each rule (linter-backed → enforce("linter/rule"), code-review-backed → guidance(), unannotated → TODO), generate the spec file (claude({sections, keyFiles, commands, rules}) with file()/cmd()/ref() refs enabling stale-reference detection), verify it compiles (npx vigiles compile and compare against the original), present the result (conversion counts, compile/lint commands, ask to write the file), optionally set up CI (GitHub Actions steps or the zernie/vigiles@v1 action). Honest caveats: disable-model-invocation is set in frontmatter — this skill only runs when you ask for it directly; the spec is only as good as the CLAUDE.md you start from; compile-then-compare is the honesty check that the spec stayed faithful. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: node/npm and a hand-written CLAUDE.md or AGENTS.md you want to type-check going forward (install vigiles with npm install -D vigiles first) — the skill is guidance the agent follows, not software to install Install "Adopt a typed spec for your hand-written CLAUDE.md" for me. It gives my agent @zernie's adopt-spec skill for vigiles: read the existing instruction file, parse its structure (commands, key files, rules, prose), classify each rule (enforce/guidance/TODO), generate the typed CLAUDE.md.spec.ts (never touching the original), verify it compiles and matches the original, present the result for approval, and optionally set up CI. MIT-licensed. Repository: https://github.com/zernie/vigiles/blob/main/skills/adopt-spec/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "adopt-spec". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. npm install -D vigiles in the target project; ask the agent to adopt your CLAUDE.md — it presents the spec before writing anything). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.