[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F3CPC5VP20BJPA81RFMTD":3,"skill-same:01M73F3CPC5VP20BJPA81RFMTD":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M73F3CPC5VP20BJPA81RFMTD","wiki-onboarding",null,"Generates four audience-tailored onboarding guides in an onboarding\u002F folder — Contributor, Staff Engineer, Executive, and Product Manager. Use when the user wants onboarding documentation for a codebase.","qhjqhj00\u002Fresearch-skills-pool","qhjqhj00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29684092?v=4","01M72AE0ZGXVM5C57N512DGQG8","Tommy Chien","01M72AE107ESJMHT7QC5SXX144",3,"MIT","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-onboarding\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wiki-onboarding\ndescription: Generates four audience-tailored onboarding guides in an onboarding\u002F folder — Contributor, Staff Engineer, Executive, and Product Manager. Use when the user wants onboarding documentation for a codebase.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# Wiki Onboarding Guide Generator\n\nGenerate four audience-tailored onboarding documents in an `onboarding\u002F` folder, each giving a different stakeholder exactly the understanding they need.\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating any guides, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## When to Activate\n\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## Output Structure\n\nGenerate an `onboarding\u002F` folder with these files:\n\n```\nonboarding\u002F\n├── index.md                    # Onboarding hub — links to all 4 guides with audience descriptions\n├── contributor-guide.md        # For new contributors (assumes Python or JS background)\n├── staff-engineer-guide.md     # For staff\u002Fprincipal engineers\n├── executive-guide.md          # For VP\u002Fdirector-level engineering leaders\n└── product-manager-guide.md    # For product managers and non-engineering stakeholders\n```\n\n### `index.md` — Onboarding Hub\n\nA landing page with:\n- **One-paragraph project summary**\n- **Guide selector table**:\n\n| Guide | Audience | What You'll Learn | Time |\n|-------|----------|-------------------|------|\n| [Contributor Guide](.\u002Fcontributor-guide.md) | New contributors with Python\u002FJS experience | Setup, first PR, codebase patterns | ~30 min |\n| [Staff Engineer Guide](.\u002Fstaff-engineer-guide.md) | Staff\u002Fprincipal engineers | Architecture, design decisions, system boundaries | ~45 min |\n| [Executive Guide](.\u002Fexecutive-guide.md) | VP\u002Fdirectors of engineering | Capabilities, risks, team topology, investment thesis | ~20 min |\n| [Product Manager Guide](.\u002Fproduct-manager-guide.md) | Product managers | Features, user journeys, constraints, data model | ~20 min |\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---\n\n## Guide 1: Contributor Guide\n\n**File**: `onboarding\u002Fcontributor-guide.md`\n**Audience**: Engineers joining the project. Assumes proficiency in Python or JavaScript and general software engineering experience.\n**Length**: 1000–2500 lines. Progressive — each section builds on the last.\n\n### Required Sections\n\n**Part I: Foundations** (skip if repo uses Python or JS)\n1. **{Primary Language} for Python\u002FJS Engineers** — Syntax comparison tables, async model, collections, type system, package management. Concrete code side-by-side, NOT abstract descriptions.\n2. **{Primary Framework} Essentials** — Compare to equivalent Python\u002FJS frameworks (e.g., FastAPI, Express). Request pipeline, routing, DI, config.\n\n**Part II: This Codebase**\n3. **What This Project Does** — 2-3 sentence elevator pitch\n4. **Project Structure** — Annotated directory tree (what lives where and why). Include `graph TB` architecture overview.\n5. **Core Concepts** — Domain-specific terminology explained with code examples. Use `erDiagram` for data model.\n6. **Request Lifecycle** — `sequenceDiagram` (with `autonumber`) tracing a typical request end-to-end.\n7. **Key Patterns** — \"If you want to add X, follow this pattern\" templates with real code\n\n**Part III: Getting Productive**\n8. **Prerequisites & Setup** — Table: Tool, Version, Install Command. Step-by-step with expected output at each step.\n9. **Your First Task** — End-to-end walkthrough of adding a simple feature\n10. **Development Workflow** — Branch strategy, commit conventions, PR process. Use `flowchart` diagram.\n11. **Running Tests** — All tests, single file, single test, coverage commands\n12. **Debugging Guide** — Common issues table: Symptom, Cause, Fix\n13. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them\n\n**Appendices**\n- **Glossary** (40+ terms)\n- **Key File Reference** — Table: Path, Purpose, Why It Matters, Source\n- **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 with expected output\n- **Minimum 5 Mermaid diagrams** (architecture, ER, sequence, flowchart, state)\n- Use Mermaid for workflow diagrams (dark-mode colors) — add `\u003C!-- Sources: ... -->` comment block after each\n- Ground all claims in actual code — cite using linked format\n\n---\n\n## Guide 2: Staff Engineer Guide\n\n**File**: `onboarding\u002Fstaff-engineer-guide.md`\n**Audience**: Staff\u002Fprincipal engineers who need the \"why\" behind every decision. Deep systems experience, may not know this repo's language.\n**Length**: 800–1200 lines. Dense, opinionated, architectural.\n\n### Required Sections\n\n1. **Executive Summary** — What the system is in one dense paragraph. What it owns vs delegates.\n2. **The Core Architectural Insight** — The SINGLE most important concept. Include pseudocode in a DIFFERENT language from the repo.\n3. **System Architecture** — Full Mermaid `graph TB` diagram. Call out the \"heart\" of the system.\n4. **Domain Model** — Mermaid `erDiagram` of core entities. Data invariants table: Entity, Invariant, Enforced By, Source.\n5. **Key Abstractions & Interfaces** — `classDiagram` showing load-bearing abstractions.\n6. **Request Lifecycle** — `sequenceDiagram` (with `autonumber`) showing typical request from entry to response.\n7. **State Transitions** — `stateDiagram-v2` for entities with meaningful lifecycle states.\n8. **Decision Log** — Table: Decision, Alternatives Considered, Rationale, Source.\n9. **Dependency Rationale** — Table: Dependency, Purpose, What It Replaced, Source.\n10. **Data Flow & State** — How data moves through the system. Storage comparison table.\n11. **Failure Modes & Error Handling** — `flowchart` for error propagation paths.\n12. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths.\n13. **Security Model** — Auth, authorization, trust boundaries, data sensitivity.\n14. **Testing Strategy** — What's tested, what isn't, testing philosophy.\n15. **Known Technical Debt** — Table: Issue, Risk Level, Affected Files, Source.\n16. **Where to Go Deep** — Recommended reading order of source files, links to wiki sections.\n\n### Rules\n- Use **pseudocode in a different language** to explain concepts\n- Use **comparison tables** to map unfamiliar concepts (e.g., `Task\u003CT>` = `Awaitable[T]`)\n- Dense prose with tables, NOT shallow bullet lists\n- Every claim backed by linked citation\n- **Minimum 5 Mermaid diagrams** (architecture, ER, class, sequence, state, flowchart)\n- Each diagram followed by `\u003C!-- Sources: ... -->` comment block\n- **Use tables aggressively** — decisions, dependencies, debt should ALL be tables with Source columns\n- Focus on WHY decisions were made, not just WHAT exists\n\n---\n\n## Guide 3: Executive Guide\n\n**File**: `onboarding\u002Fexecutive-guide.md`\n**Audience**: VP\u002Fdirector of engineering. Needs capability overview, risk assessment, and investment context — NOT code-level details.\n**Length**: 400–800 lines. Strategic, concise, decision-oriented.\n\n### Required Sections\n\n1. **System Overview** — What it does, who uses it, business value in 2-3 sentences\n2. **Capability Map** — Table: Capability, Status (Built\u002FPartial\u002FPlanned), Maturity, Dependencies. What the system can and cannot do today.\n3. **Architecture at a Glance** — High-level Mermaid `graph LR` diagram. Services, data stores, external integrations — NO internal code details. Focus on deployment units and team boundaries.\n4. **Team Topology** — Which team\u002Fperson owns which components. Table: Component, Owner, Criticality, Bus Factor.\n5. **Technology Investment Thesis** — Why these technologies were chosen. Table: Technology, Purpose, Alternatives Considered, Risk Level.\n6. **Risk Assessment** — Table: Risk, Likelihood, Impact, Mitigation, Owner. Cover reliability, security, scalability, compliance.\n7. **Cost & Scaling Model** — How costs scale with usage. What the bottlenecks are. When the next scaling investment is needed.\n8. **Dependency Map** — `graph TB` showing critical external dependencies. Table: Dependency, Type (Service\u002FLibrary\u002FPlatform), Risk if Unavailable.\n9. **Key Metrics & Observability** — What's measured, what dashboards exist, alerting coverage. Table: Metric, Current Value, Target, Source.\n10. **Roadmap Alignment** — Engineering workstreams mapped to business priorities. What's in progress, what's planned, what's blocked.\n11. **Technical Debt Summary** — Top 5 debt items with business impact. Table: Issue, Business Impact, Effort to Fix, Priority.\n12. **Recommendations** — 3-5 actionable recommendations for the next quarter, prioritized by impact.\n\n### Rules\n- **NO code snippets** — this guide is for engineering leaders, not coders\n- **Diagrams at service\u002Fteam level**, not class\u002Ffunction level\n- **Every claim backed by evidence** — cite wiki sections, architecture docs, or source files\n- **Minimum 3 Mermaid diagrams** (architecture overview, dependency map, capability\u002Froadmap)\n- Tables for every structured finding — this audience reads tables, not prose\n- **Business language** — translate technical concepts into impact (reliability, velocity, cost, risk)\n\n---\n\n## Guide 4: Product Manager Guide\n\n**File**: `onboarding\u002Fproduct-manager-guide.md`\n**Audience**: Product managers and non-engineering stakeholders. Needs to understand what the system does, what's possible, and where the boundaries are — NOT how it's built.\n**Length**: 400–800 lines. User-centric, feature-focused, constraint-aware.\n\n### Required Sections\n\n1. **What This System Does** — 2-3 sentence elevator pitch in user-facing language (no jargon)\n2. **User Journey Map** — Mermaid `graph LR` or `journey` diagram showing primary user flows through the system\n3. **Feature Capability Map** — Table: Feature, Status (Live\u002FBeta\u002FPlanned\u002FNot Possible), User-Facing Behavior, Limitations. Comprehensive map of what's built and what's not.\n4. **Data Model (Product View)** — Simplified Mermaid `erDiagram` showing entities users interact with. Explain in business terms (e.g., \"A Project has many Documents\" not \"FK relationship\").\n5. **Configuration & Feature Flags** — Table: Flag\u002FConfig, What It Controls, Default, Who Can Change It. What can be toggled without engineering work.\n6. **API Capabilities** — What integrations are possible. Table: Capability, Endpoint\u002FMethod, Authentication, Rate Limits. Written for integration partners, not developers.\n7. **Performance & SLAs** — Response times, throughput limits, availability targets. Table: Operation, Expected Latency, Throughput Limit, Current SLA.\n8. **Known Limitations & Constraints** — Honest list of what the system can't do or does poorly. Table: Limitation, User Impact, Workaround, Planned Fix.\n9. **Data & Privacy** — What data is collected, where it's stored, retention policies, compliance status. Table: Data Type, Storage Location, Retention, Compliance.\n10. **Glossary** — Domain terms explained in plain language (not engineering jargon)\n11. **FAQ** — 10+ common questions a PM would ask, answered concisely\n\n### Rules\n- **ZERO engineering jargon** — no \"middleware\", \"dependency injection\", \"ORM\". Use plain language.\n- **User-centric framing** — describe everything in terms of what users experience, not how code works\n- **Minimum 3 Mermaid diagrams** (user journey, data model, feature map\u002Fcapability overview)\n- Tables for every structured finding — PMs scan tables, not prose\n- If a technical concept must be mentioned, explain it in one sentence (e.g., \"Feature flags — toggles that let us turn features on\u002Foff without deploying code\")\n- Every claim grounded in evidence — cite wiki sections or source files for verification\n\n---\n\n## Mermaid Diagram Rules (ALL guides)\n\nALL diagrams must use dark-mode colors:\n- Node fills: `#2d333b`, borders: `#6d5dfc`, text: `#e6edf3`\n- Subgraph backgrounds: `#161b22`, borders: `#30363d`\n- Lines: `#8b949e`\n- If using inline `style` directives, use dark fills with `,color:#e6edf3`\n- Do NOT use `\u003Cbr\u002F>` in Mermaid labels (use `\u003Cbr>` or line breaks)\n\n## Validation\n\nAfter generating each guide, verify:\n- All file paths mentioned actually exist in the repo\n- All class\u002Fmethod names are accurate (not hallucinated)\n- Mermaid diagrams render (no syntax errors)\n- No bare HTML-like tags (generics like `List\u003CT>`) outside code fences — wrap in backticks\n- Each guide is appropriate for its audience — no code in Executive\u002FPM guides\n","# Wiki Onboarding Guide Generator\n\nGenerate four audience-tailored onboarding documents in an `onboarding\u002F` folder, each giving a different stakeholder exactly the understanding they need.\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating any guides, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## When to Activate\n\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## Output Structure\n\nGenerate an `onboarding\u002F` folder with these files:\n\n```\nonboarding\u002F\n├── index.md                    # Onboarding hub — links to all 4 guides with audience descriptions\n├── contributor-guide.md        # For new contributors (assumes Python or JS background)\n├── staff-engineer-guide.md     # For staff\u002Fprincipal engineers\n├── executive-guide.md          # For VP\u002Fdirector-level engineering leaders\n└── product-manager-guide.md    # For product managers and non-engineering stakeholders\n```\n\n### `index.md` — Onboarding Hub\n\nA landing page with:\n- **One-paragraph project summary**\n- **Guide selector table**:\n\n| Guide | Audience | What You'll Learn | Time |\n|-------|----------|-------------------|------|\n| [Contributor Guide](.\u002Fcontributor-guide.md) | New contributors with Python\u002FJS experience | Setup, first PR, codebase patterns | ~30 min |\n| [Staff Engineer Guide](.\u002Fstaff-engineer-guide.md) | Staff\u002Fprincipal engineers | Architecture, design decisions, system boundaries | ~45 min |\n| [Executive Guide](.\u002Fexecutive-guide.md) | VP\u002Fdirectors of engineering | Capabilities, risks, team topology, investment thesis | ~20 min |\n| [Product Manager Guide](.\u002Fproduct-manager-guide.md) | Product managers | Features, user journeys, constraints, data model | ~20 min |\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---\n\n## Guide 1: Contributor Guide\n\n**File**: `onboarding\u002Fcontributor-guide.md`\n**Audience**: Engineers joining the project. Assumes proficiency in Python or JavaScript and general software engineering experience.\n**Length**: 1000–2500 lines. Progressive — each section builds on the last.\n\n### Required Sections\n\n**Part I: Foundations** (skip if repo uses Python or JS)\n1. **{Primary Language} for Python\u002FJS Engineers** — Syntax comparison tables, async model, collections, type system, package management. Concrete code side-by-side, NOT abstract descriptions.\n2. **{Primary Framework} Essentials** — Compare to equivalent Python\u002FJS frameworks (e.g., FastAPI, Express). Request pipeline, routing, DI, config.\n\n**Part II: This Codebase**\n3. **What This Project Does** — 2-3 sentence elevator pitch\n4. **Project Structure** — Annotated directory tree (what lives where and why). Include `graph TB` architecture overview.\n5. **Core Concepts** — Domain-specific terminology explained with code examples. Use `erDiagram` for data model.\n6. **Request Lifecycle** — `sequenceDiagram` (with `autonumber`) tracing a typical request end-to-end.\n7. **Key Patterns** — \"If you want to add X, follow this pattern\" templates with real code\n\n**Part III: Getting Productive**\n8. **Prerequisites & Setup** — Table: Tool, Version, Install Command. Step-by-step with expected output at each step.\n9. **Your First Task** — End-to-end walkthrough of adding a simple feature\n10. **Development Workflow** — Branch strategy, commit conventions, PR process. Use `flowchart` diagram.\n11. **Running Tests** — All tests, single file, single test, coverage commands\n12. **Debugging Guide** — Common issues table: Symptom, Cause, Fix\n13. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them\n\n**Appendices**\n- **Glossary** (40+ terms)\n- **Key File Reference** — Table: Path, Purpose, Why It Matters, Source\n- **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 with expected output\n- **Minimum 5 Mermaid diagrams** (architecture, ER, sequence, flowchart, state)\n- Use Mermaid for workflow diagrams (dark-mode colors) — add `\u003C!-- Sources: ... -->` comment block after each\n- Ground all claims in actual code — cite using linked format\n\n---\n\n## Guide 2: Staff Engineer Guide\n\n**File**: `onboarding\u002Fstaff-engineer-guide.md`\n**Audience**: Staff\u002Fprincipal engineers who need the \"why\" behind every decision. Deep systems experience, may not know this repo's language.\n**Length**: 800–1200 lines. Dense, opinionated, architectural.\n\n### Required Sections\n\n1. **Executive Summary** — What the system is in one dense paragraph. What it owns vs delegates.\n2. **The Core Architectural Insight** — The SINGLE most important concept. Include pseudocode in a DIFFERENT language from the repo.\n3. **System Architecture** — Full Mermaid `graph TB` diagram. Call out the \"heart\" of the system.\n4. **Domain Model** — Mermaid `erDiagram` of core entities. Data invariants table: Entity, Invariant, Enforced By, Source.\n5. **Key Abstractions & Interfaces** — `classDiagram` showing load-bearing abstractions.\n6. **Request Lifecycle** — `sequenceDiagram` (with `autonumber`) showing typical request from entry to response.\n7. **State Transitions** — `stateDiagram-v2` for entities with meaningful lifecycle states.\n8. **Decision Log** — Table: Decision, Alternatives Considered, Rationale, Source.\n9. **Dependency Rationale** — Table: Dependency, Purpose, What It Replaced, Source.\n10. **Data Flow & State** — How data moves through the system. Storage comparison table.\n11. **Failure Modes & Error Handling** — `flowchart` for error propagation paths.\n12. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths.\n13. **Security Model** — Auth, authorization, trust boundaries, data sensitivity.\n14. **Testing Strategy** — What's tested, what isn't, testing philosophy.\n15. **Known Technical Debt** — Table: Issue, Risk Level, Affected Files, Source.\n16. **Where to Go Deep** — Recommended reading order of source files, links to wiki sections.\n\n### Rules\n- Use **pseudocode in a different language** to explain concepts\n- Use **comparison tables** to map unfamiliar concepts (e.g., `Task\u003CT>` = `Awaitable[T]`)\n- Dense prose with tables, NOT shallow bullet lists\n- Every claim backed by linked citation\n- **Minimum 5 Mermaid diagrams** (architecture, ER, class, sequence, state, flowchart)\n- Each diagram followed by `\u003C!-- Sources: ... -->` comment block\n- **Use tables aggressively** — decisions, dependencies, debt should ALL be tables with Source columns\n- Focus on WHY decisions were made, not just WHAT exists\n\n---\n\n## Guide 3: Executive Guide\n\n**File**: `onboarding\u002Fexecutive-guide.md`\n**Audience**: VP\u002Fdirector of engineering. Needs capability overview, risk assessment, and investment context — NOT code-level details.\n**Length**: 400–800 lines. Strategic, concise, decision-oriented.\n\n### Required Sections\n\n1. **System Overview** — What it does, who uses it, business value in 2-3 sentences\n2. **Capability Map** — Table: Capability, Status (Built\u002FPartial\u002FPlanned), Maturity, Dependencies. What the system can and cannot do today.\n3. **Architecture at a Glance** — High-level Mermaid `graph LR` diagram. Services, data stores, external integrations — NO internal code details. Focus on deployment units and team boundaries.\n4. **Team Topology** — Which team\u002Fperson owns which components. Table: Component, Owner, Criticality, Bus Factor.\n5. **Technology Investment Thesis** — Why these technologies were chosen. Table: Technology, Purpose, Alternatives Considered, Risk Level.\n6. **Risk Assessment** — Table: Risk, Likelihood, Impact, Mitigation, Owner. Cover reliability, security, scalability, compliance.\n7. **Cost & Scaling Model** — How costs scale with usage. What the bottlenecks are. When the next scaling investment is needed.\n8. **Dependency Map** — `graph TB` showing critical external dependencies. Table: Dependency, Type (Service\u002FLibrary\u002FPlatform), Risk if Unavailable.\n9. **Key Metrics & Observability** — What's measured, what dashboards exist, alerting coverage. Table: Metric, Current Value, Target, Source.\n10. **Roadmap Alignment** — Engineering workstreams mapped to business priorities. What's in progress, what's planned, what's blocked.\n11. **Technical Debt Summary** — Top 5 debt items with business impact. Table: Issue, Business Impact, Effort to Fix, Priority.\n12. **Recommendations** — 3-5 actionable recommendations for the next quarter, prioritized by impact.\n\n### Rules\n- **NO code snippets** — this guide is for engineering leaders, not coders\n- **Diagrams at service\u002Fteam level**, not class\u002Ffunction level\n- **Every claim backed by evidence** — cite wiki sections, architecture docs, or source files\n- **Minimum 3 Mermaid diagrams** (architecture overview, dependency map, capability\u002Froadmap)\n- Tables for every structured finding — this audience reads tables, not prose\n- **Business language** — translate technical concepts into impact (reliability, velocity, cost, risk)\n\n---\n\n## Guide 4: Product Manager Guide\n\n**File**: `onboarding\u002Fproduct-manager-guide.md`\n**Audience**: Product managers and non-engineering stakeholders. Needs to understand what the system does, what's possible, and where the boundaries are — NOT how it's built.\n**Length**: 400–800 lines. User-centric, feature-focused, constraint-aware.\n\n### Required Sections\n\n1. **What This System Does** — 2-3 sentence elevator pitch in user-facing language (no jargon)\n2. **User Journey Map** — Mermaid `graph LR` or `journey` diagram showing primary user flows through the system\n3. **Feature Capability Map** — Table: Feature, Status (Live\u002FBeta\u002FPlanned\u002FNot Possible), User-Facing Behavior, Limitations. Comprehensive map of what's built and what's not.\n4. **Data Model (Product View)** — Simplified Mermaid `erDiagram` showing entities users interact with. Explain in business terms (e.g., \"A Project has many Documents\" not \"FK relationship\").\n5. **Configuration & Feature Flags** — Table: Flag\u002FConfig, What It Controls, Default, Who Can Change It. What can be toggled without engineering work.\n6. **API Capabilities** — What integrations are possible. Table: Capability, Endpoint\u002FMethod, Authentication, Rate Limits. Written for integration partners, not developers.\n7. **Performance & SLAs** — Response times, throughput limits, availability targets. Table: Operation, Expected Latency, Throughput Limit, Current SLA.\n8. **Known Limitations & Constraints** — Honest list of what the system can't do or does poorly. Table: Limitation, User Impact, Workaround, Planned Fix.\n9. **Data & Privacy** — What data is collected, where it's stored, retention policies, compliance status. Table: Data Type, Storage Location, Retention, Compliance.\n10. **Glossary** — Domain terms explained in plain language (not engineering jargon)\n11. **FAQ** — 10+ common questions a PM would ask, answered concisely\n\n### Rules\n- **ZERO engineering jargon** — no \"middleware\", \"dependency injection\", \"ORM\". Use plain language.\n- **User-centric framing** — describe everything in terms of what users experience, not how code works\n- **Minimum 3 Mermaid diagrams** (user journey, data model, feature map\u002Fcapability overview)\n- Tables for every structured finding — PMs scan tables, not prose\n- If a technical concept must be mentioned, explain it in one sentence (e.g., \"Feature flags — toggles that let us turn features on\u002Foff without deploying code\")\n- Every claim grounded in evidence — cite wiki sections or source files for verification\n\n---\n\n## Mermaid Diagram Rules (ALL guides)\n\nALL diagrams must use dark-mode colors:\n- Node fills: `#2d333b`, borders: `#6d5dfc`, text: `#e6edf3`\n- Subgraph backgrounds: `#161b22`, borders: `#30363d`\n- Lines: `#8b949e`\n- If using inline `style` directives, use dark fills with `,color:#e6edf3`\n- Do NOT use `\u003Cbr\u002F>` in Mermaid labels (use `\u003Cbr>` or line breaks)\n\n## Validation\n\nAfter generating each guide, verify:\n- All file paths mentioned actually exist in the repo\n- All class\u002Fmethod names are accurate (not hallucinated)\n- Mermaid diagrams render (no syntax errors)\n- No bare HTML-like tags (generics like `List\u003CT>`) outside code fences — wrap in backticks\n- Each guide is appropriate for its audience — no code in Executive\u002FPM guides\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Microsoft","1.0.0","master","c247302c836de6438d746b45670990eb71691166","skills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-onboarding",1,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool","https:\u002F\u002Fgithub.com\u002Fqhjqhj00","chien.io","2026-05-11 15:07:59",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-onboarding",{"tool":41,"command":42},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-onboarding",{"tool":44,"command":45},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-onboarding\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M73JJB6EQPFPPVQK2Y9N67Q0","transformer-lens-interpretability","Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F130-transformer-lens\u002FSKILL.md",[],[],{"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":19},"01M73JHTANRRWEE9HP98TPEHAY","wiki-vitepress","Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F126-wiki-vitepress\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":19},"01M73JHJBMVFW46F1Y8K3SBF43","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F124-phoenix\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":19},"01M73JHFPA3A2806PMP42ZN86Q","frontend-ui-dark-ts","Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F123-frontend-ui-dark-ts\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":19},"01M73JFVBVK57NRJS49TT2VDCT","tensorboard","Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F113-tensorboard\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":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M73JFF6PK6ZCN41C89J7HS2B","markdown-mermaid-writing","Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F110-markdown-mermaid-writing\u002FSKILL.md",[],[]]