[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MAHR79XZHB16PC6NWES4BM":3,"skill-same:01M6MAHR79XZHB16PC6NWES4BM":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6MAHR79XZHB16PC6NWES4BM","agent-md-refactor",null,"Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.","superhealth\u002Fskills-hub","superhealth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6292112?v=4","01M6JA6E7F21BYK5W3E4P270TT","01M6JA6EC0W8MPHKDJVBZDSEZ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftaworks\u002Fagent-md-refactor\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33],"refactor","agent md refactor","documentation","files","monolithic","principles","splits","progressive disclosure","2026-11-10 10:12:30",false,"---\nname: agent-md-refactor\ndescription: Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.\nlicense: MIT\n---\n\n# Agent MD Refactor\n\nRefactor bloated agent instruction files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) to follow **progressive disclosure principles** - keeping essentials at root and organizing the rest into linked, categorized files.\n\n---\n\n## Triggers\n\nUse this skill when:\n- \"refactor my AGENTS.md\" \u002F \"refactor my CLAUDE.md\"\n- \"split my agent instructions\"\n- \"organize my CLAUDE.md file\"\n- \"my AGENTS.md is too long\"\n- \"progressive disclosure for my instructions\"\n- \"clean up my agent config\"\n\n---\n\n## Quick Reference\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1. Analyze | Find contradictions | List of conflicts to resolve |\n| 2. Extract | Identify essentials | Core instructions for root file |\n| 3. Categorize | Group remaining instructions | Logical categories |\n| 4. Structure | Create file hierarchy | Root + linked files |\n| 5. Prune | Flag for deletion | Redundant\u002Fvague instructions |\n\n---\n\n## Process\n\n### Phase 1: Find Contradictions\n\nIdentify any instructions that conflict with each other.\n\n**Look for:**\n- Contradictory style guidelines (e.g., \"use semicolons\" vs \"no semicolons\")\n- Conflicting workflow instructions\n- Incompatible tool preferences\n- Mutually exclusive patterns\n\n**For each contradiction found:**\n```markdown\n## Contradiction Found\n\n**Instruction A:** [quote]\n**Instruction B:** [quote]\n\n**Question:** Which should take precedence, or should both be conditional?\n```\n\nAsk the user to resolve before proceeding.\n\n---\n\n### Phase 2: Identify the Essentials\n\nExtract ONLY what belongs in the root agent file. The root should be minimal - information that applies to **every single task**.\n\n**Essential content (keep in root):**\n| Category | Example |\n|----------|---------|\n| Project description | One sentence: \"A React dashboard for analytics\" |\n| Package manager | Only if not npm (e.g., \"Uses pnpm\") |\n| Non-standard commands | Custom build\u002Ftest\u002Ftypecheck commands |\n| Critical overrides | Things that MUST override defaults |\n| Universal rules | Applies to 100% of tasks |\n\n**NOT essential (move to linked files):**\n- Language-specific conventions\n- Testing guidelines\n- Code style details\n- Framework patterns\n- Documentation standards\n- Git workflow details\n\n---\n\n### Phase 3: Group the Rest\n\nOrganize remaining instructions into logical categories.\n\n**Common categories:**\n| Category | Contents |\n|----------|----------|\n| `typescript.md` | TS conventions, type patterns, strict mode rules |\n| `testing.md` | Test frameworks, coverage, mocking patterns |\n| `code-style.md` | Formatting, naming, comments, structure |\n| `git-workflow.md` | Commits, branches, PRs, reviews |\n| `architecture.md` | Patterns, folder structure, dependencies |\n| `api-design.md` | REST\u002FGraphQL conventions, error handling |\n| `security.md` | Auth patterns, input validation, secrets |\n| `performance.md` | Optimization rules, caching, lazy loading |\n\n**Grouping rules:**\n1. Each file should be self-contained for its topic\n2. Aim for 3-8 files (not too granular, not too broad)\n3. Name files clearly: `{topic}.md`\n4. Include only actionable instructions\n\n---\n\n### Phase 4: Create the File Structure\n\n**Output structure:**\n```\nproject-root\u002F\n├── CLAUDE.md (or AGENTS.md)     # Minimal root with links\n└── .claude\u002F                      # Or docs\u002Fagent-instructions\u002F\n    ├── typescript.md\n    ├── testing.md\n    ├── code-style.md\n    ├── git-workflow.md\n    └── architecture.md\n```\n\n**Root file template:**\n```markdown\n# Project Name\n\nOne-sentence description of the project.\n\n## Quick Reference\n\n- **Package Manager:** pnpm\n- **Build:** `pnpm build`\n- **Test:** `pnpm test`\n- **Typecheck:** `pnpm typecheck`\n\n## Detailed Instructions\n\nFor specific guidelines, see:\n- [TypeScript Conventions](.claude\u002Ftypescript.md)\n- [Testing Guidelines](.claude\u002Ftesting.md)\n- [Code Style](.claude\u002Fcode-style.md)\n- [Git Workflow](.claude\u002Fgit-workflow.md)\n- [Architecture Patterns](.claude\u002Farchitecture.md)\n```\n\n**Each linked file template:**\n```markdown\n# {Topic} Guidelines\n\n## Overview\nBrief context for when these guidelines apply.\n\n## Rules\n\n### Rule Category 1\n- Specific, actionable instruction\n- Another specific instruction\n\n### Rule Category 2\n- Specific, actionable instruction\n\n## Examples\n\n### Good\n\\`\\`\\`typescript\n\u002F\u002F Example of correct pattern\n\\`\\`\\`\n\n### Avoid\n\\`\\`\\`typescript\n\u002F\u002F Example of what not to do\n\\`\\`\\`\n```\n\n---\n\n### Phase 5: Flag for Deletion\n\nIdentify instructions that should be removed entirely.\n\n**Delete if:**\n| Criterion | Example | Why Delete |\n|-----------|---------|------------|\n| Redundant | \"Use TypeScript\" (in a .ts project) | Agent already knows |\n| Too vague | \"Write clean code\" | Not actionable |\n| Overly obvious | \"Don't introduce bugs\" | Wastes context |\n| Default behavior | \"Use descriptive variable names\" | Standard practice |\n| Outdated | References deprecated APIs | No longer applies |\n\n**Output format:**\n```markdown\n## Flagged for Deletion\n\n| Instruction | Reason |\n|-------------|--------|\n| \"Write clean, maintainable code\" | Too vague to be actionable |\n| \"Use TypeScript\" | Redundant - project is already TS |\n| \"Don't commit secrets\" | Agent already knows this |\n| \"Follow best practices\" | Meaningless without specifics |\n```\n\n---\n\n## Execution Checklist\n\n```\n[ ] Phase 1: All contradictions identified and resolved\n[ ] Phase 2: Root file contains ONLY essentials\n[ ] Phase 3: All remaining instructions categorized\n[ ] Phase 4: File structure created with proper links\n[ ] Phase 5: Redundant\u002Fvague instructions removed\n[ ] Verify: Each linked file is self-contained\n[ ] Verify: Root file is under 50 lines\n[ ] Verify: All links work correctly\n```\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Keeping everything in root | Bloated, hard to maintain | Split into linked files |\n| Too many categories | Fragmentation | Consolidate related topics |\n| Vague instructions | Wastes tokens, no value | Be specific or delete |\n| Duplicating defaults | Agent already knows | Only override when needed |\n| Deep nesting | Hard to navigate | Flat structure with links |\n\n---\n\n## Examples\n\n### Before (Bloated Root)\n```markdown\n# CLAUDE.md\n\nThis is a React project.\n\n## Code Style\n- Use 2 spaces\n- Use semicolons\n- Prefer const over let\n- Use arrow functions\n... (200 more lines)\n\n## Testing\n- Use Jest\n- Coverage > 80%\n... (100 more lines)\n\n## TypeScript\n- Enable strict mode\n... (150 more lines)\n```\n\n### After (Progressive Disclosure)\n```markdown\n# CLAUDE.md\n\nReact dashboard for real-time analytics visualization.\n\n## Commands\n- `pnpm dev` - Start development server\n- `pnpm test` - Run tests with coverage\n- `pnpm build` - Production build\n\n## Guidelines\n- [Code Style](.claude\u002Fcode-style.md)\n- [Testing](.claude\u002Ftesting.md)\n- [TypeScript](.claude\u002Ftypescript.md)\n```\n\n---\n\n## Verification\n\nAfter refactoring, verify:\n\n1. **Root file is minimal** - Under 50 lines, only universal info\n2. **Links work** - All referenced files exist\n3. **No contradictions** - Instructions are consistent\n4. **Actionable content** - Every instruction is specific\n5. **Complete coverage** - No instructions were lost (unless flagged for deletion)\n6. **Self-contained files** - Each linked file stands alone\n\n---\n","# Agent MD Refactor\n\nRefactor bloated agent instruction files (AGENTS.md, CLAUDE.md, COPILOT.md, etc.) to follow **progressive disclosure principles** - keeping essentials at root and organizing the rest into linked, categorized files.\n\n---\n\n## Triggers\n\nUse this skill when:\n- \"refactor my AGENTS.md\" \u002F \"refactor my CLAUDE.md\"\n- \"split my agent instructions\"\n- \"organize my CLAUDE.md file\"\n- \"my AGENTS.md is too long\"\n- \"progressive disclosure for my instructions\"\n- \"clean up my agent config\"\n\n---\n\n## Quick Reference\n\n| Phase | Action | Output |\n|-------|--------|--------|\n| 1. Analyze | Find contradictions | List of conflicts to resolve |\n| 2. Extract | Identify essentials | Core instructions for root file |\n| 3. Categorize | Group remaining instructions | Logical categories |\n| 4. Structure | Create file hierarchy | Root + linked files |\n| 5. Prune | Flag for deletion | Redundant\u002Fvague instructions |\n\n---\n\n## Process\n\n### Phase 1: Find Contradictions\n\nIdentify any instructions that conflict with each other.\n\n**Look for:**\n- Contradictory style guidelines (e.g., \"use semicolons\" vs \"no semicolons\")\n- Conflicting workflow instructions\n- Incompatible tool preferences\n- Mutually exclusive patterns\n\n**For each contradiction found:**\n```markdown\n## Contradiction Found\n\n**Instruction A:** [quote]\n**Instruction B:** [quote]\n\n**Question:** Which should take precedence, or should both be conditional?\n```\n\nAsk the user to resolve before proceeding.\n\n---\n\n### Phase 2: Identify the Essentials\n\nExtract ONLY what belongs in the root agent file. The root should be minimal - information that applies to **every single task**.\n\n**Essential content (keep in root):**\n| Category | Example |\n|----------|---------|\n| Project description | One sentence: \"A React dashboard for analytics\" |\n| Package manager | Only if not npm (e.g., \"Uses pnpm\") |\n| Non-standard commands | Custom build\u002Ftest\u002Ftypecheck commands |\n| Critical overrides | Things that MUST override defaults |\n| Universal rules | Applies to 100% of tasks |\n\n**NOT essential (move to linked files):**\n- Language-specific conventions\n- Testing guidelines\n- Code style details\n- Framework patterns\n- Documentation standards\n- Git workflow details\n\n---\n\n### Phase 3: Group the Rest\n\nOrganize remaining instructions into logical categories.\n\n**Common categories:**\n| Category | Contents |\n|----------|----------|\n| `typescript.md` | TS conventions, type patterns, strict mode rules |\n| `testing.md` | Test frameworks, coverage, mocking patterns |\n| `code-style.md` | Formatting, naming, comments, structure |\n| `git-workflow.md` | Commits, branches, PRs, reviews |\n| `architecture.md` | Patterns, folder structure, dependencies |\n| `api-design.md` | REST\u002FGraphQL conventions, error handling |\n| `security.md` | Auth patterns, input validation, secrets |\n| `performance.md` | Optimization rules, caching, lazy loading |\n\n**Grouping rules:**\n1. Each file should be self-contained for its topic\n2. Aim for 3-8 files (not too granular, not too broad)\n3. Name files clearly: `{topic}.md`\n4. Include only actionable instructions\n\n---\n\n### Phase 4: Create the File Structure\n\n**Output structure:**\n```\nproject-root\u002F\n├── CLAUDE.md (or AGENTS.md)     # Minimal root with links\n└── .claude\u002F                      # Or docs\u002Fagent-instructions\u002F\n    ├── typescript.md\n    ├── testing.md\n    ├── code-style.md\n    ├── git-workflow.md\n    └── architecture.md\n```\n\n**Root file template:**\n```markdown\n# Project Name\n\nOne-sentence description of the project.\n\n## Quick Reference\n\n- **Package Manager:** pnpm\n- **Build:** `pnpm build`\n- **Test:** `pnpm test`\n- **Typecheck:** `pnpm typecheck`\n\n## Detailed Instructions\n\nFor specific guidelines, see:\n- [TypeScript Conventions](.claude\u002Ftypescript.md)\n- [Testing Guidelines](.claude\u002Ftesting.md)\n- [Code Style](.claude\u002Fcode-style.md)\n- [Git Workflow](.claude\u002Fgit-workflow.md)\n- [Architecture Patterns](.claude\u002Farchitecture.md)\n```\n\n**Each linked file template:**\n```markdown\n# {Topic} Guidelines\n\n## Overview\nBrief context for when these guidelines apply.\n\n## Rules\n\n### Rule Category 1\n- Specific, actionable instruction\n- Another specific instruction\n\n### Rule Category 2\n- Specific, actionable instruction\n\n## Examples\n\n### Good\n\\`\\`\\`typescript\n\u002F\u002F Example of correct pattern\n\\`\\`\\`\n\n### Avoid\n\\`\\`\\`typescript\n\u002F\u002F Example of what not to do\n\\`\\`\\`\n```\n\n---\n\n### Phase 5: Flag for Deletion\n\nIdentify instructions that should be removed entirely.\n\n**Delete if:**\n| Criterion | Example | Why Delete |\n|-----------|---------|------------|\n| Redundant | \"Use TypeScript\" (in a .ts project) | Agent already knows |\n| Too vague | \"Write clean code\" | Not actionable |\n| Overly obvious | \"Don't introduce bugs\" | Wastes context |\n| Default behavior | \"Use descriptive variable names\" | Standard practice |\n| Outdated | References deprecated APIs | No longer applies |\n\n**Output format:**\n```markdown\n## Flagged for Deletion\n\n| Instruction | Reason |\n|-------------|--------|\n| \"Write clean, maintainable code\" | Too vague to be actionable |\n| \"Use TypeScript\" | Redundant - project is already TS |\n| \"Don't commit secrets\" | Agent already knows this |\n| \"Follow best practices\" | Meaningless without specifics |\n```\n\n---\n\n## Execution Checklist\n\n```\n[ ] Phase 1: All contradictions identified and resolved\n[ ] Phase 2: Root file contains ONLY essentials\n[ ] Phase 3: All remaining instructions categorized\n[ ] Phase 4: File structure created with proper links\n[ ] Phase 5: Redundant\u002Fvague instructions removed\n[ ] Verify: Each linked file is self-contained\n[ ] Verify: Root file is under 50 lines\n[ ] Verify: All links work correctly\n```\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Keeping everything in root | Bloated, hard to maintain | Split into linked files |\n| Too many categories | Fragmentation | Consolidate related topics |\n| Vague instructions | Wastes tokens, no value | Be specific or delete |\n| Duplicating defaults | Agent already knows | Only override when needed |\n| Deep nesting | Hard to navigate | Flat structure with links |\n\n---\n\n## Examples\n\n### Before (Bloated Root)\n```markdown\n# CLAUDE.md\n\nThis is a React project.\n\n## Code Style\n- Use 2 spaces\n- Use semicolons\n- Prefer const over let\n- Use arrow functions\n... (200 more lines)\n\n## Testing\n- Use Jest\n- Coverage > 80%\n... (100 more lines)\n\n## TypeScript\n- Enable strict mode\n... (150 more lines)\n```\n\n### After (Progressive Disclosure)\n```markdown\n# CLAUDE.md\n\nReact dashboard for real-time analytics visualization.\n\n## Commands\n- `pnpm dev` - Start development server\n- `pnpm test` - Run tests with coverage\n- `pnpm build` - Production build\n\n## Guidelines\n- [Code Style](.claude\u002Fcode-style.md)\n- [Testing](.claude\u002Ftesting.md)\n- [TypeScript](.claude\u002Ftypescript.md)\n```\n\n---\n\n## Verification\n\nAfter refactoring, verify:\n\n1. **Root file is minimal** - Under 50 lines, only universal info\n2. **Links work** - All referenced files exist\n3. **No contradictions** - Instructions are consistent\n4. **Actionable content** - Every instruction is specific\n5. **Complete coverage** - No instructions were lost (unless flagged for deletion)\n6. **Self-contained files** - Each linked file stands alone\n\n---\n",{"name":5,"license":14,"description":7},"master","08cc2532077058aa50e6e18f54695bc256c88152","skills\u002Fsoftaworks\u002Fagent-md-refactor","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub","https:\u002F\u002Fgithub.com\u002Fsuperhealth","java engineer","2026-04-06 22:07:23",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add superhealth\u002Fskills-hub --skill agent-md-refactor",{"tool":52,"command":53},"bunx","bunx skills add superhealth\u002Fskills-hub --skill agent-md-refactor",{"tool":55,"command":56},"pnpm","pnpm dlx skills add superhealth\u002Fskills-hub --skill agent-md-refactor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftaworks\u002Fagent-md-refactor\u002FSKILL.md",true,[60,66],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"README.md","REFERENCE","参考文档",7326,"https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftaworks\u002Fagent-md-refactor\u002FREADME.md",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"skill-report.json",9225,"https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftaworks\u002Fagent-md-refactor\u002Fskill-report.json",[71,101,129,142,158,182],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":34},"01M6MC9F3WHV8S8FZ2W4TRB0FE","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fzhanlincui\u002Fvercel-react-best-practices\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"react","vercel react best practices","best practices","vercel","react best practices","data fetching","code","triggers","pages","next","patterns","refactoring","data","Optimization","tasks","guidelines","react components","components","performance","writing",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":111,"publishedAt":34},"01M6MB8KWE1Q5A5KERR7RFTQWP","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-testing-best-practices\u002FSKILL.md",[107,110],{"categoryNo":108,"categoryName":109,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},[112,113,114,83,115,116,117,118,119,120,121,91,122,123,124,125,126,127,128],"vue testing best practices","testing best practices","vue","testing","testing patterns","js","e2e","vitest","use","component","test","mocking","for","utils","e2e testing","github","playwright",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":34},"01M6MB8GK06M6GA4KVYNDV1BZP","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-router-best-practices\u002FSKILL.md",[135],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},[83,114,137,138,139,91,140,141,121,127],"router","vue router best practices","route","navigation","lifecycle",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":34},"01M6MB8DQF21TZMQ9XC3745ERW","vue-pinia-best-practices","Pinia stores, state management patterns, store setup, and reactivity with stores.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-pinia-best-practices\u002FSKILL.md",[148],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},[150,151,114,83,152,153,91,154,155,156,157,127],"vue pinia best practices","pinia","with","store","management","state","state management","setup",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":173,"publishedAt":34},"01M6MB8A7MC08747J9TV4GWQ9A","vue-options-api-best-practices","Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-options-api-best-practices\u002FSKILL.md",[164,165,168],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[114,174,175,176,83,177,178,179,180,93,127,181],"options","vue options api best practices","api","methods","reference","only","context","style",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":34},"01M6MB85ZTQC24Q04X49MM4YXN","vue-development-guides","A collection of best practices and tips for developing applications using Vue.js. This skill MUST be apply when developing, refactoring or reviewing Vue.js or Nuxt projects.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-development-guides\u002FSKILL.md",[188],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},[190,114,191,192,127,193,194,124,195,196,197,117,92,198,199,83],"development","guides","vue development guides","tips","apply","project","nuxt","projects","collection","applications"]