[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BNBBECNFZAM4WGY64P2HQ":3,"skill-same:01M71BNBBECNFZAM4WGY64P2HQ":71},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71BNBBECNFZAM4WGY64P2HQ","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.","strmt7\u002Fai_skills_collection_benchmarked","strmt7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28989754?v=4","01M71929P914SWKQ7QJV24NBBY","Stratos","01M71929Q9VGKQ7PWYR95VSQQQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-onboarding\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"wiki onboarding","onboarding","wiki","engineer","when","contributor","Staff","codebase","for","manager","folder","guides","microsoft","use","user","Product Manager","product","documentation","2026-11-10 10:12:30",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":47,"description":7},{"author":48,"version":49},"Microsoft","1.0.0","main","5c95bcac4646c5aed06bd9aed5235cfc7985aafc","included\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-onboarding",0,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked","https:\u002F\u002Fgithub.com\u002Fstrmt7","2026-11-11 04:18:12",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add strmt7\u002Fai_skills_collection_benchmarked --skill wiki-onboarding",{"tool":63,"command":64},"bunx","bunx skills add strmt7\u002Fai_skills_collection_benchmarked --skill wiki-onboarding",{"tool":66,"command":67},"pnpm","pnpm dlx skills add strmt7\u002Fai_skills_collection_benchmarked --skill wiki-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fcloud-azure-microsoft-sdks\u002Fofficial-vendor-reference\u002Fwiki-onboarding\u002FSKILL.md",true,[],[72,105,134,159,184,210],{"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":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":88,"publishedAt":42},"01M71D4H3T6M57DFKN8HENAWRV","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fwebapp-testing\u002FSKILL.md",[80,85],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":86,"categoryName":87,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000009","前端开发",[89,90,91,32,92,93,94,95,96,97,98,99,100,101,102,103,104],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","with","playwright","web","behavior","ui","screenshots",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":115,"publishedAt":42},"01M71D4CQR2A2TB7GASCR5ZBG3","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fskill-creator-anthropics\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fskill-creator-anthropics\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发",[116,117,118,119,120,121,28,122,123,124,125,126,127,128,129,130,131,132,32,133],"skill creator","creator","performance","improve","run evals","new","analysis","create","optimize","variance analysis","run","edit","benchmark","a skill","existing skill","evals","modify","accuracy",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":142,"publishedAt":42},"01M71D488XHEZVXXSXFYP8ENMH","playwright-skill","Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web functionality, or perform browser-based testing.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Flatest-release-browser-automation\u002Fplaywright-skill\u002FSKILL.md",[140,141],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":113,"categoryName":114,"taxonomyType":83,"taxonomyTypeDesc":84},[100,143,144,145,90,146,147,28,148,98,149,150,151,152,153,154,155,156,157,158],"playwright skill","browser automation","flows","auto","access","Bash","website","ux","login","scripts","read","write","node","install","network","responsive",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":42},"01M71CY25GM939M6RES91QSG3T","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Fweb-artifacts-builder\u002FSKILL.md",[166],{"categoryNo":86,"categoryName":87,"taxonomyType":83,"taxonomyTypeDesc":84},[168,169,170,101,171,172,173,32,174,175,94,176,37,177,178,179,180,181,182,183],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":198,"publishedAt":42},"01M71CXZB60QJJ1H4S3NN94WMZ","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Ffrontend-design\u002FSKILL.md",[191,192,195],{"categoryNo":86,"categoryName":87,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":193,"categoryName":194,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[94,199,200,173,201,202,203,92,204,205,37,28,170,206,178,207,179,208,209,99],"design","frontend design","ui design","generic","aesthetics","landing","pages","code","web ui","react components","examples",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":216,"publishedAt":42},"01M71CVZ54WFBTVA7R16PFY1ZE","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\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fzarr-python\u002FSKILL.md",[],[217,218,219,220,221,222,223,224,225,32,226,227,228,229,230,231,232,233],"zarr python","python","zarr","arrays","Cloud Storage","scientific","storage","parallel","dask","numpy","gcs","s3","integration","scientific computing","cloud","scale","pipelines"]