菜单
Optional terse commit message generator. Produces compact commit messages that preserve the why and follow the repo's usual style unless the user or repo convention says otherwise. Use when the user asks for terse, compact, or short commit wording, or /caveman-commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.
Build high-quality image generation and edit prompts from user intent using prompt structures proven across prompts.chat examples and OpenAI image prompting guidance.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
| name | caveman-commit |
| description | Optional terse commit message generator. Produces compact commit messages that preserve the why and follow the repo's usual style unless the user or repo convention says otherwise. Use when the user asks for terse, compact, or short commit wording, or /caveman-commit. |
Use this skill when the user wants a tighter commit message than the default writing style, not for ordinary commit message requests.
Always include a body for breaking changes, security fixes, risky migrations, data migrations, irreversible changes, destructive changes, and reverts. Keep warnings explicit. Do not over-compress the context in those cases.
Generate the message only. Do not stage files, amend commits, or run git commit. When no caller-specified exact output format is provided, output a paste-ready message in a code block. Normal English only.
