AGENT SKILL

vertical-slice-architect

Enforces strict vertical slice architecture, highly granular file-based Single Responsibility Principle (SRP), and domain-driven folder structures before writing any code.

License 许可
MIT
所属仓库
deJames-13/deblog
最近更新
2026-09-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
vertical-slice-architect
description
Enforces strict vertical slice architecture, highly granular file-based Single Responsibility Principle (SRP), and domain-driven folder structures before writing any code.

02 资源文件 1

03 SKILL.md 正文

Modular Feature Architecture

Guides the structural design of applications by enforcing Screaming Architecture and strict file-level Single Responsibility.

🧠 Core Philosophy

Your 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.

🗺️ 1. Mandatory Pre-Planning (Tree First)

Never start writing implementation code immediately. You must map out the structure first.

  • Always generate and present a clear, hierarchical folder tree representing the intended modules and components.
  • Finalize the structure before fleshing out the actual code.

🍰 2. Vertical Slicing (Feature-Driven)

Group files strictly by business domain or feature, rather than by technical responsibility.

  • Do this: modules/user/, modules/payments/, components/admin/
  • Avoid this: controllers/, services/, views/

🧩 3. Hyper-Granular Single Responsibility

Do not compact related logic into a single file. Dedicate one file to one specific action or component.

  • For APIs/Routes: Instead of a massive user.controller.ts, break it down into user.create.ts, user.getAll.ts, user.update.ts.
  • For UIs/Components: Instead of a massive AdminPanel.tsx, break it down into AdminHome.tsx, AdminSettingsForm.tsx, and shared bits in common/ModalView.tsx.

🏷️ 4. Explicit Naming Conventions

Use consistent, predictable naming formats (like dot-notation for backend, PascalCase for frontend components) to clearly describe the domain and the exact action.

Backend Example:

src/
|_ modules/
   |_ user/
      |_ user.service.ts
      |_ user.getAll.ts
      |_ user.create.ts
      |_ user.schema.ts

Frontend Example:

src/
|_ components/
   |_ admin/
      |_ AdminHome.tsx
      |_ AdminSidebar.tsx
   |_ common/
      |_ ModalView.tsx
      |_ ButtonAction.tsx

04 同仓库更多 Skills

deJames-13
deJames-13/deblog

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.

★ 1
deJames-13
deJames-13/deblog

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/HTML components, or organizing stylesheets into feature domain slices.

★ 1
deJames-13
deJames-13/deblog

grill-me

A relentless interview to sharpen a plan or design.

★ 1
deJames-13
deJames-13/deblog

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.

★ 1
deJames-13
deJames-13/deblog

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.

★ 1
deJames-13
deJames-13/deblog

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.

★ 1