メニュー
Build distinctive, non-generic frontends. Use when designing web UIs, landing pages, marketing sites, portfolios, or any visual frontend where the default "AI slop" aesthetic (Inter/Roboto fonts, purple gradients, generic cards) should be avoided.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Make Claude default to implementing changes rather than just suggesting them. Use when the model keeps proposing edits instead of applying them, or when you want a bias toward action in an agentic coding context.
Raise recall in code review — get Claude to report every bug it finds, including low-confidence ones. Use for code review harnesses, security audits, or any workflow where missing a real bug is worse than a few false positives.
Stop Claude from leaving behind temporary scripts, scratch files, and iteration helpers after a task. Use when you want a clean workspace — no extra files beyond the requested deliverables.
Make Claude's responses shorter and more focused. Use when the model is over-explaining, adding non-essential context, or producing verbose answers for simple lookups.
Make Claude ask before taking destructive or hard-to-reverse actions (rm, force-push, dropping tables, posting publicly). Use in autonomous agents that touch shared systems or in any context where the blast radius of a wrong action is high.
Structured, hypothesis-driven research across large corpora. Use for complex research tasks, literature reviews, competitive analysis, or anywhere Claude needs to synthesize information from many sources with tracked confidence.
| name | vojta-frontend-design |
| description | Build distinctive, non-generic frontends. Use when designing web UIs, landing pages, marketing sites, portfolios, or any visual frontend where the default "AI slop" aesthetic (Inter/Roboto fonts, purple gradients, generic cards) should be avoided. |
When building frontends, inject the snippet below into your working context and follow its guidance. Opus 4.7 has strong design instincts but defaults to a consistent house style (cream backgrounds, serif display, terracotta accents) that reads off for dashboards, dev tools, fintech, healthcare, or enterprise apps.
<frontend_aesthetics>
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white or dark backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character. Use unique fonts, cohesive colors and themes, and animations for effects and micro-interactions.
</frontend_aesthetics>
Specify a concrete alternative. The model follows explicit palette/typography specs precisely. Give hex ranges, type systems, border radii, transition timings.
Propose options before building. For open-ended briefs, offer 4 distinct visual directions (bg hex / accent hex / typeface + one-line rationale), have the user pick, then implement only that direction. This replaces what temperature used to do for design variety.
animation-delay over scattered micro-interactions