[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SMY5MECYA7BP253JKE7CT":3,"skill-same:01M79SMY5MECYA7BP253JKE7CT":64},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M79SMY5MECYA7BP253JKE7CT","code-wiki",null,"Generate wiki docs + Mermaid diagrams for any codebase.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcode-wiki\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-wiki\ndescription: \"Generate wiki docs + Mermaid diagrams for any codebase.\"\nversion: 0.2.0\nauthor: Teknium (teknium1), Hermes Agent, ported for CrusorAI\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [documentation, mermaid, architecture, diagrams, wiki, code-analysis, onboarding]\n    related_skills: [codebase-inspection, codebase-map]\n---\n\n**Triggers:** wiki, document this codebase, architecture diagram, mermaid, generate docs, codebase documentation, onboarding docs, explain the architecture\n\n# Code Wiki\n\nGenerate a wiki for any codebase — overview, architecture, per-module deep-dives, Mermaid class and sequence diagrams. Uses only existing Crusor tools (`run_terminal`, `read_file`, `search_files`, `write_file`); no Docker, no external services, no extra dependencies.\n\nProduces **reference documentation** (what\u002Fhow) — not strategic narrative (why), not single-function explanations (just answer inline).\n\n## When to Use\n\n- \"Document this codebase\", \"generate a wiki\", \"make architecture diagrams\"\n- Onboarding to an unfamiliar repo as structured reference\n- A stable markdown+Mermaid artifact is wanted that renders on GitHub\n\nDo NOT use for: single-file\u002Ffunction docs (answer directly), repos the user is actively reshaping this session (answer as questions come).\n\n## Quick Reference\n\n| Step | Action |\n|---|---|\n| 1 | Resolve target — workspace root, given path, or `git clone --depth 50 \u003Curl>` to a temp dir |\n| 2 | Scan structure — `ls`, `find -maxdepth 3`, manifest files, README |\n| 3 | Pick 8–10 modules to document |\n| 4 | Write `README.md` (overview + module map) |\n| 5 | Write `architecture.md` with Mermaid flowchart |\n| 6 | Write per-module docs in `modules\u002F` |\n| 7 | Write `diagrams\u002Fclass-diagram.md` (Mermaid classDiagram) |\n| 8 | Write `diagrams\u002Fsequences.md` (2–4 key workflow sequenceDiagrams) |\n| 9 | Write `getting-started.md` (+ `api.md` if applicable) |\n| 10 | Report paths to the user |\n\nDefault output: `~\u002F.crusorai\u002Fwikis\u002F\u003Crepo-name>\u002F`. Write INTO the repo (`docs\u002Fwiki\u002F`) only when the user explicitly requests it.\n\n## Procedure\n\n```bash\nREPO_SHA=$(git rev-parse HEAD 2>\u002Fdev\u002Fnull || echo \"uncommitted\")\nOUTPUT_DIR=\"$HOME\u002F.crusorai\u002Fwikis\u002F$(basename $PWD)\"\nmkdir -p \"$OUTPUT_DIR\u002Fmodules\" \"$OUTPUT_DIR\u002Fdiagrams\"\n```\n\nScan with `run_terminal` (`find . -maxdepth 3 -type f | grep -v node_modules | head -80`), read READMEs and entrypoints with `read_file`, map structure with `search_files`. Record the commit SHA in the wiki header — docs rot, the SHA dates them.\n\n## Quality Bars\n\n- **Modules are mental units** (runtime, bridge, ui), not folder dumps; say what each module is FOR in one sentence before any detail.\n- **Mermaid diagrams must render**: keep node labels quoted, no raw `-->` inside labels, one diagram per concern. If a diagram is >15 nodes, split it.\n- Sequence diagrams follow REAL call paths you verified in code — file:line references in the doc body, not in the diagram.\n- Every claim about behavior cites a file you actually read this session.\n- Prefer tables for inventories (endpoints, commands, config keys); prose only for relationships.\n\n## Invariants\n\n- Never modify source code while generating a wiki (read-only task, `write_file` only into the output dir).\n- One session = one repo; if the target changes, restart the wiki.\n- Report output paths at the end; offer `getting-started.md` as the entry point.\n","**Triggers:** wiki, document this codebase, architecture diagram, mermaid, generate docs, codebase documentation, onboarding docs, explain the architecture\n\n# Code Wiki\n\nGenerate a wiki for any codebase — overview, architecture, per-module deep-dives, Mermaid class and sequence diagrams. Uses only existing Crusor tools (`run_terminal`, `read_file`, `search_files`, `write_file`); no Docker, no external services, no extra dependencies.\n\nProduces **reference documentation** (what\u002Fhow) — not strategic narrative (why), not single-function explanations (just answer inline).\n\n## When to Use\n\n- \"Document this codebase\", \"generate a wiki\", \"make architecture diagrams\"\n- Onboarding to an unfamiliar repo as structured reference\n- A stable markdown+Mermaid artifact is wanted that renders on GitHub\n\nDo NOT use for: single-file\u002Ffunction docs (answer directly), repos the user is actively reshaping this session (answer as questions come).\n\n## Quick Reference\n\n| Step | Action |\n|---|---|\n| 1 | Resolve target — workspace root, given path, or `git clone --depth 50 \u003Curl>` to a temp dir |\n| 2 | Scan structure — `ls`, `find -maxdepth 3`, manifest files, README |\n| 3 | Pick 8–10 modules to document |\n| 4 | Write `README.md` (overview + module map) |\n| 5 | Write `architecture.md` with Mermaid flowchart |\n| 6 | Write per-module docs in `modules\u002F` |\n| 7 | Write `diagrams\u002Fclass-diagram.md` (Mermaid classDiagram) |\n| 8 | Write `diagrams\u002Fsequences.md` (2–4 key workflow sequenceDiagrams) |\n| 9 | Write `getting-started.md` (+ `api.md` if applicable) |\n| 10 | Report paths to the user |\n\nDefault output: `~\u002F.crusorai\u002Fwikis\u002F\u003Crepo-name>\u002F`. Write INTO the repo (`docs\u002Fwiki\u002F`) only when the user explicitly requests it.\n\n## Procedure\n\n```bash\nREPO_SHA=$(git rev-parse HEAD 2>\u002Fdev\u002Fnull || echo \"uncommitted\")\nOUTPUT_DIR=\"$HOME\u002F.crusorai\u002Fwikis\u002F$(basename $PWD)\"\nmkdir -p \"$OUTPUT_DIR\u002Fmodules\" \"$OUTPUT_DIR\u002Fdiagrams\"\n```\n\nScan with `run_terminal` (`find . -maxdepth 3 -type f | grep -v node_modules | head -80`), read READMEs and entrypoints with `read_file`, map structure with `search_files`. Record the commit SHA in the wiki header — docs rot, the SHA dates them.\n\n## Quality Bars\n\n- **Modules are mental units** (runtime, bridge, ui), not folder dumps; say what each module is FOR in one sentence before any detail.\n- **Mermaid diagrams must render**: keep node labels quoted, no raw `-->` inside labels, one diagram per concern. If a diagram is >15 nodes, split it.\n- Sequence diagrams follow REAL call paths you verified in code — file:line references in the doc body, not in the diagram.\n- Every claim about behavior cites a file you actually read this session.\n- Prefer tables for inventories (endpoints, commands, config keys); prose only for relationships.\n\n## Invariants\n\n- Never modify source code while generating a wiki (read-only task, `write_file` only into the output dir).\n- One session = one repo; if the target changes, restart the wiki.\n- Report output paths at the end; offer `getting-started.md` as the entry point.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":39,"description":7},"Teknium (teknium1), Hermes Agent, ported for CrusorAI","0.2.0",{"hermes":27},{"tags":28,"related_skills":36},[29,30,31,32,33,34,35],"documentation","mermaid","architecture","diagrams","wiki","code-analysis","onboarding",[37,38],"codebase-inspection","codebase-map",[40,41,42],"linux","macos","windows","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcode-wiki","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill code-wiki",{"tool":56,"command":57},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill code-wiki",{"tool":59,"command":60},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill code-wiki","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcode-wiki\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]