[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE7X5GWN0SX5DY15PYKD67":3,"skill-same:01M6AE7X5GWN0SX5DY15PYKD67":116},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AE7X5GWN0SX5DY15PYKD67","mermaid-diagrams",null,"Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to \"diagram\", \"visualize\", \"model\", \"map out\", \"show the flow\", or when explaining system architecture, database design, code structure, or user\u002Fapplication flows.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"mermaid diagrams","mermaid","diagrams","when","design","flows","user journeys","map","structure","relationship","show","model","Charts","api","flow","database","state","git","code","create","c4 architecture","architecture diagrams","diagram","architecture","components","domain modeling","containers","visualize","2026-11-10 10:12:30",false,"---\nname: mermaid-diagrams\ndescription: Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to \"diagram\", \"visualize\", \"model\", \"map out\", \"show the flow\", or when explaining system architecture, database design, code structure, or user\u002Fapplication flows.\n---\n\n# Mermaid Diagramming\n\nCreate professional software diagrams using Mermaid's text-based syntax. Mermaid renders diagrams from simple text definitions, making diagrams version-controllable, easy to update, and maintainable alongside code.\n\n## Core Syntax Structure\n\nAll Mermaid diagrams follow this pattern:\n\n```mermaid\ndiagramType\n  definition content\n```\n\n**Key principles:**\n- First line declares diagram type (e.g., `classDiagram`, `sequenceDiagram`, `flowchart`)\n- Use `%%` for comments\n- Line breaks and indentation improve readability but aren't required\n- Unknown words break diagrams; parameters fail silently\n\n## Diagram Type Selection Guide\n\n**Choose the right diagram type:**\n\n1. **Class Diagrams** - Domain modeling, OOP design, entity relationships\n   - Domain-driven design documentation\n   - Object-oriented class structures\n   - Entity relationships and dependencies\n\n2. **Sequence Diagrams** - Temporal interactions, message flows\n   - API request\u002Fresponse flows\n   - User authentication flows\n   - System component interactions\n   - Method call sequences\n\n3. **Flowcharts** - Processes, algorithms, decision trees\n   - User journeys and workflows\n   - Business processes\n   - Algorithm logic\n   - Deployment pipelines\n\n4. **Entity Relationship Diagrams (ERD)** - Database schemas\n   - Table relationships\n   - Data modeling\n   - Schema design\n\n5. **C4 Diagrams** - Software architecture at multiple levels\n   - System Context (systems and users)\n   - Container (applications, databases, services)\n   - Component (internal structure)\n   - Code (class\u002Finterface level)\n\n6. **State Diagrams** - State machines, lifecycle states\n7. **Git Graphs** - Version control branching strategies\n8. **Gantt Charts** - Project timelines, scheduling\n9. **Pie\u002FBar Charts** - Data visualization\n\n## Quick Start Examples\n\n### Class Diagram (Domain Model)\n```mermaid\nclassDiagram\n    Title -- Genre\n    Title *-- Season\n    Title *-- Review\n    User --> Review : creates\n    \n    class Title {\n        +string name\n        +int releaseYear\n        +play()\n    }\n    \n    class Genre {\n        +string name\n        +getTopTitles()\n    }\n```\n\n### Sequence Diagram (API Flow)\n```mermaid\nsequenceDiagram\n    participant User\n    participant API\n    participant Database\n    \n    User->>API: POST \u002Flogin\n    API->>Database: Query credentials\n    Database-->>API: Return user data\n    alt Valid credentials\n        API-->>User: 200 OK + JWT token\n    else Invalid credentials\n        API-->>User: 401 Unauthorized\n    end\n```\n\n### Flowchart (User Journey)\n```mermaid\nflowchart TD\n    Start([User visits site]) --> Auth{Authenticated?}\n    Auth -->|No| Login[Show login page]\n    Auth -->|Yes| Dashboard[Show dashboard]\n    Login --> Creds[Enter credentials]\n    Creds --> Validate{Valid?}\n    Validate -->|Yes| Dashboard\n    Validate -->|No| Error[Show error]\n    Error --> Login\n```\n\n### ERD (Database Schema)\n```mermaid\nerDiagram\n    USER ||--o{ ORDER : places\n    ORDER ||--|{ LINE_ITEM : contains\n    PRODUCT ||--o{ LINE_ITEM : includes\n    \n    USER {\n        int id PK\n        string email UK\n        string name\n        datetime created_at\n    }\n    \n    ORDER {\n        int id PK\n        int user_id FK\n        decimal total\n        datetime created_at\n    }\n```\n\n## Detailed References\n\nFor in-depth guidance on specific diagram types, see:\n\n- **[references\u002Fclass-diagrams.md](references\u002Fclass-diagrams.md)** - Domain modeling, relationships (association, composition, aggregation, inheritance), multiplicity, methods\u002Fproperties\n- **[references\u002Fsequence-diagrams.md](references\u002Fsequence-diagrams.md)** - Actors, participants, messages (sync\u002Fasync), activations, loops, alt\u002Fopt\u002Fpar blocks, notes\n- **[references\u002Fflowcharts.md](references\u002Fflowcharts.md)** - Node shapes, connections, decision logic, subgraphs, styling\n- **[references\u002Ferd-diagrams.md](references\u002Ferd-diagrams.md)** - Entities, relationships, cardinality, keys, attributes\n- **[references\u002Fc4-diagrams.md](references\u002Fc4-diagrams.md)** - System context, container, component diagrams, boundaries\n- **[references\u002Fadvanced-features.md](references\u002Fadvanced-features.md)** - Themes, styling, configuration, layout options\n\n## Best Practices\n\n1. **Start Simple** - Begin with core entities\u002Fcomponents, add details incrementally\n2. **Use Meaningful Names** - Clear labels make diagrams self-documenting\n3. **Comment Extensively** - Use `%%` comments to explain complex relationships\n4. **Keep Focused** - One diagram per concept; split large diagrams into multiple focused views\n5. **Version Control** - Store `.mmd` files alongside code for easy updates\n6. **Add Context** - Include titles and notes to explain diagram purpose\n7. **Iterate** - Refine diagrams as understanding evolves\n\n## Configuration and Theming\n\nConfigure diagrams using frontmatter:\n\n```mermaid\n---\nconfig:\n  theme: base\n  themeVariables:\n    primaryColor: \"#ff6b6b\"\n---\nflowchart LR\n    A --> B\n```\n\n**Available themes:** default, forest, dark, neutral, base\n\n**Layout options:**\n- `layout: dagre` (default) - Classic balanced layout\n- `layout: elk` - Advanced layout for complex diagrams (requires integration)\n\n**Look options:**\n- `look: classic` - Traditional Mermaid style\n- `look: handDrawn` - Sketch-like appearance\n\n## Exporting and Rendering\n\n**Native support in:**\n- GitHub\u002FGitLab - Automatically renders in Markdown\n- VS Code - With Markdown Mermaid extension\n- Notion, Obsidian, Confluence - Built-in support\n\n**Export options:**\n- [Mermaid Live Editor](https:\u002F\u002Fmermaid.live) - Online editor with PNG\u002FSVG export\n- Mermaid CLI - `npm install -g @mermaid-js\u002Fmermaid-cli` then `mmdc -i input.mmd -o output.png`\n- Docker - `docker run --rm -v $(pwd):\u002Fdata minlag\u002Fmermaid-cli -i \u002Fdata\u002Finput.mmd -o \u002Fdata\u002Foutput.png`\n\n## Common Pitfalls\n\n- **Breaking characters** - Avoid `{}` in comments, use proper escape sequences for special characters\n- **Syntax errors** - Misspellings break diagrams; validate syntax in Mermaid Live\n- **Overcomplexity** - Split complex diagrams into multiple focused views\n- **Missing relationships** - Document all important connections between entities\n\n## When to Create Diagrams\n\n**Always diagram when:**\n- Starting new projects or features\n- Documenting complex systems\n- Explaining architecture decisions\n- Designing database schemas\n- Planning refactoring efforts\n- Onboarding new team members\n\n**Use diagrams to:**\n- Align stakeholders on technical decisions\n- Document domain models collaboratively\n- Visualize data flows and system interactions\n- Plan before coding\n- Create living documentation that evolves with code\n","# Mermaid Diagramming\n\nCreate professional software diagrams using Mermaid's text-based syntax. Mermaid renders diagrams from simple text definitions, making diagrams version-controllable, easy to update, and maintainable alongside code.\n\n## Core Syntax Structure\n\nAll Mermaid diagrams follow this pattern:\n\n```mermaid\ndiagramType\n  definition content\n```\n\n**Key principles:**\n- First line declares diagram type (e.g., `classDiagram`, `sequenceDiagram`, `flowchart`)\n- Use `%%` for comments\n- Line breaks and indentation improve readability but aren't required\n- Unknown words break diagrams; parameters fail silently\n\n## Diagram Type Selection Guide\n\n**Choose the right diagram type:**\n\n1. **Class Diagrams** - Domain modeling, OOP design, entity relationships\n   - Domain-driven design documentation\n   - Object-oriented class structures\n   - Entity relationships and dependencies\n\n2. **Sequence Diagrams** - Temporal interactions, message flows\n   - API request\u002Fresponse flows\n   - User authentication flows\n   - System component interactions\n   - Method call sequences\n\n3. **Flowcharts** - Processes, algorithms, decision trees\n   - User journeys and workflows\n   - Business processes\n   - Algorithm logic\n   - Deployment pipelines\n\n4. **Entity Relationship Diagrams (ERD)** - Database schemas\n   - Table relationships\n   - Data modeling\n   - Schema design\n\n5. **C4 Diagrams** - Software architecture at multiple levels\n   - System Context (systems and users)\n   - Container (applications, databases, services)\n   - Component (internal structure)\n   - Code (class\u002Finterface level)\n\n6. **State Diagrams** - State machines, lifecycle states\n7. **Git Graphs** - Version control branching strategies\n8. **Gantt Charts** - Project timelines, scheduling\n9. **Pie\u002FBar Charts** - Data visualization\n\n## Quick Start Examples\n\n### Class Diagram (Domain Model)\n```mermaid\nclassDiagram\n    Title -- Genre\n    Title *-- Season\n    Title *-- Review\n    User --> Review : creates\n    \n    class Title {\n        +string name\n        +int releaseYear\n        +play()\n    }\n    \n    class Genre {\n        +string name\n        +getTopTitles()\n    }\n```\n\n### Sequence Diagram (API Flow)\n```mermaid\nsequenceDiagram\n    participant User\n    participant API\n    participant Database\n    \n    User->>API: POST \u002Flogin\n    API->>Database: Query credentials\n    Database-->>API: Return user data\n    alt Valid credentials\n        API-->>User: 200 OK + JWT token\n    else Invalid credentials\n        API-->>User: 401 Unauthorized\n    end\n```\n\n### Flowchart (User Journey)\n```mermaid\nflowchart TD\n    Start([User visits site]) --> Auth{Authenticated?}\n    Auth -->|No| Login[Show login page]\n    Auth -->|Yes| Dashboard[Show dashboard]\n    Login --> Creds[Enter credentials]\n    Creds --> Validate{Valid?}\n    Validate -->|Yes| Dashboard\n    Validate -->|No| Error[Show error]\n    Error --> Login\n```\n\n### ERD (Database Schema)\n```mermaid\nerDiagram\n    USER ||--o{ ORDER : places\n    ORDER ||--|{ LINE_ITEM : contains\n    PRODUCT ||--o{ LINE_ITEM : includes\n    \n    USER {\n        int id PK\n        string email UK\n        string name\n        datetime created_at\n    }\n    \n    ORDER {\n        int id PK\n        int user_id FK\n        decimal total\n        datetime created_at\n    }\n```\n\n## Detailed References\n\nFor in-depth guidance on specific diagram types, see:\n\n- **[references\u002Fclass-diagrams.md](references\u002Fclass-diagrams.md)** - Domain modeling, relationships (association, composition, aggregation, inheritance), multiplicity, methods\u002Fproperties\n- **[references\u002Fsequence-diagrams.md](references\u002Fsequence-diagrams.md)** - Actors, participants, messages (sync\u002Fasync), activations, loops, alt\u002Fopt\u002Fpar blocks, notes\n- **[references\u002Fflowcharts.md](references\u002Fflowcharts.md)** - Node shapes, connections, decision logic, subgraphs, styling\n- **[references\u002Ferd-diagrams.md](references\u002Ferd-diagrams.md)** - Entities, relationships, cardinality, keys, attributes\n- **[references\u002Fc4-diagrams.md](references\u002Fc4-diagrams.md)** - System context, container, component diagrams, boundaries\n- **[references\u002Fadvanced-features.md](references\u002Fadvanced-features.md)** - Themes, styling, configuration, layout options\n\n## Best Practices\n\n1. **Start Simple** - Begin with core entities\u002Fcomponents, add details incrementally\n2. **Use Meaningful Names** - Clear labels make diagrams self-documenting\n3. **Comment Extensively** - Use `%%` comments to explain complex relationships\n4. **Keep Focused** - One diagram per concept; split large diagrams into multiple focused views\n5. **Version Control** - Store `.mmd` files alongside code for easy updates\n6. **Add Context** - Include titles and notes to explain diagram purpose\n7. **Iterate** - Refine diagrams as understanding evolves\n\n## Configuration and Theming\n\nConfigure diagrams using frontmatter:\n\n```mermaid\n---\nconfig:\n  theme: base\n  themeVariables:\n    primaryColor: \"#ff6b6b\"\n---\nflowchart LR\n    A --> B\n```\n\n**Available themes:** default, forest, dark, neutral, base\n\n**Layout options:**\n- `layout: dagre` (default) - Classic balanced layout\n- `layout: elk` - Advanced layout for complex diagrams (requires integration)\n\n**Look options:**\n- `look: classic` - Traditional Mermaid style\n- `look: handDrawn` - Sketch-like appearance\n\n## Exporting and Rendering\n\n**Native support in:**\n- GitHub\u002FGitLab - Automatically renders in Markdown\n- VS Code - With Markdown Mermaid extension\n- Notion, Obsidian, Confluence - Built-in support\n\n**Export options:**\n- [Mermaid Live Editor](https:\u002F\u002Fmermaid.live) - Online editor with PNG\u002FSVG export\n- Mermaid CLI - `npm install -g @mermaid-js\u002Fmermaid-cli` then `mmdc -i input.mmd -o output.png`\n- Docker - `docker run --rm -v $(pwd):\u002Fdata minlag\u002Fmermaid-cli -i \u002Fdata\u002Finput.mmd -o \u002Fdata\u002Foutput.png`\n\n## Common Pitfalls\n\n- **Breaking characters** - Avoid `{}` in comments, use proper escape sequences for special characters\n- **Syntax errors** - Misspellings break diagrams; validate syntax in Mermaid Live\n- **Overcomplexity** - Split complex diagrams into multiple focused views\n- **Missing relationships** - Document all important connections between entities\n\n## When to Create Diagrams\n\n**Always diagram when:**\n- Starting new projects or features\n- Documenting complex systems\n- Explaining architecture decisions\n- Designing database schemas\n- Planning refactoring efforts\n- Onboarding new team members\n\n**Use diagrams to:**\n- Align stakeholders on technical decisions\n- Document domain models collaboratively\n- Visualize data flows and system interactions\n- Plan before coding\n- Create living documentation that evolves with code\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add davila7\u002Fclaude-code-templates --skill mermaid-diagrams",{"tool":78,"command":79},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill mermaid-diagrams",{"tool":81,"command":82},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill mermaid-diagrams","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002FSKILL.md",true,[86,92,96,100,104,108,112],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"README.md","REFERENCE","参考文档",9219,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002FREADME.md",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fadvanced-features.md",10365,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002Freferences\u002Fadvanced-features.md",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fc4-diagrams.md",15266,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002Freferences\u002Fc4-diagrams.md",{"path":101,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fclass-diagrams.md",6915,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002Freferences\u002Fclass-diagrams.md",{"path":105,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Ferd-diagrams.md",12348,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002Freferences\u002Ferd-diagrams.md",{"path":109,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fflowcharts.md",9844,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002Freferences\u002Fflowcharts.md",{"path":113,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fsequence-diagrams.md",9213,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fmermaid-diagrams\u002Freferences\u002Fsequence-diagrams.md",[117,146,172,200,233,257],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":126,"publishedAt":57},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[127,128,129,130,131,132,133,134,135,32,136,137,138,139,140,141,142,143,144,145],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":57},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[152],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},[154,155,156,157,158,159,160,161,162,163,164,32,47,165,166,167,168,169,170,171],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":183,"publishedAt":57},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[178,179,180],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":181,"categoryName":182,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[184,185,186,187,188,189,190,132,191,192,193,194,195,196,197,135,198,44,32,199],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","query",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":211,"publishedAt":57},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[208],{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[212,213,214,215,216,45,217,218,219,220,221,222,223,224,53,225,226,227,228,229,230,231,132,232],"artifacts builder","web","web artifacts builder","artifacts","builder","routing","state management","component","css","frontend","ui","Tools","file","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":244,"publishedAt":57},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[240,243],{"categoryNo":241,"categoryName":242,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,248,249,213,250,221,222,251,252,253,254,132,255,137,256],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":258,"name":259,"nameZh":6,"description":260,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":261,"sourceHtmlUrl":262,"categories":263,"keywords":271,"publishedAt":57},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[264,267,268],{"categoryNo":265,"categoryName":266,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":269,"categoryName":270,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[272,273,274,275,276,277,278,279,215,280,224,47,281,282,283,284,285,196,286,32,287,288,289,290,291,143,292],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]