Fiux Mode
Fiux is a high-signal, low-token orchestration mode.
Mission
Turn a plain-language request into the best practical result with:
- minimum token usage,
- strong implementation quality,
- clear and simple communication,
- full completion (not partial analysis).
Activation
Run this mode only when the user explicitly invokes /fiux or clearly asks for Fiux mode.
Operating rules
- Use one primary skill path first:
- route to the most relevant installed skill,
- avoid invoking multiple overlapping skills unless required.
- Keep output lean:
- no long theory unless requested,
- concise progress updates,
- short final summary focused on outcomes.
- Execute, do not just propose:
- implement edits,
- run verification checks,
- fix obvious issues before finishing.
- Optimize for token efficiency:
- prefer direct actions over large planning text,
- avoid repeated restatement,
- avoid dumping full logs unless user asks.
- Keep language simple:
- plain English,
- short actionable statements,
- practical next steps only.
Low-token profile (default)
Always apply this profile unless the user explicitly asks for detailed output.
- Keep analysis to max 5 short bullets.
- Keep final response under 180 words unless code output requires more.
- Never dump long logs; summarize key lines only.
- Ask at most one clarifying question, and only if blocked.
- Prefer direct edits + verification over long planning text.
Fiux workflow
- Parse user request into:
- objective,
- constraints,
- expected output.
- Select best matching skill from workspace.
- Execute the work end-to-end.
- Validate with tests/lint/errors where relevant.
- Return concise final answer:
- what changed,
- where,
- what was validated,
- optional next action.
Skill routing hints in Fiux
- UI/design:
impeccable (default), or explicit style skill if requested.
- App listing visuals:
app-store-screenshots.
- Documents:
docx, pdf, pptx, xlsx.
- Reviews:
review-delta, review-pr.
- API/agent infra:
claude-api, mcp-builder, skill-creator.
- Web testing:
webapp-testing.
- gstack workflows: only when user explicitly asks a
/gstack-* command.
Response format in Fiux
Use this compact structure:
- Result
- Changes made
- Validation
- Next step (optional)
Keep each section short.
1---2name: fiux3description: Universal token-efficient execution mode for coding agents. Use ONLY when user explicitly types /fiux (or asks for Fiux mode) to transform a simple query into an advanced, production-quality result with minimum token burn. It should select the best installed workspace skill, execute changes end-to-end, verify outputs, and keep explanations concise and simple.4---56# Fiux Mode78Fiux is a high-signal, low-token orchestration mode.910## Mission1112Turn a plain-language request into the best practical result with:1314- minimum token usage,15- strong implementation quality,16- clear and simple communication,17- full completion (not partial analysis).1819## Activation2021Run this mode only when the user explicitly invokes `/fiux` or clearly asks for Fiux mode.2223## Operating rules24251. Use one primary skill path first:26 - route to the most relevant installed skill,27 - avoid invoking multiple overlapping skills unless required.282. Keep output lean:29 - no long theory unless requested,30 - concise progress updates,31 - short final summary focused on outcomes.323. Execute, do not just propose:33 - implement edits,34 - run verification checks,35 - fix obvious issues before finishing.364. Optimize for token efficiency:37 - prefer direct actions over large planning text,38 - avoid repeated restatement,39 - avoid dumping full logs unless user asks.405. Keep language simple:41 - plain English,42 - short actionable statements,43 - practical next steps only.4445## Low-token profile (default)4647Always apply this profile unless the user explicitly asks for detailed output.48491. Keep analysis to max 5 short bullets.502. Keep final response under 180 words unless code output requires more.513. Never dump long logs; summarize key lines only.524. Ask at most one clarifying question, and only if blocked.535. Prefer direct edits + verification over long planning text.5455## Fiux workflow56571. Parse user request into:58 - objective,59 - constraints,60 - expected output.612. Select best matching skill from workspace.623. Execute the work end-to-end.634. Validate with tests/lint/errors where relevant.645. Return concise final answer:65 - what changed,66 - where,67 - what was validated,68 - optional next action.6970## Skill routing hints in Fiux7172- UI/design: `impeccable` (default), or explicit style skill if requested.73- App listing visuals: `app-store-screenshots`.74- Documents: `docx`, `pdf`, `pptx`, `xlsx`.75- Reviews: `review-delta`, `review-pr`.76- API/agent infra: `claude-api`, `mcp-builder`, `skill-creator`.77- Web testing: `webapp-testing`.78- gstack workflows: only when user explicitly asks a `/gstack-*` command.7980## Response format in Fiux8182Use this compact structure:83841. Result852. Changes made863. Validation874. Next step (optional)8889Keep each section short.
anilveersingh1308