[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71TPX2JGVVCSJMY0XA4P26M":3,"skill-same:01M71TPX2JGVVCSJMY0XA4P26M":124},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M71TPX2JGVVCSJMY0XA4P26M","plann",null,"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.","toanil315\u002Fvn-itinerary-be","toanil315","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58522459?v=4","01M71JK4015WT83WGZTMKWMWRK","Toanil","01M71TNAXJFP5NQVFTGZD7RTVJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"archive","phases","solution","phase","for","feature planning","architectures","feature","system design","design","system","plan","team","red-team","implementation strategy","planning","create","documentation","architecture","2026-11-10 13:02:02",false,"---\nname: plann\ndescription: \"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.\"\nargument-hint: \"[task] OR archive|red-team|validate\"\nlicense: MIT\n---\n\n# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## Default (No Arguments)\n\nIf invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, use `AskUserQuestion` to present available operations:\n\n| Operation   | Description                           |\n| ----------- | ------------------------------------- |\n| `(default)` | Create implementation plan for a task |\n| `archive`   | Write journal entry & archive plans   |\n| `red-team`  | Adversarial plan review               |\n| `validate`  | Critical questions interview          |\n\nPresent as options via `AskUserQuestion` with header \"Planning Operation\", question \"What would you like to do?\".\n\n## Workflow Modes\n\nDefault: `--auto` (analyze task complexity and auto-pick mode).\n\n| Flag         | Mode           | Research       | Red Team        | Validation      | Cook Flag    |\n| ------------ | -------------- | -------------- | --------------- | --------------- | ------------ |\n| `--auto`     | Auto-detect    | Follows mode   | Follows mode    | Follows mode    | Follows mode |\n| `--fast`     | Fast           | Skip           | Skip            | Skip            | `--auto`     |\n| `--hard`     | Hard           | 2 researchers  | Yes             | Optional        | (none)       |\n| `--parallel` | Parallel       | 2 researchers  | Yes             | Optional        | `--parallel` |\n| `--two`      | Two approaches | 2+ researchers | After selection | After selection | (none)       |\n\nAdd `--no-tasks` to skip task hydration in any mode.\n\nLoad: `references\u002Fworkflow-modes.md` for auto-detection logic, per-mode workflows, context reminders.\n\n## When to Use\n\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n\n## Core Responsibilities & Rules\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### 1. Research & Analysis\n\nLoad: `references\u002Fresearch-phase.md`\n**Skip if:** Fast mode or provided with researcher reports\n\n### 2. Codebase Understanding\n\nLoad: `references\u002Fcodebase-understanding.md`\n**Skip if:** Provided with scout reports\n\n### 3. Solution Design\n\nLoad: `references\u002Fsolution-design.md`\n\n### 4. Plan Creation & Organization\n\nLoad: `references\u002Fplan-organization.md`\n\n### 5. Task Breakdown & Output Standards\n\nLoad: `references\u002Foutput-standards.md`\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n2. **Mode Detection** → Auto-detect or use explicit flag (see `workflow-modes.md`)\n3. **Research Phase** → Spawn researchers (skip in fast mode)\n4. **Codebase Analysis** → Read docs, scout if needed\n5. **Plan Documentation** → Write comprehensive plan via planner subagent\n6. **Red Team Review** → Use `Skill` tool: `plan:red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Use `Skill` tool: `plan:validate {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n8. **Hydrate Tasks** → Create Claude Tasks from phases (default on, `--no-tasks` to skip)\n9. **Context Reminder** → Output cook command with absolute path (MANDATORY)\n\n## Output Requirements\n\n- DO NOT implement code - only create plans\n- Respond with plan file path and summary\n- Ensure self-contained plans with necessary context\n- Include code snippets\u002Fpseudocode when clarifying\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file\n\n## Task Management\n\nPlan files = persistent. Tasks = session-scoped. Hydration bridges the gap.\n\n**Default:** Auto-hydrate tasks after plan files are written. Skip with `--no-tasks`.\n**3-Task Rule:** \u003C3 phases → skip task creation.\n\nLoad: `references\u002Ftask-management.md` for hydration pattern, TaskCreate patterns, cook handoff protocol.\n\n### Hydration Workflow\n\n1. Write plan.md + phase files (persistent layer)\n2. TaskCreate per phase with `addBlockedBy` chain\n3. TaskCreate for critical\u002Fhigh-risk steps within phases\n4. Metadata: phase, priority, effort, planDir, phaseFile\n5. Cook picks up via TaskList (same session) or re-hydrates (new session)\n\n## Active Plan State\n\nCheck `## Plan Context` injected by hooks:\n\n- **\"Plan: {path}\"** → Active plan. Ask \"Continue? [Y\u002Fn]\"\n- **\"Suggested: {path}\"** → Branch hint only. Ask if activate or create new.\n- **\"Plan: none\"** → Create new using `Plan dir:` from `## Naming`\n\nAfter creating plan: `node .github\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\n\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n## Subcommands\n\n| Subcommand        | Reference                         | Purpose                                         |\n| ----------------- | --------------------------------- | ----------------------------------------------- |\n| `\u002Fplann archive`  | `references\u002Farchive-workflow.md`  | Archive plans + write journal entries           |\n| `\u002Fplann red-team` | `references\u002Fred-team-workflow.md` | Adversarial plan review with hostile reviewers  |\n| `\u002Fplann validate` | `references\u002Fvalidate-workflow.md` | Validate plan with critical questions interview |\n\n## Quality Standards\n\n- Thorough and specific, consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Detailed enough for junior developers\n- Validate against existing codebase patterns\n\n**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.\n","# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## Default (No Arguments)\n\nIf invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, use `AskUserQuestion` to present available operations:\n\n| Operation   | Description                           |\n| ----------- | ------------------------------------- |\n| `(default)` | Create implementation plan for a task |\n| `archive`   | Write journal entry & archive plans   |\n| `red-team`  | Adversarial plan review               |\n| `validate`  | Critical questions interview          |\n\nPresent as options via `AskUserQuestion` with header \"Planning Operation\", question \"What would you like to do?\".\n\n## Workflow Modes\n\nDefault: `--auto` (analyze task complexity and auto-pick mode).\n\n| Flag         | Mode           | Research       | Red Team        | Validation      | Cook Flag    |\n| ------------ | -------------- | -------------- | --------------- | --------------- | ------------ |\n| `--auto`     | Auto-detect    | Follows mode   | Follows mode    | Follows mode    | Follows mode |\n| `--fast`     | Fast           | Skip           | Skip            | Skip            | `--auto`     |\n| `--hard`     | Hard           | 2 researchers  | Yes             | Optional        | (none)       |\n| `--parallel` | Parallel       | 2 researchers  | Yes             | Optional        | `--parallel` |\n| `--two`      | Two approaches | 2+ researchers | After selection | After selection | (none)       |\n\nAdd `--no-tasks` to skip task hydration in any mode.\n\nLoad: `references\u002Fworkflow-modes.md` for auto-detection logic, per-mode workflows, context reminders.\n\n## When to Use\n\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n\n## Core Responsibilities & Rules\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### 1. Research & Analysis\n\nLoad: `references\u002Fresearch-phase.md`\n**Skip if:** Fast mode or provided with researcher reports\n\n### 2. Codebase Understanding\n\nLoad: `references\u002Fcodebase-understanding.md`\n**Skip if:** Provided with scout reports\n\n### 3. Solution Design\n\nLoad: `references\u002Fsolution-design.md`\n\n### 4. Plan Creation & Organization\n\nLoad: `references\u002Fplan-organization.md`\n\n### 5. Task Breakdown & Output Standards\n\nLoad: `references\u002Foutput-standards.md`\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n2. **Mode Detection** → Auto-detect or use explicit flag (see `workflow-modes.md`)\n3. **Research Phase** → Spawn researchers (skip in fast mode)\n4. **Codebase Analysis** → Read docs, scout if needed\n5. **Plan Documentation** → Write comprehensive plan via planner subagent\n6. **Red Team Review** → Use `Skill` tool: `plan:red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Use `Skill` tool: `plan:validate {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n8. **Hydrate Tasks** → Create Claude Tasks from phases (default on, `--no-tasks` to skip)\n9. **Context Reminder** → Output cook command with absolute path (MANDATORY)\n\n## Output Requirements\n\n- DO NOT implement code - only create plans\n- Respond with plan file path and summary\n- Ensure self-contained plans with necessary context\n- Include code snippets\u002Fpseudocode when clarifying\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file\n\n## Task Management\n\nPlan files = persistent. Tasks = session-scoped. Hydration bridges the gap.\n\n**Default:** Auto-hydrate tasks after plan files are written. Skip with `--no-tasks`.\n**3-Task Rule:** \u003C3 phases → skip task creation.\n\nLoad: `references\u002Ftask-management.md` for hydration pattern, TaskCreate patterns, cook handoff protocol.\n\n### Hydration Workflow\n\n1. Write plan.md + phase files (persistent layer)\n2. TaskCreate per phase with `addBlockedBy` chain\n3. TaskCreate for critical\u002Fhigh-risk steps within phases\n4. Metadata: phase, priority, effort, planDir, phaseFile\n5. Cook picks up via TaskList (same session) or re-hydrates (new session)\n\n## Active Plan State\n\nCheck `## Plan Context` injected by hooks:\n\n- **\"Plan: {path}\"** → Active plan. Ask \"Continue? [Y\u002Fn]\"\n- **\"Suggested: {path}\"** → Branch hint only. Ask if activate or create new.\n- **\"Plan: none\"** → Create new using `Plan dir:` from `## Naming`\n\nAfter creating plan: `node .github\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\n\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n## Subcommands\n\n| Subcommand        | Reference                         | Purpose                                         |\n| ----------------- | --------------------------------- | ----------------------------------------------- |\n| `\u002Fplann archive`  | `references\u002Farchive-workflow.md`  | Archive plans + write journal entries           |\n| `\u002Fplann red-team` | `references\u002Fred-team-workflow.md` | Adversarial plan review with hostile reviewers  |\n| `\u002Fplann validate` | `references\u002Fvalidate-workflow.md` | Validate plan with critical questions interview |\n\n## Quality Standards\n\n- Thorough and specific, consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Detailed enough for junior developers\n- Validate against existing codebase patterns\n\n**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.\n",{"name":5,"license":15,"description":7,"argument-hint":53},"[task] OR archive|red-team|validate","main","90a211e38a42b59ef5339ddd6471c747129a7440",".github\u002Fskills\u002Fplann","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be","https:\u002F\u002Fgithub.com\u002Ftoanil315","2026-05-09 19:23:45",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add toanil315\u002Fvn-itinerary-be --skill plann",{"tool":66,"command":67},"bunx","bunx skills add toanil315\u002Fvn-itinerary-be --skill plann",{"tool":69,"command":70},"pnpm","pnpm dlx skills add toanil315\u002Fvn-itinerary-be --skill plann","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002FSKILL.md",true,[74,80,84,88,92,96,100,104,108,112,116,120],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Farchive-workflow.md","REFERENCE","参考文档",2336,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Farchive-workflow.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcodebase-understanding.md",1973,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fcodebase-understanding.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Foutput-standards.md",4571,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Foutput-standards.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fplan-organization.md",3837,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fplan-organization.md",{"path":93,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fred-team-personas.md",2621,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fred-team-personas.md",{"path":97,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fred-team-workflow.md",2793,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fred-team-workflow.md",{"path":101,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fresearch-phase.md",1578,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fresearch-phase.md",{"path":105,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fsolution-design.md",{"path":109,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Ftask-management.md",5846,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Ftask-management.md",{"path":113,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fvalidate-question-framework.md",2361,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fvalidate-question-framework.md",{"path":117,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fvalidate-workflow.md",2320,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fvalidate-workflow.md",{"path":121,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Fworkflow-modes.md",6352,"https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplann\u002Freferences\u002Fworkflow-modes.md",[125,151,175,196,223,237],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":48},"01M71TQK0CCJY53JT3CNMBES7B","ck:web-frameworks","Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,36],"ck:web frameworks","frameworks","web frameworks","web","ck","shared","app","apps","caching","react","router","strategies","server","rsc","next","ssr","rendering","turborepo","framework",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":48},"01M71TQF4PX0A344GVTBB6MCF5","ck:sequential-thinking","Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[158,159,160,136,161,162,163,44,33,164,165,166,167,168,169,170,171,172,173,174],"thinking","sequential thinking","ck:sequential thinking","adaptive","course","problem","use","apply","analysis","analyze","with","multi","verification","decomposition","reasoning","revision","hypothesis",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":48},"01M71TQAQ3RZMFKKTW5CFA6E7K","ck:research","Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability\u002Fsecurity\u002Fmaintainability analysis.","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fresearch\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[177,185,136,35,33,186,38,187,188,164,189,190,166,191,167,192,31,193,194,195],"research","gather","technology","technical","best practices","requirements","scalability","solutions","maintainability","Evaluation","security",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":207,"publishedAt":48},"01M71TNVC42JJZM75QP95N6ZAP","ck:databases","Design schemas, write queries for MongoDB and PostgreSQL. Use for database design, SQL\u002FNoSQL queries, aggregation pipelines, indexes, migrations, replication, performance optimization, psql CLI.","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdatabases\u002FSKILL.md",[202,205,206],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[208,198,136,209,33,210,211,212,38,213,214,164,215,216,217,218,219,220,221,222],"databases","replication","Optimization","performance","schemas","schema","mongodb","database","query","task","queries","postgresql","cli","performance optimization","migrations",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":48},"01M71TNHJBS5KPF88NR7PDP58Q","ck:brainstorm","Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fbrainstorm\u002FSKILL.md",[],[230,136,225,231,163,36,33,232,38,188,164,233,166,47,168,234,192,235,236],"brainstorm","exploration","assessment","decisions","ideation","trade","feasibility",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":48},"01M71TNFB3RHTXZX9B8BQAS5GE","ck:backend-development","Build backends with Node.js, Python, Go (NestJS, FastAPI, Django). Use for REST\u002FGraphQL\u002FgRPC APIs, auth (OAuth, JWT), databases, microservices, security (OWASP), Docker\u002FK8s.","https:\u002F\u002Fgithub.com\u002Ftoanil315\u002Fvn-itinerary-be\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fbackend-development\u002FSKILL.md",[243],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,136,247,248,208,249,250,251,252,33,253,254,255,164,256,217,168,257,258],"development","backend","ck:backend development","backend development","grpc","k8s","django","auth","docker","python","fastapi","OAuth","nestjs","REST"]