[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMCXNMSGKS8VF2201NADJP":3,"skill-same:01M7CMCXNMSGKS8VF2201NADJP":54},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CMCXNMSGKS8VF2201NADJP","vertical-slice-architect",null,"Enforces strict vertical slice architecture, highly granular file-based Single Responsibility Principle (SRP), and domain-driven folder structures before writing any code.","deJames-13\u002Fdeblog","deJames-13","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F109223910?v=4","01M7CFW3B0EF3WP64ZSQR5A7PR","Derick James M. Espinosa","01M7CMBS9K02PJPXCCH7BD7NJ6",1,"MIT","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fvertical-slice-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vertical-slice-architect\ndescription: Enforces strict vertical slice architecture, highly granular file-based Single Responsibility Principle (SRP), and domain-driven folder structures before writing any code.\n---\n\n# Modular Feature Architecture\n\nGuides the structural design of applications by enforcing Screaming Architecture and strict file-level Single Responsibility. \n\n## 🧠 Core Philosophy\n\nYour folder structure should instantly communicate **what the application does**, not what framework it uses. Avoid monolithic files; always default to a highly granular, file-based separation of concerns.\n\n## 🗺️ 1. Mandatory Pre-Planning (Tree First)\n\n**Never start writing implementation code immediately.** You must map out the structure first.\n\n- Always generate and present a clear, hierarchical folder tree representing the intended modules and components.\n- Finalize the structure before fleshing out the actual code.\n\n## 🍰 2. Vertical Slicing (Feature-Driven)\n\nGroup files strictly by **business domain or feature**, rather than by technical responsibility.\n\n- **Do this:** `modules\u002Fuser\u002F`, `modules\u002Fpayments\u002F`, `components\u002Fadmin\u002F`\n- **Avoid this:** `controllers\u002F`, `services\u002F`, `views\u002F`\n\n## 🧩 3. Hyper-Granular Single Responsibility\n\nDo not compact related logic into a single file. Dedicate **one file to one specific action or component**.\n\n- **For APIs\u002FRoutes:** Instead of a massive `user.controller.ts`, break it down into `user.create.ts`, `user.getAll.ts`, `user.update.ts`.\n- **For UIs\u002FComponents:** Instead of a massive `AdminPanel.tsx`, break it down into `AdminHome.tsx`, `AdminSettingsForm.tsx`, and shared bits in `common\u002FModalView.tsx`.\n\n## 🏷️ 4. Explicit Naming Conventions\n\nUse consistent, predictable naming formats (like dot-notation for backend, PascalCase for frontend components) to clearly describe the domain and the exact action.\n\n**Backend Example:**\n```text\nsrc\u002F\n|_ modules\u002F\n   |_ user\u002F\n      |_ user.service.ts\n      |_ user.getAll.ts\n      |_ user.create.ts\n      |_ user.schema.ts\n\n```\n\n**Frontend Example:**\n\n```text\nsrc\u002F\n|_ components\u002F\n   |_ admin\u002F\n      |_ AdminHome.tsx\n      |_ AdminSidebar.tsx\n   |_ common\u002F\n      |_ ModalView.tsx\n      |_ ButtonAction.tsx\n\n```\n","# Modular Feature Architecture\n\nGuides the structural design of applications by enforcing Screaming Architecture and strict file-level Single Responsibility. \n\n## 🧠 Core Philosophy\n\nYour folder structure should instantly communicate **what the application does**, not what framework it uses. Avoid monolithic files; always default to a highly granular, file-based separation of concerns.\n\n## 🗺️ 1. Mandatory Pre-Planning (Tree First)\n\n**Never start writing implementation code immediately.** You must map out the structure first.\n\n- Always generate and present a clear, hierarchical folder tree representing the intended modules and components.\n- Finalize the structure before fleshing out the actual code.\n\n## 🍰 2. Vertical Slicing (Feature-Driven)\n\nGroup files strictly by **business domain or feature**, rather than by technical responsibility.\n\n- **Do this:** `modules\u002Fuser\u002F`, `modules\u002Fpayments\u002F`, `components\u002Fadmin\u002F`\n- **Avoid this:** `controllers\u002F`, `services\u002F`, `views\u002F`\n\n## 🧩 3. Hyper-Granular Single Responsibility\n\nDo not compact related logic into a single file. Dedicate **one file to one specific action or component**.\n\n- **For APIs\u002FRoutes:** Instead of a massive `user.controller.ts`, break it down into `user.create.ts`, `user.getAll.ts`, `user.update.ts`.\n- **For UIs\u002FComponents:** Instead of a massive `AdminPanel.tsx`, break it down into `AdminHome.tsx`, `AdminSettingsForm.tsx`, and shared bits in `common\u002FModalView.tsx`.\n\n## 🏷️ 4. Explicit Naming Conventions\n\nUse consistent, predictable naming formats (like dot-notation for backend, PascalCase for frontend components) to clearly describe the domain and the exact action.\n\n**Backend Example:**\n```text\nsrc\u002F\n|_ modules\u002F\n   |_ user\u002F\n      |_ user.service.ts\n      |_ user.getAll.ts\n      |_ user.create.ts\n      |_ user.schema.ts\n\n```\n\n**Frontend Example:**\n\n```text\nsrc\u002F\n|_ components\u002F\n   |_ admin\u002F\n      |_ AdminHome.tsx\n      |_ AdminSidebar.tsx\n   |_ common\u002F\n      |_ ModalView.tsx\n      |_ ButtonAction.tsx\n\n```\n",{"name":5,"description":7},"main","56b9c98c27212697000a026faeb3a6caa405ed47","web\u002F.agents\u002Fskills\u002Fvertical-slice-architect",0,"https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog","https:\u002F\u002Fdeblog.derickespinosa.app","https:\u002F\u002Fgithub.com\u002FdeJames-13","https:\u002F\u002Fwww.derickespinosa.site\u002F","journey before destination\r\n","2026-09-14 18:56:08",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add deJames-13\u002Fdeblog --skill vertical-slice-architect",{"tool":40,"command":41},"bunx","bunx skills add deJames-13\u002Fdeblog --skill vertical-slice-architect",{"tool":43,"command":44},"pnpm","pnpm dlx skills add deJames-13\u002Fdeblog --skill vertical-slice-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fvertical-slice-architect\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",252,"https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fvertical-slice-architect\u002Fagents\u002Fopenai.yaml",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CMCSQX38862E7CE62DDDT6","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CMCN7HYXZ1VENTFYKAC0XD","tailwind-file-first-vsa","Prioritizes file-based Tailwind CSS styling using Vertical Slice Architecture (VSA) to reduce component bloat and maintain a scalable global design system. Use when structuring Tailwind styles, refactoring utility-bloated JSX\u002FHTML components, or organizing stylesheets into feature domain slices.","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Ftailwind-file-first-vsa\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CMCM0X4HNX2TRH6PKKM0RA","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CMCHFM31PQ629P5SG0HV0J","angular-new-app","Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fangular-new-app\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CMCCN6AXD0AVMP943P3C6J","angular-developer","Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fangular-developer\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CMC7QGJ6XQE2A73HNBPDVT","angular-architect","Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance. Use when building Angular 17+ applications with standalone components or signals, setting up NgRx stores, establishing RxJS reactive patterns, performance tuning, or writing Angular tests for enterprise apps.","https:\u002F\u002Fgithub.com\u002FdeJames-13\u002Fdeblog\u002Fblob\u002Fmain\u002Fweb\u002F.agents\u002Fskills\u002Fangular-architect\u002FSKILL.md",[],[]]