菜单
Consolidated compressed-communication skill. Use for caveman mode, terse mode, reduced-token replies, /caveman intensity levels, Wenyan variants, or /caveman:compress memory-file compression. Includes both live response style and natural-language file compression into caveman format.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | caveman |
| description | Consolidated compressed-communication skill. Use for caveman mode, terse mode, reduced-token replies, /caveman intensity levels, Wenyan variants, or /caveman:compress memory-file compression. Includes both live response style and natural-language file compression into caveman format. |
Follow workflow.md for live response style.
For /caveman:compress <filepath> or memory-file compression requests, read and follow steps/compress.md.
Use when writing or reviewing code in any language. Covers typed-language rules (TypeScript, Python, Go), naming conventions, file organisation, error handling, import ordering, and universal quality rules. Read project conventions first to identify the stack, then apply only the relevant language sections.
Consolidated UI/UX design skill for product-fit direction, new interface implementation, redesigns, animation and micro-interactions, GSAP/ScrollTrigger choreography, style modes such as soft/minimalist/brutalist, UX critique, UI audits, UI performance optimization, Google Stitch DESIGN.md generation, and complete output enforcement. Use for any request naming design-intelligence, redesign, animate, gsap, soft, minimalist, brutalist, stitch, critique, ui-audit, ui-optimize, output, or any UI/UX/frontend visual work.
Compact the current conversation into a handoff document for another agent to pick up.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Use when writing SQL or migrations, designing schemas, troubleshooting slow queries, implementing Row Level Security, tuning connection pooling, or reviewing database changes. Based on Supabase-leaning Postgres practice.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
