feat(agents): add design gate for automatic ui-ux-pro-max detection
Lightweight skills (feat, hotfix, bugfix) had zero plugin awareness — design tasks ran without ui-ux-pro-max even when relevant. Add a design gate (lib/design-gate.md) that auto-detects UI/style signals in task description and filesystem, then asks the user to activate ui-ux-pro-max if inactive. Orchestrators already handle this via their STEP 0 plugin-check. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
+8
-1
@@ -39,6 +39,13 @@ Print a one-line scope confirmation:
|
||||
FEAT: <feature name> — ~<N> files, <brief approach>
|
||||
```
|
||||
|
||||
## STEP 0.5 — DESIGN GATE
|
||||
|
||||
Follow `$HOME/.claude/lib/design-gate.md`:
|
||||
- Scan $ARGUMENTS and target files for design/UI/style signals.
|
||||
- If signals found and `ui-ux-pro-max` inactive → ask user to activate.
|
||||
- If no signals → skip (zero overhead).
|
||||
|
||||
## STEP 1 — MINI-PLAN
|
||||
|
||||
Quick mental model, not a formal plan document:
|
||||
@@ -116,7 +123,7 @@ Execute in automatic mode:
|
||||
|
||||
## RULES
|
||||
- Max 5 files. If more needed → `/ship-feature`.
|
||||
- No plugin check (not an orchestrator).
|
||||
- Design gate only (not full plugin check). See STEP 0.5.
|
||||
- No brainstorm/design phase (if needed → `/ship-feature`).
|
||||
- No subagents — direct implementation.
|
||||
- Keep scope tight. If scope creep happens mid-work, stop
|
||||
|
||||
Reference in New Issue
Block a user