docs-site
Skill1 starsChanged 3 months agoMITView on GitHub
Repo-local docs-maintenance dev skill for the Cadence documentation site (the Starlight project in website/). NOT a distributed plugin skill — it never ships to Cadence users. A thin dispatcher that routes to one of three self-contained actions: drift-check (semantically compare each reference page against its source SKILL.md and propose per-page patches, never auto-fixing), new-skill-doc (scaffold a reference page and register it in the sidebar when a new /c-* command ships), and course-lesson (enforce the course voice and structure when writing or revising a course lesson). Use when maintaining, drift-checking, or extending the Cadence docs site.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- navjyotnishant/nj-agentstheir own version, first seen Oct 15, 2026
- Lee-Dongwook/E2E-Self-Healtheir own version, first seen Oct 9, 2026
- VPDPersonal/Aspid.MVVMtheir own version, first seen Oct 9, 2026
- AmineDjeghri/awesome-os-setuptheir own version, first seen Oct 8, 2026
- INERATE/ateliertheir own version, first seen Sep 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- AmineDjeghri/awesome-os-setup★ 673same name
- VPDPersonal/Aspid.MVVM★ 65same name
- Lee-Dongwook/E2E-Self-Heal★ 9same name
- INERATE/atelier★ 2same name
- navjyotnishant/nj-agents★ 1same name
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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- c-auditSkill
- c-brainstormSkill
- c-checkSkill
- c-designSkill
- c-executeSkill
- c-explainSkill
- c-find-bugsSkill
- c-planSkill
- c-validateSkill
- c-worktreeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Read the matching actions/<name>.md and follow that file's procedure end to end.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
docs-site
You maintain the Cadence documentation site — the Starlight project under website/. This is a repo-local Claude Code skill at .claude/skills/docs-site/. It is a Cadence-development tool only.
This skill is not one of the distributed /c-* plugin skills. Those live at skills/<name>/SKILL.md and ship to every Cadence user (c-brainstorm, c-design, c-plan, c-execute, c-audit, c-validate, c-check, c-find-bugs, c-explain, c-worktree). docs-site is repo-local infrastructure for the people who write Cadence's docs and is never bundled into the plugin — plugin users never see it.
You are a thin dispatcher. You carry no procedure detail of your own. Your job is to identify which action the user wants, then read and follow the matching actions/<name>.md end to end. Each action file is fully self-contained.
Routing table
Match the user's request against this table and pick exactly one action:
| User intent | Action | File |
"drift check", "is the reference out of date?", "does this page still match its command?", "check the docs against the skills", any sync/staleness check between reference pages and skills/<command>/SKILL.md | drift-check | actions/drift-check.md |
"new skill doc", "scaffold a reference page for c-foo", "a new /c-* command shipped", "wire a new command into the docs site" | new-skill-doc | actions/new-skill-doc.md |
"course lesson", "write/revise a course page", "check this lesson's voice", "is this lesson on-voice?", authoring or polishing any page under course/ | course-lesson | actions/course-lesson.md |
How to dispatch
- The user names an action — for example "docs-site drift check", "docs-site new-skill-doc for
c-foo", or invokes the skill with an action argument. - Match the request against the routing table above to pick one of
{drift-check, new-skill-doc, course-lesson}. - Read the matching
actions/<name>.mdand follow that file's procedure end to end. Do not improvise procedure detail here — the action file is the source of truth. - If no action is named (or the request is ambiguous), do not guess. List the three available actions with a one-line summary each and ask which to run:
- drift-check — compare each reference page to its source
SKILL.mdand propose per-page patches; never auto-fixes. - new-skill-doc — scaffold a reference page and register it in the sidebar when a new
/c-*command ships. - course-lesson — enforce the course voice and structure when writing or revising a course lesson.
- drift-check — compare each reference page to its source
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
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.