setup-docs
Skill288 starsChanged 51 days agoMITView on GitHub
Run the docs site, blog, or Storybook locally. Use when contributing to documentation, previewing blog posts, or developing UI components in isolation. Not needed for regular frontend development.
- Installs packages
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adrSkill
- commitSkill
- db-migrateSkill
- dcoSkill
- event-trackingSkill
- fix-security-findingSkill
- fix-vulnsSkill
- preflightSkill
- review-prSkill
- setupSkill
- tech-writerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
All commands run from the frontend/ directory.
≈ “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.
Files
Local Docs, Blog & Storybook Setup
These are all independent of the main dev server — you don't need the database or Auth0 configured to run any of them. Just make sure dependencies are installed first (pnpm install --filter frontend from the repo root).
All commands run from the frontend/ directory.
Docs site
VitePress docs served at http://localhost:5173:
cd frontend && pnpm docs:devBuild and preview the production output:
cd frontend && pnpm docs:build && pnpm docs:previewBlog
VitePress blog served at http://localhost:5174:
cd frontend && pnpm blog:devBuild and preview:
cd frontend && pnpm blog:build && pnpm blog:preview --port 5174Storybook
Component development and documentation, served at http://localhost:6006:
cd frontend && pnpm storybookBuild static Storybook:
cd frontend && pnpm storybook:buildTroubleshooting
- Port already in use — kill the process using the port or change it with
--port <N> - Missing dependencies — run
pnpm install --filter frontendfrom the repo root first - Storybook build errors — usually a component import issue; check the console output for the failing story
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.

