5-styleguide-generation
Creates domain-specific style guides by analyzing patterns in categorized project files.
Install
mkdir -p .claude/skills/5-styleguide-generation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11502" && unzip -o skill.zip -d .claude/skills/5-styleguide-generation && rm skill.zipInstalls to .claude/skills/5-styleguide-generation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Fifth step in building instruction context for codebaseKey capabilities
- →Review every individual file under each category
- →Identify unique and distinctive patterns in the codebase
- →Focus on project-specific approaches, custom patterns, and non-standard implementations
- →Create one markdown file per category highlighting unique conventions
- →Generate style guides that explain what makes the codebase unique
- →Ensure anyone can create a file matching existing conventions based on the guides
How it works
This skill reviews every file in each category to identify unique and distinctive patterns. It then creates a markdown file for each category, detailing these project-specific conventions.
Inputs & outputs
When to use 5-styleguide-generation
- →Generating style guides
- →Codifying project standards
- →Documentation creation
- →Standardizing patterns
About this skill
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.
When not to use it
- →When the task is not about generating style guides for a codebase
- →When the user does not want to identify unique and distinctive patterns
- →When the user does not need to create markdown files for each category of files
Limitations
- →The skill must review every individual file listed under each category.
- →It must identify only the unique and distinctive patterns.
- →It must create one markdown file per category, with no omissions.
How it compares
This process focuses on extracting only the unique and non-standard patterns specific to the codebase, unlike documenting common industry patterns.
Compared to similar skills
5-styleguide-generation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| 5-styleguide-generation (this skill) | 0 | 5mo | No flags | Advanced |
| docx | 93 | 5mo | Review | Advanced |
| notion-knowledge-capture | 10 | 9mo | No flags | Intermediate |
| session-handoff | 13 | 2mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by diegosouzapw
View all by diegosouzapw →You might also like
docx
anthropics
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
session-handoff
davila7
Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
feishu-doc
openclaw
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
marker
benchflow-ai
Convert PDF documents to Markdown using marker_single. Use when Claude needs to extract text content from PDFs while preserving LaTeX formulas, equations, and document structure. Ideal for academic papers and technical documents containing mathematical notation.