[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EQEH8F04FK46BEGAJ798AX":3,"skill-same:01M7EQEH8F04FK46BEGAJ798AX":48},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7EQEH8F04FK46BEGAJ798AX","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.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcontent-writing\u002Fwiki-onboarding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ncategory: content-writing\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: critical\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## Example\n\n**User request:**\n\n> Create onboarding documentation that helps a new engineer run, understand, and safely change this codebase.\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## Example\n\n**User request:**\n\n> Create onboarding documentation that helps a new engineer run, understand, and safely change this codebase.\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":24,"source":25,"category":26,"date_added":27,"description":7},"critical","community","content-writing","2026-02-27","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcontent-writing\u002Fwiki-onboarding","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill wiki-onboarding",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill wiki-onboarding",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill wiki-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcontent-writing\u002Fwiki-onboarding\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":56},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":56},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":56},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]