plankit-cli 1.2.0 → 1.3.0

package/README.md

@@ -77,10 +77,10 @@ plankit status --json
 
 | Agent | What is copied |
 |---|---|
-| `opencode` (default) | `AGENTS.md`-style slash commands under `.opencode/commands/` |
-| `gemini` / `antigravity` | `.gemini/instructions.md` (plus `--global-gemini-skills` under your profile) |
-| `codex` | `AGENTS.md` |
-| `cursor` | `.cursorrules` |
+| `opencode` (default) | Slash commands under `.opencode/commands/` |
+| `gemini` / `antigravity` | `.gemini/instructions.md` + `angular-*` skills (plus `--global-gemini-skills` under your profile) |
+| `codex` | `AGENTS.md` + Angular commands under `.codex/commands/` |
+| `cursor` | `.cursorrules` + Angular command rules under `.cursor/rules/` |
 
 Selection order:
 1. `--agent <name>` flag (non-interactive / CI).
@@ -88,7 +88,13 @@ Selection order:
 3. An interactive numbered menu (when run in a terminal).
 4. The `opencode` default — announced explicitly so the behavior is never silent.
 
-When the Angular command/skill library ships, each agent's `commandBundles` entry installs that agent's `commands/`/`skills/` folder automatically with no CLI changes.
+### Angular command suite
+
+Alongside the phase workflow, `init` installs a per-agent Angular command library that gives your AI assistant 16 deterministic Angular engineering workflows, driven by repository discovery rather than generic prompts:
+
+`component-from`, `feature`, `clone-pattern`, `design-match`, `page-from-api`, `form-from-model`, `table-from-model`, `wire-api`, `signalize`, `extract-component`, `split-component`, `extract-store`, `modernize`, `responsive`, `generate-tests`, `fixtures` — plus a shared `angular-project-discovery` reference.
+
+Every command ships with the exact per-agent binding, so only your selected agent's folder/commands are copied. To include Angular command templates in a custom `templatesDir`, mirror the `templates/angular-commands/` and `templates/angular-skills/` folder layout.
 
 ## Template overrides
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "plankit-cli",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "PlanKit Command Suite CLI for AI Coding Assistants (Antigravity, OpenCode, Codex, Cursor)",
   "main": "src/cli.js",
   "bin": {

package/src/cli.js

@@ -114,10 +114,6 @@ function installCommandBundle(agent, bundleName, config, options, io) {
     };
   }
 
-  if (entry.global && options.dryRun) {
-    return { action: 'info', path: bundleName, message: 'would install to user profile (dry run)' };
-  }
-
   const targetRoot = entry.global
     ? path.join(os.homedir(), ...entry.dest)
     : safeJoin(io.cwd, ...entry.dest);

package/src/commandBundles.js

@@ -15,8 +15,7 @@ export const COMMAND_BUNDLES = {
     label: 'Angular skill suite',
     src: path.join('angular-skills', 'gemini'),
     dest: ['.gemini', 'skills'],
-    kind: 'folder',
-    global: true
+    kind: 'folder'
   },
   'codex-angular': {
     label: 'Angular command suite',
@@ -27,7 +26,7 @@ export const COMMAND_BUNDLES = {
   'cursor-angular': {
     label: 'Angular command suite',
     src: path.join('angular-commands', 'cursor'),
-    dest: ['.cursor'],
+    dest: ['.cursor', 'rules'],
     kind: 'folder'
   }
 };

package/templates/angular-commands/codex/angular-clone-pattern.md

@@ -0,0 +1,23 @@
+# angular-clone-pattern
+> Clone the pattern of an existing feature/page/dialog/store/form/table/service or route config to a new target.
+
+# /clone-pattern
+
+Core primitive: clone an architectural pattern to a new target.
+
+## Workflow
+1. Build a PATTERN MODEL (type, architecture, state style, API style, routing, styling, testing).
+2. Apply: PATTERN + TARGET DOMAIN = IMPLEMENTATION.
+
+## Categories
+- COPY:   folder structure, naming conventions
+- ADAPT:  model, inputs, routes
+- IGNORE: business logic, temporary workarounds, hardcoded styling
+
+## Guardrail
+Identify and refuse to propagate suspicious patterns (e.g. manual subscriptions without teardown) when the dominant repository pattern differs. Never build /clone-tech-debt.
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-component-from.md

@@ -0,0 +1,26 @@
+# angular-component-from
+> Generate a new Angular component using an existing component as the architectural and stylistic reference.
+
+# /component-from
+
+Generate a new component by learning from an existing one instead of blind clone-and-rename.
+
+## Workflow
+1. Analyze the source component and classify what is reusable vs business-specific.
+2. Identify: component structure, file layout, input/output style, inject() convention, tokens, shared components, testing style.
+3. Understand the target domain (optionally from --model).
+4. Generate the new component using the reusable pattern.
+
+## Guardrail
+Never literal clone-and-rename (Product->User). Extract the pattern, understand the target domain, then generate.
+
+## Options
+- --model <Type>     inspect the model to derive appropriate inputs
+- --no-tests         skip generating a spec
+- --interactive      ask before writing
+- --dry-run          show files to create only
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-design-match.md

@@ -0,0 +1,20 @@
+# angular-design-match
+> Match the design language of a generated component to a reference and its surrounding UI.
+
+# /design-match
+
+Align a target with a reference design system.
+
+## Workflow
+1. Discover design vocabulary from reference + neighbors (surfaces, spacing, typography, buttons, icons, states, breakpoints).
+2. Compare semantic regions, not raw DOM.
+3. Transform using priority: shared component -> design token -> existing utility -> existing SCSS pattern -> new style.
+
+## Options
+- --scope <layout|styles|states|all>
+- --auto-reference   search for the closest visually/functionally similar component
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-extract-component.md

@@ -0,0 +1,21 @@
+# angular-extract-component
+> Extract a template region into a child component, deriving the smallest sensible API.
+
+# /extract-component
+
+Extract a child component with a clean boundary.
+
+## Workflow
+1. Analyze all reads/writes/uses inside the template region.
+2. Derive the smallest sensible input/output API.
+3. Prioritize strong boundaries (independent concept, repeated UI, clear I/O) over weak ones (5 lines, tight coupling, 14 inputs).
+4. If extraction makes architecture worse, reject it and recommend an alternative (e.g. a directive/field-group).
+
+## Options
+- --selection        extract a user-specified selection
+- --auto             detect candidate boundaries with confidence scores
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-extract-store.md

@@ -0,0 +1,19 @@
+# angular-extract-store
+> Extract server/user state from a component into a feature-scoped store.
+
+# /extract-store
+
+Move state and state transitions into a store without turning it into a dumping ground.
+
+## Workflow
+1. Detect existing state and classify: SERVER STATE, USER STATE, DERIVED, EPHEMERAL UI.
+2. Keep ephemeral UI (e.g. dialogOpen) local; move server/user/derived state into the store.
+3. Determine provider scope from the app (component / route / feature / root) — do not default everything to root.
+
+## Safeguard
+Keep presentation and DOM logic out of the store. Store = state + transitions + relevant orchestration only.
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-feature.md

@@ -0,0 +1,24 @@
+# angular-feature
+> Build an entire Angular feature while respecting the application existing architecture.
+
+# /feature
+
+High-level feature builder that composes lower-level commands.
+
+## Workflow
+1. Turn the request into capabilities (pages, data, state, UI, routes).
+2. Discover the closest existing feature (e.g. --like customers).
+3. Map capabilities onto existing repository patterns.
+4. Compose: clone-pattern -> component-from -> wire-api -> form-from-model -> generate-tests.
+
+## Safeguard
+Do not invent infrastructure. If existing features do not use stores/repositories/facades, do not introduce them here.
+
+## Options
+- --like <feature>   pattern reference
+- --plan             output only the plan (files, patterns, dependencies, routes, tests) without writing
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-fixtures.md

@@ -0,0 +1,23 @@
+# angular-fixtures
+> Generate reusable fixtures from TypeScript domain models with override support.
+
+# /fixtures
+
+Create test/dev fixtures from existing models.
+
+## Workflow
+1. Given a model (e.g. Order), generate a factory: createOrder(overrides = {}) with sensible defaults and nested factories.
+2. Compose states where valuable.
+
+## Options
+- --count <n>        generate an array of n fixtures
+- --states           generate named states (pendingOrder, completedOrder, cancelledOrder, emptyOrder, largeOrder)
+- --edge-cases       generate edge cases (longName, missingOptionalFields, unicodeName, inactiveUser)
+
+## Integration
+Feeds /component-from, /table-from-model, /generate-tests.
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-form-from-model.md

@@ -0,0 +1,22 @@
+# angular-form-from-model
+> Generate an Angular form from a TypeScript model, inferring field types, controls, and validation.
+
+# /form-from-model
+
+Build forms from domain models with semantic inference.
+
+## Workflow
+1. Understand field semantics (email -> email input, roleId -> select, active -> toggle, birthDate -> date).
+2. Reuse existing project form components (app-field, app-input, app-select, app-toggle).
+3. Discover validation from existing DTOs/sibling forms/schemas; separate KNOWN from INFERRED validation — never hallucinate constraints.
+4. Respect Reactive Forms vs Signal Forms based on project version.
+5. Generate a mapping layer (toCreateDto / toFormModel) instead of coupling DTOs to the UI.
+
+## Options
+- --create | --edit | --dialog | --stepper
+- --like <form>      reference form
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-generate-tests.md

@@ -0,0 +1,20 @@
+# angular-generate-tests
+> Generate behavior-focused tests, deriving behaviors and filling gaps only.
+
+# /generate-tests
+
+Test behavior, not implementation details.
+
+## Workflow
+1. Derive behaviors for the target (form init, validation, derived values, submit blocking, request emission, error display, disabled states).
+2. Find existing coverage and generate only missing tests.
+3. Use given/when/then behavior, not expect(component).toBeTruthy().
+
+## Options
+- --diff             generate tests around changed behaviors only
+- target types: component | service | store | route (--navigation)
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-modernize.md

@@ -0,0 +1,20 @@
+# angular-modernize
+> Orchestrate incremental Angular migrations, building/testing between each stage.
+
+# /modernize
+
+Treat this as a migration orchestrator, not an LLM rewrite.
+
+## Workflow
+1. Determine the Angular version and applicable migrations (standalone, built-in control flow, inject(), signal inputs, output(), signal queries).
+2. Make transformations individually selectable and apply them one at a time.
+3. Categorize: SAFE AUTOMATED (*ngIf->@if), SAFE WITH VERIFICATION (constructor DI->inject()), ARCHITECTURAL (local state->Signals), NOT RECOMMENDED (working RxJS->Signals).
+4. Build/test between every stage.
+
+## Options
+- --control-flow | --inject | --standalone | --signal-inputs | --recommended
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-page-from-api.md

@@ -0,0 +1,23 @@
+# angular-page-from-api
+> Generate an Angular page from a typed API method, deriving UI requirements from the API contract.
+
+# /page-from-api
+
+Scaffold a page that matches the API capabilities.
+
+## Workflow
+1. Inspect the API method signature and return type (e.g. PagedResult<Order>).
+2. Derive likely UI requirements: list, loading, empty, error, pagination; filters/sorting only if the API supports them.
+3. Find the closest existing page pattern and reuse it.
+
+## Critical rule
+Never invent unsupported API functionality. If the API has no sort parameter, do not generate server-side sorting. If no delete endpoint, no Delete button.
+
+## Options
+- --like <page>      reference pattern
+- --crud             scaffold full CRUD (list/details/create/edit/delete) from a typed service
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-project-discovery.md

@@ -0,0 +1,39 @@
+# Angular Project Discovery
+> Discover repository context before any Angular command.
+
+# Angular Project Discovery
+
+Before any Angular command, discover the repository context:
+
+- Angular version
+- Package manager
+- Standalone vs NgModule
+- Signals / RxJS usage
+- State-management libraries
+- Reactive Forms / Signal Forms
+- UI library: Material / PrimeNG / custom
+- Styling: SCSS / CSS / Tailwind / tokens
+- Testing: Vitest / Jest / Karma
+- Existing naming conventions
+- Existing folder architecture
+- Closest comparable implementation
+
+Never modernize code merely because the framework supports it — only when it fits the repository.
+
+## Commands
+- component-from : use an existing component as the reference
+- feature        : build a whole feature respecting existing architecture
+- clone-pattern  : clone any architectural pattern
+- design-match   : align a generated component with the design system
+- page-from-api  : scaffold a page from a typed API
+- form-from-model: build a form from a domain model
+- table-from-model: build a table with semantic columns
+- wire-api       : replace mock data with real API calls
+- signalize      : migrate state to Signals where appropriate
+- extract-component: extract a template region into a child component
+- split-component: decompose an oversized component
+- extract-store  : move state into a feature store
+- modernize      : orchestrate incremental migrations
+- responsive     : make a component responsive per project convention
+- generate-tests : write behavior-focused tests
+- fixtures       : generate model fixtures

package/templates/angular-commands/codex/angular-responsive.md

@@ -0,0 +1,21 @@
+# angular-responsive
+> Make a component responsive following the existing project breakpoints and patterns.
+
+# /responsive
+
+Responsive is not just media queries.
+
+## Workflow
+1. Discover project breakpoints, container widths, grid, mobile nav, table->card behavior, spacing/typography changes, dialog behavior.
+2. Analyze the target and transform fixed layouts (width: 900px; grid 400px 400px) per project conventions.
+3. Test important states: long translated text, empty, loading, validation errors, many actions, large values, small phone, tablet.
+
+## Options
+- --mobile | --tablet | --all
+- --like <page>      follow a reference responsive page
+- --visual           (future) iterate on rendered screenshots
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-signalize.md

@@ -0,0 +1,20 @@
+# angular-signalize
+> Refactor Angular component state to Signals where appropriate, deriving instead of synchronizing.
+
+# /signalize
+
+Judiciously migrate toward Angular Signals.
+
+## Workflow
+1. Classify members: plain value, signal state, computed state, input signal, output, observable stream, resource, form state.
+2. Transform only what benefits: @Input -> input(), @Output -> output(), derived props -> computed(), async -> toSignal(), manual sync -> computed().
+3. Principle: derive instead of synchronize (replace set() effects with computed()).
+4. Keep RxJS where it is genuinely the right tool: websockets, router events, debouncing, retry, complex async orchestration.
+
+## Options
+- --inputs | --outputs | --state | --queries | --all
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-split-component.md

@@ -0,0 +1,21 @@
+# angular-split-component
+> Decompose an oversized component into focused components, controlling coupling and API surface.
+
+# /split-component
+
+Refactor a large component (e.g. 1100+ lines) into focused parts.
+
+## Workflow
+1. Determine why it is large: many UI sections, too much state, business logic, data orchestration, forms.
+2. Choose a decomposition plan (presentational children + orchestrating container; extract a store if state is the issue).
+3. Aim for: cohesion HIGH, coupling LOW, API SMALL, testability IMPROVED.
+4. Avoid turning one large component into 14 tiny ones with 18 inputs / 11 outputs / 6 services.
+
+## Options
+- --plan            show decomposition plan only
+- --apply           execute the plan
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-table-from-model.md

@@ -0,0 +1,22 @@
+# angular-table-from-model
+> Generate an Angular data table from a model or API with semantic column selection and formatting.
+
+# /table-from-model
+
+Produce a table that shows the right columns with correct formatting.
+
+## Workflow
+1. Select columns semantically: show identity, primary data, status, total, created; drop raw FKs/internal fields unless project patterns say otherwise.
+2. Detect formatting: status -> badge, total -> currency, createdAt -> date.
+3. Infer capabilities from the API: paged -> pagination, sort param -> sortable, filter object -> filters, search -> search.
+
+## Options
+- --actions <view,edit,delete>
+- --selectable | --filters | --pagination | --virtual
+- --responsive       follow project table->card transformation
+- --like <table>     reference table
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/codex/angular-wire-api.md

@@ -0,0 +1,24 @@
+# angular-wire-api
+> Replace static UI data with real API calls, choosing the dominant data-access pattern.
+
+# /wire-api
+
+Wire a component to real data using the repository's dominant approach.
+
+## Workflow
+1. Derive UI requirements (collection, search, pagination, delete, refresh).
+2. Map service APIs onto those needs.
+3. Inspect existing patterns first: async pipe, toSignal, resource, feature store, NgRx, SignalStore, custom store.
+4. Choose the DOMINANT project pattern.
+5. Handle all states: initial, loading, loaded, empty, error, refreshing, mutation pending, mutation error.
+
+## Guardrail
+Do not wire unsupported actions. If the UI has Edit but the API has no update, report unresolved functionality instead of wiring.
+
+## Options
+- --preserve-mocks   keep mocks for Storybook/dev-mode
+
+## Execution
+1. Run Angular PROJECT DISCOVERY against the repository.
+2. Apply the workflow above with the provided target.
+3. Report files created/modified and patterns reused.

package/templates/angular-commands/cursor/angular-clone-pattern.md

@@ -0,0 +1,24 @@
+---
+description: Clone the pattern of an existing feature/page/dialog/store/form/table/service or route config to a new target.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-clone-pattern
+
+# /clone-pattern
+
+Core primitive: clone an architectural pattern to a new target.
+
+## Workflow
+1. Build a PATTERN MODEL (type, architecture, state style, API style, routing, styling, testing).
+2. Apply: PATTERN + TARGET DOMAIN = IMPLEMENTATION.
+
+## Categories
+- COPY:   folder structure, naming conventions
+- ADAPT:  model, inputs, routes
+- IGNORE: business logic, temporary workarounds, hardcoded styling
+
+## Guardrail
+Identify and refuse to propagate suspicious patterns (e.g. manual subscriptions without teardown) when the dominant repository pattern differs. Never build /clone-tech-debt.
+
+Follow this workflow whenever asked to clone-pattern a component/feature in this Angular repository.

package/templates/angular-commands/cursor/angular-component-from.md

@@ -0,0 +1,27 @@
+---
+description: Generate a new Angular component using an existing component as the architectural and stylistic reference.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-component-from
+
+# /component-from
+
+Generate a new component by learning from an existing one instead of blind clone-and-rename.
+
+## Workflow
+1. Analyze the source component and classify what is reusable vs business-specific.
+2. Identify: component structure, file layout, input/output style, inject() convention, tokens, shared components, testing style.
+3. Understand the target domain (optionally from --model).
+4. Generate the new component using the reusable pattern.
+
+## Guardrail
+Never literal clone-and-rename (Product->User). Extract the pattern, understand the target domain, then generate.
+
+## Options
+- --model <Type>     inspect the model to derive appropriate inputs
+- --no-tests         skip generating a spec
+- --interactive      ask before writing
+- --dry-run          show files to create only
+
+Follow this workflow whenever asked to component-from a component/feature in this Angular repository.

package/templates/angular-commands/cursor/angular-design-match.md

@@ -0,0 +1,21 @@
+---
+description: Match the design language of a generated component to a reference and its surrounding UI.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-design-match
+
+# /design-match
+
+Align a target with a reference design system.
+
+## Workflow
+1. Discover design vocabulary from reference + neighbors (surfaces, spacing, typography, buttons, icons, states, breakpoints).
+2. Compare semantic regions, not raw DOM.
+3. Transform using priority: shared component -> design token -> existing utility -> existing SCSS pattern -> new style.
+
+## Options
+- --scope <layout|styles|states|all>
+- --auto-reference   search for the closest visually/functionally similar component
+
+Follow this workflow whenever asked to design-match a component/feature in this Angular repository.

package/templates/angular-commands/cursor/angular-extract-component.md

@@ -0,0 +1,22 @@
+---
+description: Extract a template region into a child component, deriving the smallest sensible API.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-extract-component
+
+# /extract-component
+
+Extract a child component with a clean boundary.
+
+## Workflow
+1. Analyze all reads/writes/uses inside the template region.
+2. Derive the smallest sensible input/output API.
+3. Prioritize strong boundaries (independent concept, repeated UI, clear I/O) over weak ones (5 lines, tight coupling, 14 inputs).
+4. If extraction makes architecture worse, reject it and recommend an alternative (e.g. a directive/field-group).
+
+## Options
+- --selection        extract a user-specified selection
+- --auto             detect candidate boundaries with confidence scores
+
+Follow this workflow whenever asked to extract-component a component/feature in this Angular repository.

package/templates/angular-commands/cursor/angular-extract-store.md

@@ -0,0 +1,20 @@
+---
+description: Extract server/user state from a component into a feature-scoped store.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-extract-store
+
+# /extract-store
+
+Move state and state transitions into a store without turning it into a dumping ground.
+
+## Workflow
+1. Detect existing state and classify: SERVER STATE, USER STATE, DERIVED, EPHEMERAL UI.
+2. Keep ephemeral UI (e.g. dialogOpen) local; move server/user/derived state into the store.
+3. Determine provider scope from the app (component / route / feature / root) — do not default everything to root.
+
+## Safeguard
+Keep presentation and DOM logic out of the store. Store = state + transitions + relevant orchestration only.
+
+Follow this workflow whenever asked to extract-store a component/feature in this Angular repository.

package/templates/angular-commands/cursor/angular-feature.md

@@ -0,0 +1,25 @@
+---
+description: Build an entire Angular feature while respecting the application existing architecture.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-feature
+
+# /feature
+
+High-level feature builder that composes lower-level commands.
+
+## Workflow
+1. Turn the request into capabilities (pages, data, state, UI, routes).
+2. Discover the closest existing feature (e.g. --like customers).
+3. Map capabilities onto existing repository patterns.
+4. Compose: clone-pattern -> component-from -> wire-api -> form-from-model -> generate-tests.
+
+## Safeguard
+Do not invent infrastructure. If existing features do not use stores/repositories/facades, do not introduce them here.
+
+## Options
+- --like <feature>   pattern reference
+- --plan             output only the plan (files, patterns, dependencies, routes, tests) without writing
+
+Follow this workflow whenever asked to feature a component/feature in this Angular repository.

package/templates/angular-commands/cursor/angular-fixtures.md

@@ -0,0 +1,24 @@
+---
+description: Generate reusable fixtures from TypeScript domain models with override support.
+globs: **/*.ts, **/*.html, **/*.scss
+---
+
+# angular-fixtures
+
+# /fixtures
+
+Create test/dev fixtures from existing models.
+
+## Workflow
+1. Given a model (e.g. Order), generate a factory: createOrder(overrides = {}) with sensible defaults and nested factories.
+2. Compose states where valuable.
+
+## Options
+- --count <n>        generate an array of n fixtures
+- --states           generate named states (pendingOrder, completedOrder, cancelledOrder, emptyOrder, largeOrder)
+- --edge-cases       generate edge cases (longName, missingOptionalFields, unicodeName, inactiveUser)
+
+## Integration
+Feeds /component-from, /table-from-model, /generate-tests.
+
+Follow this workflow whenever asked to fixtures a component/feature in this Angular repository.