菜单
Extracts business rules from a module (backend + frontend) and produces three tables: Product view (business concepts), Backend dev view (type + source), Frontend dev view (type + source). Saves to docs/business-rules/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit naming quality (files, functions, types, variables, folders) without reading the code. Takes names as input and reports what Claude understands from each name alone. Judges three axes: Screaming Architecture (does the name reveal the domain?), Clean Code (full words, intention-revealing, no abbreviations), and Ubiquitous Language (vocabulary consistency across the codebase). Useful to validate that names self-document.
Strategic DDD guide for this project (fullstack — backend + frontend share the same bounded contexts). Use to slice the domain into bounded contexts, define ubiquitous language, create a new business module, analyze boundaries between contexts. Tactical patterns follow Clean Architecture (see architecture-backend and architecture-frontend skills).
Runs a Big Picture Event Storming session on a bounded context or the entire codebase (backend + frontend). Discovers domain events, commands, entities, context boundaries, frontend projections (hooks, presenters, views). Produces a structured document in docs/ddd/.
Autonomous frontend feature implementation via spec-driven development. Orchestrates a frontend-planner and a frontend-implementer with architecture-frontend preloaded. Applies Humble Object pattern to views, MVVM structure with Presenter classes + Zod ViewModels, singleton registry DI. Consumes specs produced by /product-manager. For backend features, use /implement-feature instead.
Feature challenge and specification. Use to define a feature, write acceptance criteria, scope a ticket, produce INVEST specs with custom DSL in docs/specs/. Refuses vague scopes and forces clarification.
Discover implicit team conventions (tribal knowledge) in a codebase. Spawns parallel sub-agents to analyze 6 axes: naming, error handling, testing, architecture, git workflow, and code idioms. Generates a structured report in docs/tribal-knowledge/.
| name | business-rules-extractor |
| description | Extracts business rules from a module (backend + frontend) and produces three tables: Product view (business concepts), Backend dev view (type + source), Frontend dev view (type + source). Saves to docs/business-rules/. |
| triggers | ["business.*rules","règles.*métier","extraire.*règles","business rules"] |
Extracts business rules from a module (backend + frontend) and produces three tables: Product view (business concepts), Backend dev view, Frontend dev view. A Bounded Context spans both workspaces — rules may live in backend entities/usecases/guards AND in frontend presenters/hooks/viewmodel schemas.
/business-rules-extractor <module>Extract from the user message:
Spawn the business-rules-extractor agent with this prompt:
Module: <module>
Focus: <focus or "complete">
Extract all business rules from the module according to your mission.
Use subagent_type: "business-rules-extractor" and model: "sonnet".
Save the result in docs/business-rules/<module>.md.
Display the agent result as-is — do not summarize, do not reformat.
/business-rules-extractor shipping
/business-rules-extractor tracking focus validation
/business-rules-extractor billing