[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FNMG0PGW2P9T1TPTSB5XJP":3,"skill-same:01M6FNMG0PGW2P9T1TPTSB5XJP":68},{"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":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6FNMG0PGW2P9T1TPTSB5XJP","map",null,"Scan project structure and generate ARCHITECTURE.md with a Mermaid module relationship diagram. Use when user says \"\u002Fmap\".","shenxingy\u002FClade","shenxingy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89829751?v=4","01M6CQXHTV3WQZJMG0JXD93MEK","Xingyu (Alex) Shen","01M6CQXHYCTGPJ5HD8Z7MD4Q5P",10,"MIT","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fmap\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"project structure","architecture","diagram","mermaid","generate","user","use","scan","relationship","structure","project","module","with","generate architecture","when","2026-11-10 10:12:30",false,"---\nname: map\ndescription: \"Scan project structure and generate ARCHITECTURE.md with a Mermaid module relationship diagram. Use when user says \\\"\u002Fmap\\\".\"\n---\n\n# Clade for Codex\n\nThis workflow runs **directly in Codex**. Do not launch the `claude` CLI or\ndelegate the workflow to Clade's MCP bridge.\n\nCodex compatibility rules:\n\n- Plugin skills are namespaced. Invoke this workflow explicitly as\n  `$clade:map`; a bare `$name` does not select the installed Clade plugin.\n- Read the nearest `AGENTS.md` files for repository instructions. If a project\n  has only `CLAUDE.md`, treat it as legacy project guidance and read it too.\n- Store new Clade working state under `.clade\u002F` (or `~\u002F.clade\u002F` for personal\n  state). Existing legacy Claude state may be read for migration, but do not\n  create new vendor-specific state.\n- A `\u002Fskill-name` reference means the corresponding Codex\n  `$clade:skill-name` plugin skill, or the same workflow invoked naturally when\n  explicit skill invocation is not available.\n- Use Codex web, file, shell, image, and subagent capabilities when the source\n  workflow names a vendor-specific tool. If a capability is unavailable, use\n  the documented fallback instead of spawning another agent CLI.\n- Paths such as `\u003Cplugin-root>\u002F...` are relative to the installed Clade plugin\n  containing this `SKILL.md`; resolve that root before invoking a helper.\n\n## Canonical Clade workflow\n\n# \u002Fmap Skill: Generate Project Architecture Diagram\n\n## Purpose\nAutomatically scan the project structure and generate `ARCHITECTURE.md` with a module relationship diagram using Mermaid.\n\n## Execution Steps\n\n1. **Read existing ARCHITECTURE.md**\n   - If `ARCHITECTURE.md` exists at the project root, read it first\n   - This helps preserve any existing documentation and allows you to update rather than overwrite\n\n2. **Scan project structure**\n   - Use Glob to find major directories: `find . -maxdepth 2 -type d -not -path '*\u002F\\.*' -not -path '*\u002Fnode_modules\u002F*' -not -path '*\u002F__pycache__\u002F*'`\n   - For each top-level directory (src\u002F, lib\u002F, app\u002F, components\u002F, etc.), identify:\n     - What it contains (modules, libraries, features)\n     - Its primary responsibility\n     - Key files or sub-modules within it\n\n3. **Identify modules and dependencies**\n   - Scan key files with Grep\u002FRead to understand module structure\n   - Map logical dependencies (imports, API calls, shared state)\n   - Identify which modules depend on which others\n   - Look for: package.json, setup.py, .go files, main entry points\n\n4. **Generate Mermaid diagram**\n   - Create a `graph TD` (top-down) Mermaid diagram showing:\n     - Each major module as a node (use clear, short names)\n     - Arrows showing dependencies: `ModuleA --> ModuleB` means ModuleA imports\u002Fuses ModuleB\n     - Group related modules if they form a subsystem\n   - Keep the diagram readable (max ~10-15 nodes for clarity)\n   - Example structure:\n     ```\n     graph TD\n       API[\"API Layer\"]\n       DB[\"Database\"]\n       Auth[\"Authentication\"]\n       UI[\"Frontend\"]\n\n       UI --> API\n       API --> Auth\n       API --> DB\n       Auth --> DB\n     ```\n\n5. **Write ARCHITECTURE.md**\n   - Create or update `ARCHITECTURE.md` at the project root\n   - **Structure**:\n     ```markdown\n     # Project Architecture\n\n     ## Overview\n     [1-2 sentence high-level description of what the project does]\n\n     ## Directory Structure\n\n     ### src\u002F\n     [Description of what this directory contains]\n     - Key files: file1.ts, file2.ts\n\n     ### lib\u002F\n     [Description]\n     - Key files: ...\n\n     [... repeat for each top-level directory ...]\n\n     ## Module Relationships\n\n     ```mermaid\n     [Your generated Mermaid graph]\n     ```\n\n     ## Key Components\n\n     ### Module Name\n     - **Location**: src\u002Fmodule\u002F\n     - **Responsibility**: What this module does\n     - **Exports**: Key functions\u002Fclasses\n     - **Depends on**: Other modules it uses\n\n     [... repeat for each major module ...]\n\n     ## Data Flow\n     [Optional: describe how data flows through the system, if applicable]\n     ```\n   - Keep descriptions concise (1-3 lines per section)\n   - Focus on \"why\" not \"what\" — what problem does each module solve?\n\n6. **Report success**\n   - Tell the user: \"Updated ARCHITECTURE.md\"\n   - If the diagram is complex, add a note about what the diagram shows\n\n## Implementation Notes\n\n- **Diagram scope**: Show the 5-10 most important modules, not every single file\n- **Avoid noise**: Don't include vendored code (node_modules, venv, .git)\n- **Update strategy**: If ARCHITECTURE.md exists, preserve existing descriptions and update the diagram + file list\n- **Language**: Use English for all documentation\n- **Mermaid syntax**: Use valid Mermaid graph TD syntax; test the diagram visually if possible\n\n## Success Criteria\n\n✓ ARCHITECTURE.md exists at project root\n✓ Diagram renders without syntax errors\n✓ All major modules are represented\n✓ Dependencies are correctly shown\n✓ Descriptions are clear and concise\n\n\n---\n\n## Completion Status\n\n- ✅ **DONE** — task completed successfully\n- ⚠ **DONE_WITH_CONCERNS** — completed but with caveats to note\n- ❌ **BLOCKED** — cannot proceed; write details to `.clade\u002Fblockers.md`\n- ❓ **NEEDS_CONTEXT** — missing information; use AskUserQuestion\n\n**3-strike rule:** If the same approach fails 3 times, switch to BLOCKED — do not retry indefinitely.\n\n## Delivery completion\n\nIf this workflow changes files or external state:\n\n- Inspect the real final state before responding, including `git status` for a\n  repository task.\n- Never report `DONE` while task-owned changes are uncommitted. Use or continue\n  `$clade:delivery` and create a repository-compliant checkpoint or preserve\n  the work when committing is unavailable.\n- When the user request or trusted repository policy makes publication,\n  deployment, or live verification part of the task, do not silently downgrade\n  the result to local-only work.\n- If a required delivery transition lacks authority, credentials, a destination,\n  or reachable external state, report `BLOCKED` or `NEEDS_CONTEXT` rather than\n  appending a \"not committed\u002Fpushed\u002Fdeployed\" caveat after `DONE`.\n","# Clade for Codex\n\nThis workflow runs **directly in Codex**. Do not launch the `claude` CLI or\ndelegate the workflow to Clade's MCP bridge.\n\nCodex compatibility rules:\n\n- Plugin skills are namespaced. Invoke this workflow explicitly as\n  `$clade:map`; a bare `$name` does not select the installed Clade plugin.\n- Read the nearest `AGENTS.md` files for repository instructions. If a project\n  has only `CLAUDE.md`, treat it as legacy project guidance and read it too.\n- Store new Clade working state under `.clade\u002F` (or `~\u002F.clade\u002F` for personal\n  state). Existing legacy Claude state may be read for migration, but do not\n  create new vendor-specific state.\n- A `\u002Fskill-name` reference means the corresponding Codex\n  `$clade:skill-name` plugin skill, or the same workflow invoked naturally when\n  explicit skill invocation is not available.\n- Use Codex web, file, shell, image, and subagent capabilities when the source\n  workflow names a vendor-specific tool. If a capability is unavailable, use\n  the documented fallback instead of spawning another agent CLI.\n- Paths such as `\u003Cplugin-root>\u002F...` are relative to the installed Clade plugin\n  containing this `SKILL.md`; resolve that root before invoking a helper.\n\n## Canonical Clade workflow\n\n# \u002Fmap Skill: Generate Project Architecture Diagram\n\n## Purpose\nAutomatically scan the project structure and generate `ARCHITECTURE.md` with a module relationship diagram using Mermaid.\n\n## Execution Steps\n\n1. **Read existing ARCHITECTURE.md**\n   - If `ARCHITECTURE.md` exists at the project root, read it first\n   - This helps preserve any existing documentation and allows you to update rather than overwrite\n\n2. **Scan project structure**\n   - Use Glob to find major directories: `find . -maxdepth 2 -type d -not -path '*\u002F\\.*' -not -path '*\u002Fnode_modules\u002F*' -not -path '*\u002F__pycache__\u002F*'`\n   - For each top-level directory (src\u002F, lib\u002F, app\u002F, components\u002F, etc.), identify:\n     - What it contains (modules, libraries, features)\n     - Its primary responsibility\n     - Key files or sub-modules within it\n\n3. **Identify modules and dependencies**\n   - Scan key files with Grep\u002FRead to understand module structure\n   - Map logical dependencies (imports, API calls, shared state)\n   - Identify which modules depend on which others\n   - Look for: package.json, setup.py, .go files, main entry points\n\n4. **Generate Mermaid diagram**\n   - Create a `graph TD` (top-down) Mermaid diagram showing:\n     - Each major module as a node (use clear, short names)\n     - Arrows showing dependencies: `ModuleA --> ModuleB` means ModuleA imports\u002Fuses ModuleB\n     - Group related modules if they form a subsystem\n   - Keep the diagram readable (max ~10-15 nodes for clarity)\n   - Example structure:\n     ```\n     graph TD\n       API[\"API Layer\"]\n       DB[\"Database\"]\n       Auth[\"Authentication\"]\n       UI[\"Frontend\"]\n\n       UI --> API\n       API --> Auth\n       API --> DB\n       Auth --> DB\n     ```\n\n5. **Write ARCHITECTURE.md**\n   - Create or update `ARCHITECTURE.md` at the project root\n   - **Structure**:\n     ```markdown\n     # Project Architecture\n\n     ## Overview\n     [1-2 sentence high-level description of what the project does]\n\n     ## Directory Structure\n\n     ### src\u002F\n     [Description of what this directory contains]\n     - Key files: file1.ts, file2.ts\n\n     ### lib\u002F\n     [Description]\n     - Key files: ...\n\n     [... repeat for each top-level directory ...]\n\n     ## Module Relationships\n\n     ```mermaid\n     [Your generated Mermaid graph]\n     ```\n\n     ## Key Components\n\n     ### Module Name\n     - **Location**: src\u002Fmodule\u002F\n     - **Responsibility**: What this module does\n     - **Exports**: Key functions\u002Fclasses\n     - **Depends on**: Other modules it uses\n\n     [... repeat for each major module ...]\n\n     ## Data Flow\n     [Optional: describe how data flows through the system, if applicable]\n     ```\n   - Keep descriptions concise (1-3 lines per section)\n   - Focus on \"why\" not \"what\" — what problem does each module solve?\n\n6. **Report success**\n   - Tell the user: \"Updated ARCHITECTURE.md\"\n   - If the diagram is complex, add a note about what the diagram shows\n\n## Implementation Notes\n\n- **Diagram scope**: Show the 5-10 most important modules, not every single file\n- **Avoid noise**: Don't include vendored code (node_modules, venv, .git)\n- **Update strategy**: If ARCHITECTURE.md exists, preserve existing descriptions and update the diagram + file list\n- **Language**: Use English for all documentation\n- **Mermaid syntax**: Use valid Mermaid graph TD syntax; test the diagram visually if possible\n\n## Success Criteria\n\n✓ ARCHITECTURE.md exists at project root\n✓ Diagram renders without syntax errors\n✓ All major modules are represented\n✓ Dependencies are correctly shown\n✓ Descriptions are clear and concise\n\n\n---\n\n## Completion Status\n\n- ✅ **DONE** — task completed successfully\n- ⚠ **DONE_WITH_CONCERNS** — completed but with caveats to note\n- ❌ **BLOCKED** — cannot proceed; write details to `.clade\u002Fblockers.md`\n- ❓ **NEEDS_CONTEXT** — missing information; use AskUserQuestion\n\n**3-strike rule:** If the same approach fails 3 times, switch to BLOCKED — do not retry indefinitely.\n\n## Delivery completion\n\nIf this workflow changes files or external state:\n\n- Inspect the real final state before responding, including `git status` for a\n  repository task.\n- Never report `DONE` while task-owned changes are uncommitted. Use or continue\n  `$clade:delivery` and create a repository-compliant checkpoint or preserve\n  the work when committing is unavailable.\n- When the user request or trusted repository policy makes publication,\n  deployment, or live verification part of the task, do not silently downgrade\n  the result to local-only work.\n- If a required delivery transition lacks authority, credentials, a destination,\n  or reachable external state, report `BLOCKED` or `NEEDS_CONTEXT` rather than\n  appending a \"not committed\u002Fpushed\u002Fdeployed\" caveat after `DONE`.\n",{"name":5,"description":7},"main","bb20646cb013d2f52f854743fcee83dcc5ccfbd9","plugins\u002Fclade\u002Fskills\u002Fmap",6,"https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade","https:\u002F\u002Falexshen.dev\u002Fen\u002Fblog\u002Fclade","https:\u002F\u002Fgithub.com\u002Fshenxingy","https:\u002F\u002Falexshen.dev\u002F","Founding Engineer @ Scam AI | ECE @ Duke University | Data Science @ Duke Kunshan University","2026-11-13 19:38:31",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add shenxingy\u002FClade --skill map",{"tool":60,"command":61},"bunx","bunx skills add shenxingy\u002FClade --skill map",{"tool":63,"command":64},"pnpm","pnpm dlx skills add shenxingy\u002FClade --skill map","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fmap\u002FSKILL.md",true,[],[69,87,120,140,165,182],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":76,"publishedAt":39},"01M6FNPBA3494GF2W7V4MMAKG3","worktree","Create or inspect runtime-adaptive isolated Git workspaces with explicit ownership and delivery routing","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fworktree\u002FSKILL.md",[75],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[71,77,78,36,79,80,81,82,83,84,85,86],"adaptive","inspect","ownership","delivery routing","runtime","delivery","workspaces","git","routing","create",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":99,"publishedAt":39},"01M6FNP75BY8CS006EWGN29FM0","web-search","Route online research and URL reading to native tools or TinyFish MCP\u002FAPI; prepare targeted requests, handle progress and failures, and check returned evidence. Applies to web search, fetching, and bulk collection; excludes repository\u002Ffile search.","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fweb-search\u002FSKILL.md",[93,94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"web search","search","web","repository","file","research","MCP","requests","collection","reading","URL","native","bulk","progress","file search","route","tinyfish","evidence","check","api",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":39},"01M6FNP2616DRTZRSZJQM3HPHY","verify","Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Codex built-in \u002Fverify (which runs the app to observe a single change working) — this one walks the AGENTS.md \"Features (Behavior Anchors)\" list.","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fverify\u002FSKILL.md",[126],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[122,128,129,130,131,132,133,34,134,135,136,137,138,139],"app","single","features","which","interaction","tests","observe","autonomous","behavior","list","change","codex",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":39},"01M6FNNX95R9H29BNERFY15704","tasks","Coordinate dependency-aware project tasks across independent Codex, Codex, Kimi and human sessions using Beads. Use for shared plans, claiming work, task handoffs, acceptance and agent monitoring snapshots.","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Ftasks\u002FSKILL.md",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,148,149,150,34,151,152,153,154,155,156,157,158,159,30,160,161,162,163,164,139],"for","plans","work","shared","across","human","task","coordinate","kimi","snapshots","agent monitoring","dependency","using beads","beads","monitoring","acceptance","sessions",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":39},"01M6FNNTAD1BCZX5Q9TC55MZCH","sync","End-of-session documentation sync — updates TODO.md and PROGRESS.md only (run \u002Fcommit after to commit everything)","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fsync\u002FSKILL.md",[171],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[167,173,174,175,176,177,178,179,113,180,181],"session","run","documentation","commit","only","documentation sync","updates","end","todo",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":39},"01M6FNNPTR5H23MD3849E66WYA","status","Show a provider-neutral, freshness-aware snapshot of active Agent work, Git delivery, execution identity, and usage limits. Use for “what's going on right now”, what is running, progress updates, active runtime\u002Fprovider\u002Fmodel, or stuck-work checks.","https:\u002F\u002Fgithub.com\u002Fshenxingy\u002FClade\u002Fblob\u002Fmain\u002Fplugins\u002Fclade\u002Fskills\u002Fstatus\u002FSKILL.md",[188],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[184,81,190,191,148,179,192,193,113,194,82,195,196,30,197,150,198,199,84,200],"running","limits","usage","now","active","show","provider","snapshot","model","execution","identity"]