القائمة
Load when creating or reviewing production-grade frontend components, pages, layouts, visual polish, interaction design, or non-generic UI aesthetics.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Load when backend API work touches authentication, authorization, rate limiting, CORS, input validation, public endpoints, or security remediation in Mandate402.
Load when architecture choices, ADRs, trade-off evaluation, technical debt, or pattern selection need explicit decision records for Mandate402.
Load when designing or reviewing backend systems, APIs, auth, databases, security, performance, scalability, CI/CD, monitoring, or production runtime patterns.
Load when reviewing Mandate402 code for secrets, auth, authorization, input validation, payment safety, blockchain integration, or release security risks.
Load when testing Cloudflare Workers, Vitest worker pools, binding mocks, integration tests, coverage, or worker test failures.
Load when planning or building React/Next.js UI with CO-STAR structure, design tokens, dashboards, hero sections, or custom UI prompts.
| name | frontend-design |
| description | Load when creating or reviewing production-grade frontend components, pages, layouts, visual polish, interaction design, or non-generic UI aesthetics. |
| license | MIT |
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
Before coding, understand the context and commit to a BOLD aesthetic direction:
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
Focus on:
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
Issue: Generic font choices (Inter, Arial, Roboto) Solution: Use distinctive font pairings from Google Fonts or custom fonts. Examples: display fonts (Playfair Display, Bebas Neue, Archivo Black) paired with refined body fonts (Source Serif, Crimson Text, Work Sans).
Issue: Poor hierarchy and readability Solution: Establish clear type scale with CSS variables. Use size, weight, and spacing to create visual hierarchy.
Issue: Clichéd color schemes (purple gradients on white) Solution: Commit to bold, contextual color choices. Use CSS variables for consistency. Consider: monochromatic with one accent, high-contrast brutalism, muted earth tones, vibrant complementary pairs.
Issue: Low contrast affecting accessibility Solution: Verify color contrast ratios meet WCAG AA (4.5:1 for text, 3:1 for large text). Use tools like WebAIM Contrast Checker.
Issue: Predictable, cookie-cutter layouts Solution: Experiment with asymmetry, overlapping elements, diagonal flow, grid-breaking components. Use CSS Grid and Flexbox creatively.
Issue: Responsive breakpoints failing Solution: Test at 320px, 768px, 1024px, 1440px. Use fluid typography (clamp()) and container queries.
Issue: Excessive or jarring animations
Solution: Use subtle, purposeful animations. Respect prefers-reduced-motion. Focus on one well-orchestrated page load rather than scattered micro-interactions.
Issue: Performance problems from animations
Solution: Prefer CSS animations over JavaScript. Use transform and opacity (GPU-accelerated). Avoid animating width, height, top, left.
Issue: Missing keyboard navigation Solution: Ensure all interactive elements are keyboard accessible. Add visible focus states.
Issue: Poor semantic HTML
Solution: Use semantic tags (<nav>, <main>, <article>, <section>). Add ARIA labels where needed.
Issue: Missing alt text on images
Solution: Add descriptive alt text for images. Use empty alt (alt="") for decorative images.
After creating a design, verify:
prefers-reduced-motiontransform, opacity)# Test responsive breakpoints
# Open browser DevTools → Toggle device toolbar
# Test at: 320px, 768px, 1024px, 1440px, 1920px
# Check color contrast
# Use WebAIM Contrast Checker: https://webaim.org/resources/contrastchecker/
# Test keyboard navigation
# Tab through all interactive elements
# Verify visible focus states
# Test with screen reader (VoiceOver on Mac, NVDA on Windows)
# Open browser DevTools → Performance tab
# Record page load and interactions
# Look for layout shifts (CLS)
# Verify animations run at 60fps
# Check for memory leaks with long animations