[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75P7C4DGS9NDQ040RZ45GCJ":3,"skill-same:01M75P7C4DGS9NDQ040RZ45GCJ":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75P7C4DGS9NDQ040RZ45GCJ","code-to-diagram",null,"Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS\u002FTS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a module diagram from source code.","NobleFatherCreations\u002FWookbook","NobleFatherCreations","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F293071470?v=4","01M75MK5GTGGTFASDP4VDSYNJ1","01M75MK5HARFP14YVRHXYXG49Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fcode-to-diagram\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fcode-to-diagram\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: code-to-diagram\ndescription: \"Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS\u002FTS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a module diagram from source code.\"\nlicense: MIT\ntype: tool\ntags: [\"visualization\", \"architecture\", \"mermaid\", \"ast\", \"diagram\"]\n---\n\n# Code to Diagram\n\nExtract import and dependency relationships from a codebase via AST parsing, and automatically generate three types of diagrams:\n\n1. **Architecture Diagram** — Module\u002Fdirectory-level dependency relationships\n2. **Flowchart** — File-level import call chains\n3. **Org Chart** — Directory\u002Ffile hierarchy structure\n\nSupported languages: Python, JavaScript, TypeScript, Go, Java\n\nOutput formats: Mermaid text (`.mmd`) or SVG images (requires `mmdc` installed on the system)\n\n## Usage\n\n### Basic: Analyze an Entire Project\n\n```bash\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject\n```\n\nOutputs three Mermaid diagrams to stdout and writes `.mmd` files to the current directory.\n\n### Specify Diagram Type\n\n```bash\n# Architecture diagram only\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --type architecture\n\n# Flowchart only\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --type flowchart\n\n# Org chart only\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --type org\n```\n\n### Specify Output Directory and Format\n\n```bash\n# Output to a specific directory\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --output \u002Ftmp\u002Fdiagrams\n\n# Output as SVG (requires mmdc)\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --format svg\n\n# Output both Mermaid and SVG\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --format both\n```\n\n### Output JSON Analysis Results\n\n```bash\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --json\n```\n\n### Parameters\n\n| Parameter | Description |\n|-----------|-------------|\n| `directory` | Code directory to analyze (required) |\n| `--type, -t` | Diagram type: `architecture`, `flowchart`, `org`, `all` (default: `all`) |\n| `--output, -o` | Output directory (default: current directory) |\n| `--format, -f` | Output format: `mermaid`, `svg`, `both` (default: `mermaid`) |\n| `--max-files` | Maximum number of files to scan (default: 500) |\n| `--max-depth` | Maximum depth for org chart (default: 4) |\n| `--json` | Output analysis results in JSON format |\n\n## How It Works\n\n1. **Scan phase**: Recursively traverse the directory, skipping `node_modules`, `.git`, `__pycache__`, etc.\n2. **Parse phase**:\n   - Python files: uses the `ast` module to parse `import` and `from ... import` statements\n   - JS\u002FTS files: uses regex to match `import`, `require`, and `export from`\n   - Go files: uses regex to match `import` statements\n   - Java files: uses regex to match `import` statements\n3. **Resolve internal dependencies**: Maps import paths to actual files within the project\n4. **Generate diagrams**: Converts dependency relationships into Mermaid diagram syntax\n5. **Render (optional)**: Calls `mmdc` (Mermaid CLI) to render `.mmd` files as SVG\n\n## Use Cases\n\n- Quickly understand the module structure of an unfamiliar project\n- Visualize dependencies during code review\n- Create architecture diagrams for technical documentation\n- Detect circular dependencies or excessive coupling\n- Analyze project structure before refactoring\n\n## Dependencies\n\n- Python 3.7+ (standard library only, no extra packages needed)\n- SVG output requires `@mermaid-js\u002Fmermaid-cli` (optional)\n\n## Notes\n\n- Only analyzes static import relationships; dynamic imports are not tracked\n- For large projects, use `--max-files` to limit the scan scope\n- Mermaid diagrams with too many nodes may be hard to render; use `--type` to generate diagrams separately\n","# Code to Diagram\n\nExtract import and dependency relationships from a codebase via AST parsing, and automatically generate three types of diagrams:\n\n1. **Architecture Diagram** — Module\u002Fdirectory-level dependency relationships\n2. **Flowchart** — File-level import call chains\n3. **Org Chart** — Directory\u002Ffile hierarchy structure\n\nSupported languages: Python, JavaScript, TypeScript, Go, Java\n\nOutput formats: Mermaid text (`.mmd`) or SVG images (requires `mmdc` installed on the system)\n\n## Usage\n\n### Basic: Analyze an Entire Project\n\n```bash\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject\n```\n\nOutputs three Mermaid diagrams to stdout and writes `.mmd` files to the current directory.\n\n### Specify Diagram Type\n\n```bash\n# Architecture diagram only\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --type architecture\n\n# Flowchart only\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --type flowchart\n\n# Org chart only\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --type org\n```\n\n### Specify Output Directory and Format\n\n```bash\n# Output to a specific directory\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --output \u002Ftmp\u002Fdiagrams\n\n# Output as SVG (requires mmdc)\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --format svg\n\n# Output both Mermaid and SVG\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --format both\n```\n\n### Output JSON Analysis Results\n\n```bash\npython3 scripts\u002Fanalyze_codebase.py \u002Fpath\u002Fto\u002Fproject --json\n```\n\n### Parameters\n\n| Parameter | Description |\n|-----------|-------------|\n| `directory` | Code directory to analyze (required) |\n| `--type, -t` | Diagram type: `architecture`, `flowchart`, `org`, `all` (default: `all`) |\n| `--output, -o` | Output directory (default: current directory) |\n| `--format, -f` | Output format: `mermaid`, `svg`, `both` (default: `mermaid`) |\n| `--max-files` | Maximum number of files to scan (default: 500) |\n| `--max-depth` | Maximum depth for org chart (default: 4) |\n| `--json` | Output analysis results in JSON format |\n\n## How It Works\n\n1. **Scan phase**: Recursively traverse the directory, skipping `node_modules`, `.git`, `__pycache__`, etc.\n2. **Parse phase**:\n   - Python files: uses the `ast` module to parse `import` and `from ... import` statements\n   - JS\u002FTS files: uses regex to match `import`, `require`, and `export from`\n   - Go files: uses regex to match `import` statements\n   - Java files: uses regex to match `import` statements\n3. **Resolve internal dependencies**: Maps import paths to actual files within the project\n4. **Generate diagrams**: Converts dependency relationships into Mermaid diagram syntax\n5. **Render (optional)**: Calls `mmdc` (Mermaid CLI) to render `.mmd` files as SVG\n\n## Use Cases\n\n- Quickly understand the module structure of an unfamiliar project\n- Visualize dependencies during code review\n- Create architecture diagrams for technical documentation\n- Detect circular dependencies or excessive coupling\n- Analyze project structure before refactoring\n\n## Dependencies\n\n- Python 3.7+ (standard library only, no extra packages needed)\n- SVG output requires `@mermaid-js\u002Fmermaid-cli` (optional)\n\n## Notes\n\n- Only analyzes static import relationships; dynamic imports are not tracked\n- For large projects, use `--max-files` to limit the scan scope\n- Mermaid diagrams with too many nodes may be hard to render; use `--type` to generate diagrams separately\n",{"name":5,"tags":24,"type":30,"license":14,"description":7},[25,26,27,28,29],"visualization","architecture","mermaid","ast","diagram","tool","main","2054e69da4e24a9c2d4ea00a9dfaf7b82ecaad16","tools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fcode-to-diagram","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations","2026-10-27 22:28:45",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add NobleFatherCreations\u002FWookbook --skill code-to-diagram",{"tool":43,"command":44},"bunx","bunx skills add NobleFatherCreations\u002FWookbook --skill code-to-diagram",{"tool":46,"command":47},"pnpm","pnpm dlx skills add NobleFatherCreations\u002FWookbook --skill code-to-diagram","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fcode-to-diagram\u002FSKILL.md",true,[51,55],{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":15},"LICENSE","许可证",1083,{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Fanalyze_codebase.py","SCRIPT","脚本",17030,"https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fcode-to-diagram\u002Fscripts\u002Fanalyze_codebase.py",[62,69,77,85,92,100],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75PT3YZYRSXP9C3WSMGB8M5","typescript-pro","Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftypescript-pro\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75PSYW9K37V0KSW2DQVD6GS","tos-clause-scanner","Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues. Trigger when a user asks to review, audit, or analyze a ToS, privacy policy, or user agreement, or mentions specific concerns like auto-renewal or data authorization.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftos-clause-scanner\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftos-clause-scanner\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M75PSM0B592091AD055VWBE8","timeline-builder","Generate beautiful interactive timeline HTML pages from JSON data, with vertical, horizontal, or dual-side layouts, collapsible details, and custom colors. Ideal for project milestones, company histories, or resumes. Triggered when a user mentions 'timeline', 'history of events', 'project milestones', 'release log', or asks to visualize a chronological sequence of data.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftimeline-builder\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftimeline-builder\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M75PSC75EEQKNN9J622ADPV4","three-best-practices","Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL\u002FWebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fthree-best-practices\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M75PS6QF7WM17XMPW2BJKBTC","test-suite-architect","This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-suite-architect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-suite-architect\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M75PS409PK46W5QD9K3W6A2M","test-driven-dev","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-driven-dev\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-driven-dev\u002FSKILL.md",[],[]]