[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ATFBKBW3PWFBFPHXTS0EE":3,"skill-same:01M72ATFBKBW3PWFBFPHXTS0EE":46},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M72ATFBKBW3PWFBFPHXTS0EE","wiki-onboarding",null,"Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs \u002Fdeep-wiki, or user wants to help new team members understand a codebase.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fwiki-onboarding\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: wiki-onboarding\ndescription: \"Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs \u002Fdeep-wiki, or user wants to help new team members understand a codebase.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Wiki Onboarding Guide Generator\n\nGenerate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase.\n\n## When to Use\n- User asks for onboarding docs or getting-started guides\n- User runs `\u002Fdeep-wiki:onboard` command\n- User wants to help new team members understand a codebase\n\n## Language Detection\n\nScan the repository for build files to determine the primary language for code examples:\n- `package.json` \u002F `tsconfig.json` → TypeScript\u002FJavaScript\n- `*.csproj` \u002F `*.sln` → C# \u002F .NET\n- `Cargo.toml` → Rust\n- `pyproject.toml` \u002F `setup.py` \u002F `requirements.txt` → Python\n- `go.mod` → Go\n- `pom.xml` \u002F `build.gradle` → Java\n\n## Guide 1: Principal-Level Onboarding\n\n**Audience**: Senior\u002Fstaff+ engineers who need the \"why\" behind decisions.\n\n### Required Sections\n\n1. **System Philosophy & Design Principles** — What invariants does the system maintain? What were the key design choices and why?\n2. **Architecture Overview** — Component map with Mermaid diagram. What owns what, communication patterns.\n3. **Key Abstractions & Interfaces** — The load-bearing abstractions everything depends on\n4. **Decision Log** — Major architectural decisions with context, alternatives considered, trade-offs\n5. **Dependency Rationale** — Why each major dependency was chosen, what it replaced\n6. **Data Flow & State** — How data moves through the system (traced from actual code, not guessed)\n7. **Failure Modes & Error Handling** — What breaks, how errors propagate, recovery patterns\n8. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths\n9. **Security Model** — Auth, authorization, trust boundaries, data sensitivity\n10. **Testing Strategy** — What's tested, what isn't, testing philosophy\n11. **Operational Concerns** — Deployment, monitoring, feature flags, configuration\n12. **Known Technical Debt** — Honest assessment of shortcuts and their risks\n\n### Rules\n- Every claim backed by `(file_path:line_number)` citation\n- Minimum 3 Mermaid diagrams (architecture, data flow, dependency graph)\n- All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)\n- Focus on WHY decisions were made, not just WHAT exists\n\n## Guide 2: Zero-to-Hero Contributor Guide\n\n**Audience**: New contributors who need step-by-step practical guidance.\n\n### Required Sections\n\n1. **What This Project Does** — 2-3 sentence elevator pitch\n2. **Prerequisites** — Tools, versions, accounts needed\n3. **Environment Setup** — Step-by-step with exact commands, expected output at each step\n4. **Project Structure** — Annotated directory tree (what lives where and why)\n5. **Your First Task** — End-to-end walkthrough of adding a simple feature\n6. **Development Workflow** — Branch strategy, commit conventions, PR process\n7. **Running Tests** — How to run tests, what to test, how to add a test\n8. **Debugging Guide** — Common issues and how to diagnose them\n9. **Key Concepts** — Domain-specific terminology explained with code examples\n10. **Code Patterns** — \"If you want to add X, follow this pattern\" templates\n11. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them\n12. **Where to Get Help** — Communication channels, documentation, key contacts\n13. **Glossary** — Terms used in the codebase that aren't obvious\n14. **Quick Reference Card** — Cheat sheet of most-used commands and patterns\n\n### Rules\n- All code examples in the detected primary language\n- Every command must be copy-pasteable\n- Include expected output for verification steps\n- Use Mermaid for workflow diagrams (dark-mode colors)\n- Ground all claims in actual code — cite `(file_path:line_number)`\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Wiki Onboarding Guide Generator\n\nGenerate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase.\n\n## When to Use\n- User asks for onboarding docs or getting-started guides\n- User runs `\u002Fdeep-wiki:onboard` command\n- User wants to help new team members understand a codebase\n\n## Language Detection\n\nScan the repository for build files to determine the primary language for code examples:\n- `package.json` \u002F `tsconfig.json` → TypeScript\u002FJavaScript\n- `*.csproj` \u002F `*.sln` → C# \u002F .NET\n- `Cargo.toml` → Rust\n- `pyproject.toml` \u002F `setup.py` \u002F `requirements.txt` → Python\n- `go.mod` → Go\n- `pom.xml` \u002F `build.gradle` → Java\n\n## Guide 1: Principal-Level Onboarding\n\n**Audience**: Senior\u002Fstaff+ engineers who need the \"why\" behind decisions.\n\n### Required Sections\n\n1. **System Philosophy & Design Principles** — What invariants does the system maintain? What were the key design choices and why?\n2. **Architecture Overview** — Component map with Mermaid diagram. What owns what, communication patterns.\n3. **Key Abstractions & Interfaces** — The load-bearing abstractions everything depends on\n4. **Decision Log** — Major architectural decisions with context, alternatives considered, trade-offs\n5. **Dependency Rationale** — Why each major dependency was chosen, what it replaced\n6. **Data Flow & State** — How data moves through the system (traced from actual code, not guessed)\n7. **Failure Modes & Error Handling** — What breaks, how errors propagate, recovery patterns\n8. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths\n9. **Security Model** — Auth, authorization, trust boundaries, data sensitivity\n10. **Testing Strategy** — What's tested, what isn't, testing philosophy\n11. **Operational Concerns** — Deployment, monitoring, feature flags, configuration\n12. **Known Technical Debt** — Honest assessment of shortcuts and their risks\n\n### Rules\n- Every claim backed by `(file_path:line_number)` citation\n- Minimum 3 Mermaid diagrams (architecture, data flow, dependency graph)\n- All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)\n- Focus on WHY decisions were made, not just WHAT exists\n\n## Guide 2: Zero-to-Hero Contributor Guide\n\n**Audience**: New contributors who need step-by-step practical guidance.\n\n### Required Sections\n\n1. **What This Project Does** — 2-3 sentence elevator pitch\n2. **Prerequisites** — Tools, versions, accounts needed\n3. **Environment Setup** — Step-by-step with exact commands, expected output at each step\n4. **Project Structure** — Annotated directory tree (what lives where and why)\n5. **Your First Task** — End-to-end walkthrough of adding a simple feature\n6. **Development Workflow** — Branch strategy, commit conventions, PR process\n7. **Running Tests** — How to run tests, what to test, how to add a test\n8. **Debugging Guide** — Common issues and how to diagnose them\n9. **Key Concepts** — Domain-specific terminology explained with code examples\n10. **Code Patterns** — \"If you want to add X, follow this pattern\" templates\n11. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them\n12. **Where to Get Help** — Communication channels, documentation, key contacts\n13. **Glossary** — Terms used in the codebase that aren't obvious\n14. **Quick Reference Card** — Cheat sheet of most-used commands and patterns\n\n### Rules\n- All code examples in the detected primary language\n- Every command must be copy-pasteable\n- Include expected output for verification steps\n- Use Mermaid for workflow diagrams (dark-mode colors)\n- Ground all claims in actual code — cite `(file_path:line_number)`\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":23,"source":24,"date_added":25,"description":7},"unknown","community","2026-02-27","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fwiki-onboarding","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Sansar35\u002Fclaude-agent --skill wiki-onboarding",{"tool":38,"command":39},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill wiki-onboarding",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill wiki-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fwiki-onboarding\u002FSKILL.md",true,[],[47,54,61,68,75,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]