What problem does it solve?
Strict routing mode for prompts prefixed with (best). USE FOR: any turn where the user explicitly wants the safest, smallest-context, highest-discipline execution path. This skill must route into context-budget-guard first, then continue into the task-specific workflow.
Core Features & Use Cases
- Enforces routing through context-budget-guard as the first step when triggered.
- Prioritizes token-efficiency, risk assessment, and disciplined execution for high-stakes prompts.
- Supports seamless handoffs to task-specific workflows (UI, large documents, or artifact-heavy tasks) after the guard.
- Provides deterministic, low-risk execution paths with clear final-token budgeting notes.
Quick Start
When a user message begins with (best) or mentions the best-mode skill, route it through context-budget-guard first, then continue with the task-specific workflow.