kyto64kyto64/aidd-template-scale/.agents/skills/docs-app-sync/SKILL.md

docs-app-sync

Skill0 starsChanged 2 months agoMITView on GitHub

Sync VitePress navigation when docs/ markdown files are added, removed, or renamed.

In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/CLAUDE.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/docker-compose-local.mdcCursor rule
- .cursor/rules/github-cli-pr.mdcCursor rule
- .cursor/rules/git.mdcCursor rule
- .cursor/rules/git-worktree.mdcCursor rule
- .cursor/rules/ticket-driven-workflow.mdcCursor rule
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
When docs//*.md changes in a PR, update these three navigation surfaces in the same PR:
line 9
Very specific:
Update _inventory.md when new doc areas or directories appear
line 21
Very specific:
Run pnpm --dir docs-site build when Node/pnpm available
line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Docs app sync

When docs/**/*.md changes in a PR, update these three navigation surfaces in the same PR:

Surface	Location
Sidebar	`docs-site/.vitepress/config.mjs`
Directory index	`docs/<area>/index.md` tables
Inventory	`docs/_inventory.md`

Steps

git diff --name-status -- docs/**/*.md (or compare to main)
For each added/removed/renamed page, update sidebar links and index tables
Update _inventory.md when new doc areas or directories appear
Run pnpm --dir docs-site build when Node/pnpm available

Notes

VitePress srcDir points at ../docs — do not duplicate markdown under docs-site/.

Download now (ZIP)

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