菜单
Toggle lite mode — instructs the assistant to be terse (no preamble, no summaries, no decorative formatting). Use when tokens are limited or you just want shorter answers. Persists across turns until disabled.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | uvs-lite |
| description | Toggle lite mode — instructs the assistant to be terse (no preamble, no summaries, no decorative formatting). Use when tokens are limited or you just want shorter answers. Persists across turns until disabled. |
| argument-hint | [on | off | status] |
| user-invocable | true |
| allowed-tools | ["Write(*)","Read(*)","Bash(mkdir *)","Bash(ls *)","Bash(cat *)"] |
$ARGUMENTS
!ls .uv-suite-state/lite-mode.txt 2>/dev/null && cat .uv-suite-state/lite-mode.txt 2>/dev/null || echo "off (no state file)"
.uv-suite-state/ exists (mkdir -p .uv-suite-state).$ARGUMENTS (lowercase, trim whitespace):
on — write on to .uv-suite-state/lite-mode.txt. Reply: Lite mode: ON.off — write off to .uv-suite-state/lite-mode.txt. Reply: Lite mode: OFF.status or empty — read the file (default off if missing) and reply with the current state.Usage: /uvs-lite [on | off | status] and stop.lite-mode-inject.sh UserPromptSubmit hook reads the file each turn).When ON, a UserPromptSubmit hook injects terseness instructions into the assistant's context every turn:
Also activates if the UVS_LITE=1 environment variable is set (useful for UVS_LITE=1 uv claude pro one-off sessions).
Design system architecture and decompose work into Acts with tasks, dependencies, and cycle budgets. Use after a spec is approved, before coding begins.
Review, test, slop-check, then commit and optionally open a PR. The ship pipeline: one command from "code complete" to "committed and reviewed."
Show all UV Suite skills, agents, hooks, guardrails, and personas. Use when you want to know what's available or how to use a specific feature.
Systematic root-cause debugging. Traces data flow, tests hypotheses, narrows scope. Stops after 3 failed attempts and escalates. Use when something is broken and you don't know why.
Build an interactive prototype as a static React site. For concept exploration, stakeholder demos, presentations, and documentation websites.
Browser-based QA: exercises the running app via Playwright MCP, captures console errors and visual evidence, optionally fixes source bugs with atomic commits and generates regression tests. Three tiers (quick / standard / exhaustive). Writes uv-out/qa-state.md so /uvs-commit and /ship can detect completion and read the health score.