[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73A2JK0WR8SS9VG2PV5D0TC":3,"skill-same:01M73A2JK0WR8SS9VG2PV5D0TC":56},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M73A2JK0WR8SS9VG2PV5D0TC","code-tour",null,"Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fcode-tour\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"code-tour\"\ndescription: \"Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.\"\n---\n\n# Code Tour\n\nCreate **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours\u002F` and work with the [VS Code CodeTour extension](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour).\n\n## Overview\n\nA great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code.\n\n## When to Use This Skill\n\n- User asks to create a code tour, onboarding tour, or architecture walkthrough\n- User says \"tour for this PR\", \"explain how X works\", \"vibe check\", \"RCA tour\"\n- User wants a contributor guide, security review, or bug investigation walkthrough\n- Any request for a structured walkthrough with file\u002Fline anchors\n\n## Core Workflow\n\n### 1. Discover the repo\n\nBefore asking anything, explore the codebase:\n\nIn parallel: list root directory, read README, check config files.\nThen: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.\n\nIf the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.\n\n### 2. Infer the intent\n\nOne message should be enough. Infer persona, depth, and focus silently.\n\n| User says | Persona | Depth |\n|-----------|---------|-------|\n| \"tour for this PR\" | pr-reviewer | standard |\n| \"why did X break\" \u002F \"RCA\" | rca-investigator | standard |\n| \"onboarding\" \u002F \"new joiner\" | new-joiner | standard |\n| \"quick tour\" \u002F \"vibe check\" | vibecoder | quick |\n| \"architecture\" | architect | deep |\n| \"security\" \u002F \"auth review\" | security-reviewer | standard |\n| (no qualifier) | new-joiner | standard |\n\nWhen intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.\n\n### 3. Read actual files\n\n**Every file path and line number must be verified.** A tour pointing to the wrong line is worse than no tour.\n\n### 4. Write the tour\n\nSave to `.tours\u002F\u003Cpersona>-\u003Cfocus>.tour`.\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"Descriptive Title — Persona \u002F Goal\",\n  \"description\": \"Who this is for and what they'll understand after.\",\n  \"ref\": \"\u003Ccurrent-branch-or-commit>\",\n  \"steps\": []\n}\n```\n\n### Step types\n\n| Type | When to use | Example |\n|------|-------------|---------|\n| **Content** | Intro\u002Fclosing only (max 2) | `{ \"title\": \"Welcome\", \"description\": \"...\" }` |\n| **Directory** | Orient to a module | `{ \"directory\": \"src\u002Fservices\", \"title\": \"...\" }` |\n| **File + line** | The workhorse | `{ \"file\": \"src\u002Fauth.ts\", \"line\": 42, \"title\": \"...\" }` |\n| **Selection** | Highlight a code block | `{ \"file\": \"...\", \"selection\": {...}, \"title\": \"...\" }` |\n| **Pattern** | Regex match (volatile files) | `{ \"file\": \"...\", \"pattern\": \"class App\", \"title\": \"...\" }` |\n| **URI** | Link to PR, issue, doc | `{ \"uri\": \"https:\u002F\u002F...\", \"title\": \"...\" }` |\n\n### Step count\n\n| Depth | Steps | Use for |\n|-------|-------|---------|\n| Quick | 5-8 | Vibecoder, fast exploration |\n| Standard | 9-13 | Most personas |\n| Deep | 14-18 | Architect, RCA |\n\n### Writing descriptions — SMIG formula\n\n- **S — Situation**: What is the reader looking at?\n- **M — Mechanism**: How does this code work?\n- **I — Implication**: Why does this matter for this persona?\n- **G — Gotcha**: What would a smart person get wrong?\n\n### 5. Validate\n\n- [ ] Every `file` path relative to repo root (no leading `\u002F` or `.\u002F`)\n- [ ] Every `file` confirmed to exist\n- [ ] Every `line` verified by reading the file\n- [ ] First step has `file` or `directory` anchor\n- [ ] At most 2 content-only steps\n- [ ] `nextTour` matches another tour's `title` exactly if set\n\n## Personas\n\n| Persona | Goal | Must cover |\n|---------|------|------------|\n| **Vibecoder** | Get the vibe fast | Entry point, main modules. Max 8 steps. |\n| **New joiner** | Structured ramp-up | Directories, setup, business context |\n| **Bug fixer** | Root cause fast | Trigger -> fault points -> tests |\n| **RCA investigator** | Why did it fail | Causality chain, observability anchors |\n| **Feature explainer** | End-to-end | UI -> API -> backend -> storage |\n| **PR reviewer** | Review correctly | Change story, invariants, risky areas |\n| **Architect** | Shape and rationale | Boundaries, tradeoffs, extension points |\n| **Security reviewer** | Trust boundaries | Auth flow, validation, secret handling |\n| **Refactorer** | Safe restructuring | Seams, hidden deps, extraction order |\n| **External contributor** | Contribute safely | Safe areas, conventions, landmines |\n\n## Narrative Arc\n\n1. **Orientation** — `file` or `directory` step (never content-only first step — blank in VS Code)\n2. **High-level map** — 1-3 directory steps showing major modules\n3. **Core path** — file\u002Fline steps, the heart of the tour\n4. **Closing** — what the reader can now do, suggested follow-ups\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **File listing** — \"this file contains the models\" | Tell a story. Each step depends on the previous. |\n| **Generic descriptions** | Name the specific pattern unique to this codebase. |\n| **Line number guessing** | Never write a line you didn't verify by reading. |\n| **Too many steps** for quick depth | Actually cut steps. |\n| **Hallucinated files** | If it doesn't exist, skip the step. |\n| **Recap closing** — \"we covered X, Y, Z\" | Tell the reader what they can now *do*. |\n| **Content-only first step** | Anchor step 1 to a file or directory. |\n\n## Cross-References\n\n- Related: `engineering\u002Fcodebase-onboarding` — for broader onboarding beyond tours\n- Related: `engineering\u002Fpr-review-expert` — for automated PR review workflows\n- CodeTour extension: [microsoft\u002Fcodetour](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour)\n- Real-world tours: [coder\u002Fcode-server](https:\u002F\u002Fgithub.com\u002Fcoder\u002Fcode-server\u002Fblob\u002Fmain\u002F.tours\u002Fcontributing.tour)\n","# Code Tour\n\nCreate **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours\u002F` and work with the [VS Code CodeTour extension](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour).\n\n## Overview\n\nA great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code.\n\n## When to Use This Skill\n\n- User asks to create a code tour, onboarding tour, or architecture walkthrough\n- User says \"tour for this PR\", \"explain how X works\", \"vibe check\", \"RCA tour\"\n- User wants a contributor guide, security review, or bug investigation walkthrough\n- Any request for a structured walkthrough with file\u002Fline anchors\n\n## Core Workflow\n\n### 1. Discover the repo\n\nBefore asking anything, explore the codebase:\n\nIn parallel: list root directory, read README, check config files.\nThen: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.\n\nIf the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.\n\n### 2. Infer the intent\n\nOne message should be enough. Infer persona, depth, and focus silently.\n\n| User says | Persona | Depth |\n|-----------|---------|-------|\n| \"tour for this PR\" | pr-reviewer | standard |\n| \"why did X break\" \u002F \"RCA\" | rca-investigator | standard |\n| \"onboarding\" \u002F \"new joiner\" | new-joiner | standard |\n| \"quick tour\" \u002F \"vibe check\" | vibecoder | quick |\n| \"architecture\" | architect | deep |\n| \"security\" \u002F \"auth review\" | security-reviewer | standard |\n| (no qualifier) | new-joiner | standard |\n\nWhen intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.\n\n### 3. Read actual files\n\n**Every file path and line number must be verified.** A tour pointing to the wrong line is worse than no tour.\n\n### 4. Write the tour\n\nSave to `.tours\u002F\u003Cpersona>-\u003Cfocus>.tour`.\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"Descriptive Title — Persona \u002F Goal\",\n  \"description\": \"Who this is for and what they'll understand after.\",\n  \"ref\": \"\u003Ccurrent-branch-or-commit>\",\n  \"steps\": []\n}\n```\n\n### Step types\n\n| Type | When to use | Example |\n|------|-------------|---------|\n| **Content** | Intro\u002Fclosing only (max 2) | `{ \"title\": \"Welcome\", \"description\": \"...\" }` |\n| **Directory** | Orient to a module | `{ \"directory\": \"src\u002Fservices\", \"title\": \"...\" }` |\n| **File + line** | The workhorse | `{ \"file\": \"src\u002Fauth.ts\", \"line\": 42, \"title\": \"...\" }` |\n| **Selection** | Highlight a code block | `{ \"file\": \"...\", \"selection\": {...}, \"title\": \"...\" }` |\n| **Pattern** | Regex match (volatile files) | `{ \"file\": \"...\", \"pattern\": \"class App\", \"title\": \"...\" }` |\n| **URI** | Link to PR, issue, doc | `{ \"uri\": \"https:\u002F\u002F...\", \"title\": \"...\" }` |\n\n### Step count\n\n| Depth | Steps | Use for |\n|-------|-------|---------|\n| Quick | 5-8 | Vibecoder, fast exploration |\n| Standard | 9-13 | Most personas |\n| Deep | 14-18 | Architect, RCA |\n\n### Writing descriptions — SMIG formula\n\n- **S — Situation**: What is the reader looking at?\n- **M — Mechanism**: How does this code work?\n- **I — Implication**: Why does this matter for this persona?\n- **G — Gotcha**: What would a smart person get wrong?\n\n### 5. Validate\n\n- [ ] Every `file` path relative to repo root (no leading `\u002F` or `.\u002F`)\n- [ ] Every `file` confirmed to exist\n- [ ] Every `line` verified by reading the file\n- [ ] First step has `file` or `directory` anchor\n- [ ] At most 2 content-only steps\n- [ ] `nextTour` matches another tour's `title` exactly if set\n\n## Personas\n\n| Persona | Goal | Must cover |\n|---------|------|------------|\n| **Vibecoder** | Get the vibe fast | Entry point, main modules. Max 8 steps. |\n| **New joiner** | Structured ramp-up | Directories, setup, business context |\n| **Bug fixer** | Root cause fast | Trigger -> fault points -> tests |\n| **RCA investigator** | Why did it fail | Causality chain, observability anchors |\n| **Feature explainer** | End-to-end | UI -> API -> backend -> storage |\n| **PR reviewer** | Review correctly | Change story, invariants, risky areas |\n| **Architect** | Shape and rationale | Boundaries, tradeoffs, extension points |\n| **Security reviewer** | Trust boundaries | Auth flow, validation, secret handling |\n| **Refactorer** | Safe restructuring | Seams, hidden deps, extraction order |\n| **External contributor** | Contribute safely | Safe areas, conventions, landmines |\n\n## Narrative Arc\n\n1. **Orientation** — `file` or `directory` step (never content-only first step — blank in VS Code)\n2. **High-level map** — 1-3 directory steps showing major modules\n3. **Core path** — file\u002Fline steps, the heart of the tour\n4. **Closing** — what the reader can now do, suggested follow-ups\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **File listing** — \"this file contains the models\" | Tell a story. Each step depends on the previous. |\n| **Generic descriptions** | Name the specific pattern unique to this codebase. |\n| **Line number guessing** | Never write a line you didn't verify by reading. |\n| **Too many steps** for quick depth | Actually cut steps. |\n| **Hallucinated files** | If it doesn't exist, skip the step. |\n| **Recap closing** — \"we covered X, Y, Z\" | Tell the reader what they can now *do*. |\n| **Content-only first step** | Anchor step 1 to a file or directory. |\n\n## Cross-References\n\n- Related: `engineering\u002Fcodebase-onboarding` — for broader onboarding beyond tours\n- Related: `engineering\u002Fpr-review-expert` — for automated PR review workflows\n- CodeTour extension: [microsoft\u002Fcodetour](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour)\n- Real-world tours: [coder\u002Fcode-server](https:\u002F\u002Fgithub.com\u002Fcoder\u002Fcode-server\u002Fblob\u002Fmain\u002F.tours\u002Fcontributing.tour)\n",{"name":5,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fnginity-engineering\u002Fcode-tour","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill code-tour",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill code-tour",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill code-tour","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fcode-tour\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",625,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fcode-tour\u002F.claude-plugin\u002Fplugin.json",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"evals.json",1942,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fcode-tour\u002Fevals.json",[57,64,71,78,85,92],{"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},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\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},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\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},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\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},"01M73CF80XCM9K81567MJ8QZFW","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\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\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":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]