frontend-design — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited frontend-design (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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 any aesthetic decision, run the ui-ux-pro-max design system generator:
py ~/.claude/skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system -p "Project Name"Extract from the user request:
The generator returns: pattern, style, color palette, typography pairing, effects, and anti-patterns to avoid. Use this as the foundation — then apply the bold aesthetic direction below to make it distinctive and unforgettable.
To persist the design system across sessions (recommended for multi-page projects):
py ~/.claude/skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"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.
This skill applies equally to server-rendered HTML. When the context is a Jinja2/Django/Flask template:
{% block %} / {% for %} / {{ var }} as the data layer — design lives in CSS, not in template logicbase.htmlbase.html design system → page templates extend itWhen building admin/monitoring dashboards (KPI + table + detail pages), use this structure:
base.html — CSS variables, nav, global components
├── list page — KPI row (colored stat cards) + filterable table
├── detail page — entity card (score/ring/metric-row) + sub-tables
└── stats page — chart panels (bar charts) + ranking tablesComponent vocabulary for dark dashboards:
| Class | Purpose |
|---|---|
.kpi / .kpi-row | Stat cards with top color strip |
.s-ring (SVG) | Score ring: r=13, circumference=82, stroke-dasharray="{{dash}} 82", rotate(-90deg) |
.badge-SEVERITY | Severity pill chips (CRITICAL / HIGH / MEDIUM / LOW) |
.sig-col / .sig-row | Horizontal signal bars (width proportional to score%) |
.bchart / .brow | Bar chart rows (label + track + fill + stat) |
.sec-hdr | Section header with decorative right-extending line |
.panel / .panel-hdr | Surface card with uppercase header |
.t-buy / .t-sell | BUY/SELL direction indicators |
.res-won / .res-lost | Outcome result indicators (✓/✗) |
SVG score ring formula: dash = floor(score / 100 × 82), where 82 = floor(2π × 13). For larger rings scale proportionally: r=20 → C=126.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.