The design language that makes your AI harness better at design.
JavaScript
Sync generated provider output
github-actions[bot]707fb6061c3a
diff --git a/.agent/skills/impeccable/SKILL.md b/.agent/skills/impeccable/SKILL.mdindex dd7e7e5b5..668ccfc54 100644--- a/.agent/skills/impeccable/SKILL.md+++ b/.agent/skills/impeccable/SKILL.md@@ -69,7 +69,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.agent/skills/impeccable/reference/routing.md b/.agent/skills/impeccable/reference/routing.mdindex d17f74140..7c7b3c356 100644--- a/.agent/skills/impeccable/reference/routing.md+++ b/.agent/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.agents/skills/impeccable/SKILL.md b/.agents/skills/impeccable/SKILL.mdindex 9d2a8d715..92f217d7e 100644--- a/.agents/skills/impeccable/SKILL.md+++ b/.agents/skills/impeccable/SKILL.md@@ -66,7 +66,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.agents/skills/impeccable/reference/routing.md b/.agents/skills/impeccable/reference/routing.mdindex e383c067b..6d48b47a0 100644--- a/.agents/skills/impeccable/reference/routing.md+++ b/.agents/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `$impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.claude/skills/impeccable/SKILL.md b/.claude/skills/impeccable/SKILL.mdindex af17455ce..d604d93fa 100644--- a/.claude/skills/impeccable/SKILL.md+++ b/.claude/skills/impeccable/SKILL.md@@ -68,7 +68,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.claude/skills/impeccable/reference/routing.md b/.claude/skills/impeccable/reference/routing.mdindex 1ce74abf2..33bf7fc0d 100644--- a/.claude/skills/impeccable/reference/routing.md+++ b/.claude/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.cursor/skills/impeccable/SKILL.md b/.cursor/skills/impeccable/SKILL.mdindex 578ca2d75..5370e476a 100644--- a/.cursor/skills/impeccable/SKILL.md+++ b/.cursor/skills/impeccable/SKILL.md@@ -66,7 +66,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.cursor/skills/impeccable/reference/routing.md b/.cursor/skills/impeccable/reference/routing.mdindex 6f7bb0406..1d72fe6b3 100644--- a/.cursor/skills/impeccable/reference/routing.md+++ b/.cursor/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.gemini/skills/impeccable/SKILL.md b/.gemini/skills/impeccable/SKILL.mdindex 9ad5a5c8b..9c138e45d 100644--- a/.gemini/skills/impeccable/SKILL.md+++ b/.gemini/skills/impeccable/SKILL.md@@ -65,7 +65,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.gemini/skills/impeccable/reference/routing.md b/.gemini/skills/impeccable/reference/routing.mdindex 4ef37c68e..7cb2c8f92 100644--- a/.gemini/skills/impeccable/reference/routing.md+++ b/.gemini/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.github/skills/impeccable/SKILL.md b/.github/skills/impeccable/SKILL.mdindex d8be00b5b..7737ffbb7 100644--- a/.github/skills/impeccable/SKILL.md+++ b/.github/skills/impeccable/SKILL.md@@ -68,7 +68,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.github/skills/impeccable/reference/routing.md b/.github/skills/impeccable/reference/routing.mdindex 8e3bce5ee..f3767131f 100644--- a/.github/skills/impeccable/reference/routing.md+++ b/.github/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.grok/skills/impeccable/SKILL.md b/.grok/skills/impeccable/SKILL.mdindex aac448851..1f87d90fa 100644--- a/.grok/skills/impeccable/SKILL.md+++ b/.grok/skills/impeccable/SKILL.md@@ -71,7 +71,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.grok/skills/impeccable/reference/routing.md b/.grok/skills/impeccable/reference/routing.mdindex aff3bbd2f..d9fead33b 100644--- a/.grok/skills/impeccable/reference/routing.md+++ b/.grok/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.hermes/skills/impeccable/SKILL.md b/.hermes/skills/impeccable/SKILL.mdindex 55cb30658..28fa925e0 100644--- a/.hermes/skills/impeccable/SKILL.md+++ b/.hermes/skills/impeccable/SKILL.md@@ -66,7 +66,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.hermes/skills/impeccable/reference/routing.md b/.hermes/skills/impeccable/reference/routing.mdindex 41b68205a..f1828dedf 100644--- a/.hermes/skills/impeccable/reference/routing.md+++ b/.hermes/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.kiro/skills/impeccable/SKILL.md b/.kiro/skills/impeccable/SKILL.mdindex 398ec02e5..9052ebd0a 100644--- a/.kiro/skills/impeccable/SKILL.md+++ b/.kiro/skills/impeccable/SKILL.md@@ -66,7 +66,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.kiro/skills/impeccable/reference/routing.md b/.kiro/skills/impeccable/reference/routing.mdindex e739956b0..8ceae94ef 100644--- a/.kiro/skills/impeccable/reference/routing.md+++ b/.kiro/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.opencode/skills/impeccable/SKILL.md b/.opencode/skills/impeccable/SKILL.mdindex b1fa065f9..76be0d71a 100644--- a/.opencode/skills/impeccable/SKILL.md+++ b/.opencode/skills/impeccable/SKILL.md@@ -71,7 +71,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.opencode/skills/impeccable/reference/routing.md b/.opencode/skills/impeccable/reference/routing.mdindex 06ac412d8..17171acfb 100644--- a/.opencode/skills/impeccable/reference/routing.md+++ b/.opencode/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.pi/skills/impeccable/SKILL.md b/.pi/skills/impeccable/SKILL.mdindex 4f4427203..6f321607d 100644--- a/.pi/skills/impeccable/SKILL.md+++ b/.pi/skills/impeccable/SKILL.md@@ -69,7 +69,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.pi/skills/impeccable/reference/routing.md b/.pi/skills/impeccable/reference/routing.mdindex a4a4962f9..532b34bc6 100644--- a/.pi/skills/impeccable/reference/routing.md+++ b/.pi/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.qoder/skills/impeccable/SKILL.md b/.qoder/skills/impeccable/SKILL.mdindex 68b412181..fb6e557f4 100644--- a/.qoder/skills/impeccable/SKILL.md+++ b/.qoder/skills/impeccable/SKILL.md@@ -71,7 +71,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.qoder/skills/impeccable/reference/routing.md b/.qoder/skills/impeccable/reference/routing.mdindex a18137617..aa7114154 100644--- a/.qoder/skills/impeccable/reference/routing.md+++ b/.qoder/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.rovodev/skills/impeccable/SKILL.md b/.rovodev/skills/impeccable/SKILL.mdindex 0d6de5ca6..828187397 100644--- a/.rovodev/skills/impeccable/SKILL.md+++ b/.rovodev/skills/impeccable/SKILL.md@@ -71,7 +71,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.rovodev/skills/impeccable/reference/routing.md b/.rovodev/skills/impeccable/reference/routing.mdindex 59566d51b..69ceef6bd 100644--- a/.rovodev/skills/impeccable/reference/routing.md+++ b/.rovodev/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.trae-cn/skills/impeccable/SKILL.md b/.trae-cn/skills/impeccable/SKILL.mdindex 044ac464c..0f710c555 100644--- a/.trae-cn/skills/impeccable/SKILL.md+++ b/.trae-cn/skills/impeccable/SKILL.md@@ -68,7 +68,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.trae-cn/skills/impeccable/reference/routing.md b/.trae-cn/skills/impeccable/reference/routing.mdindex d13b1850a..ffafd5b0c 100644--- a/.trae-cn/skills/impeccable/reference/routing.md+++ b/.trae-cn/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.trae/skills/impeccable/SKILL.md b/.trae/skills/impeccable/SKILL.mdindex 1ee77d828..f7115ed48 100644--- a/.trae/skills/impeccable/SKILL.md+++ b/.trae/skills/impeccable/SKILL.md@@ -68,7 +68,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.trae/skills/impeccable/reference/routing.md b/.trae/skills/impeccable/reference/routing.mdindex 8f59ac8a3..6fcf89317 100644--- a/.trae/skills/impeccable/reference/routing.md+++ b/.trae/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.veto/skills/impeccable/SKILL.md b/.veto/skills/impeccable/SKILL.mdindex 195212ff1..d1ff2d820 100644--- a/.veto/skills/impeccable/SKILL.md+++ b/.veto/skills/impeccable/SKILL.md@@ -66,7 +66,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.veto/skills/impeccable/reference/routing.md b/.veto/skills/impeccable/reference/routing.mdindex 6a32cb8f0..269edd596 100644--- a/.veto/skills/impeccable/reference/routing.md+++ b/.veto/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/.vibe/skills/impeccable/SKILL.md b/.vibe/skills/impeccable/SKILL.mdindex a317ef454..363f4f9b9 100644--- a/.vibe/skills/impeccable/SKILL.md+++ b/.vibe/skills/impeccable/SKILL.md@@ -70,7 +70,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/.vibe/skills/impeccable/reference/routing.md b/.vibe/skills/impeccable/reference/routing.mdindex 55a845a03..d8a2c17c4 100644--- a/.vibe/skills/impeccable/reference/routing.md+++ b/.vibe/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.diff --git a/plugin/skills/impeccable/SKILL.md b/plugin/skills/impeccable/SKILL.mdindex 27f5e9e77..573c3335d 100644--- a/plugin/skills/impeccable/SKILL.md+++ b/plugin/skills/impeccable/SKILL.md@@ -68,7 +68,8 @@ Choose the mode from the requested surface, not the product, and persist it onlyRouting:- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.-- **Explicit or clearly implied command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.+- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.diff --git a/plugin/skills/impeccable/reference/routing.md b/plugin/skills/impeccable/reference/routing.mdindex a3fe0a94e..5036a3d7d 100644--- a/plugin/skills/impeccable/reference/routing.md+++ b/plugin/skills/impeccable/reference/routing.md@@ -1,4 +1,10 @@-# No-argument routing: the context-aware menu+# Command guidance++## Workflow questions++Give advice without executing commands; the menu below is only for bare invocations. Consult relevant command references as needed for prerequisites and scope. Link to the [docs](https://impeccable.style/docs/) for the broader workflow guide. If the user also requests execution, follow that request.++## No-argument routing: the context-aware menuRead this when the user invokes `/impeccable` with no argument. They are asking "what should I do?" Make the menu context-aware instead of static.