القائمة
Optional terse code review comment style. Produces short, actionable review comments with location, problem, and suggested fix direction. Use when the user asks for terse review feedback, one-line review comments, or /caveman-review.
التثبيت باستخدام 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-review |
| description | Optional terse code review comment style. Produces short, actionable review comments with location, problem, and suggested fix direction. Use when the user asks for terse review feedback, one-line review comments, or /caveman-review. |
Use this skill when the user wants code review comments shorter than the default review style.
file:L<line>: <problem>. Suggest <fix direction>.bug, risk, nit, q.Use normal paragraph form for security findings, irreversible or destructive changes, risky migrations, auth or data-loss risk, architectural disagreements, or onboarding-heavy feedback where the author needs more rationale. Keep warnings explicit. Resume terse comments after that.
Reviews only. Do not write code patches, change reviewer verdict contracts, or run verification tools. For ad-hoc human review comments, output comments ready to paste in a human review thread. Use normal human comment style unless the caller specifies another format.