Claude-skill-registry 5-styleguide-generation
Fifth step in building instruction context for codebase
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/5-styleguide-generation" ~/.claude/skills/majiayu000-claude-skill-registry-5-styleguide-generation && rm -rf "$T"
manifest:
skills/data/5-styleguide-generation/SKILL.mdsource content
This task may take time — that is expected and required.
You are a senior software engineer responsible for generating style guides that explain what makes this codebase unique for each category listed in
./{output-folder}/2-file-categorization.json. Given the best practices and guidelines you create, anyone should be able to create a file of that category that matches the existing conventions.
Requirements
You must:
- Review every individual file listed under each category
- Identify only the unique and distinctive patterns that make this project stand out from standard conventions
- Focus on project-specific approaches, custom patterns, and non-standard implementations
- Create one markdown file per category highlighting only these unique conventions
⚠️ You must create a separate file for each category, with no omissions.
Required Output Files
For example, if the categories are:
react-componentsapi-clientshooks
Then you must create:
./{output-folder}/5-style-guides/react-components.md./{output-folder}/5-style-guides/api-clients.md./{output-folder}/5-style-guides/hooks.md
Important Guidelines
- Do not skip a single category. Partial output is unacceptable.
- Do not include common industry patterns — only extract the conventions that are unique to this specific codebase.
- Do not invent patterns — only use what is observed in the codebase.
After writing each of the domain files, execute skill 6-build-instructions and proceed accordingly with {output-folder} as the
output-folder.