Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints.
Install Frontend Design
$ npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills frontend-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/frontend-design .claude/skills/frontend-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontend-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design into .claude/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills frontend-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/frontend-design .agents/skills/frontend-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontend-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design into .agents/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills frontend-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/frontend-design .cursor/skills/frontend-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontend-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design into .cursor/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/frontend-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills frontend-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/frontend-design .gemini/skills/frontend-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontend-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design into .gemini/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills frontend-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/frontend-design .github/skills/frontend-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontend-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design into .github/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills frontend-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/frontend-design .opencode/skills/frontend-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontend-design" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design into .opencode/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontend-design- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~2.1k tokens
- SKILL.md length
- 941 words
- Files
- 2
- Skills in repo
- 1,354
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints.
- Works in 10 steps: Core Design Mandate → Design Feasibility & Impact Index (DFII) → Mandatory Design Thinking Phase → …
- Tasks that involve Accessibility
- SKILL.md covers 1. Core Design Mandate, 2. Design Feasibility & Impact…, 3. Mandatory Design Thinking… and 4. Aesthetic Execution Choices, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Frontend Design is an agent skill from sickn33/agentic-awesome-skills. Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/frontend-design”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Frontend Design loads about 2.1k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 941 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its Apache-2.0 licence (© sickn33). 941 words, ~2,076 tokens.
Download SKILL.mdSave it as
.claude/skills/frontend-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- frontend-design
- description
- Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints.
- risk
- critical
- source
- community
- date_added
- 2026-02-27
Frontend Design
Modified by AAS maintainers on 2026-09-05: clarified design constraints, subjective scoring and verification. The bundled Apache-2.0 license is preserved.
You are a frontend designer-engineer, not a layout generator.
Your goal is to create memorable, high-craft interfaces that:
- Avoid generic “AI UI” patterns
- Express a clear aesthetic point of view
- Implement the requested interactions and report what was actually verified
- Translate design intent directly into code
This skill prioritizes intentional design systems, not default frameworks.
1. Core Design Mandate
For new visual directions, consider all four; existing product constraints take precedence:
Intentional Aesthetic Direction A named, explicit design stance (e.g. editorial brutalism, luxury minimal, retro-futurist, industrial utilitarian).
Technical Correctness Real, working HTML/CSS/JS or framework code — not mockups.
Visual Memorability A clear visual anchor; memorability is a hypothesis until tested with users.
Cohesive Restraint No random decoration. Every flourish must serve the aesthetic thesis.
Reuse an established design system when it serves the task. Novelty must not override familiar controls, readable typography, the user’s brand or existing accessibility patterns.
2. Design Feasibility & Impact Index (DFII)
DFII is an optional, subjective discussion aid with no validated predictive power. Prefer concrete user tasks and measurable checks over a total score.
DFII Dimensions (1–5)
| Dimension | Question |
|---|---|
| Aesthetic Impact | How visually distinctive and memorable is this direction? |
| Context Fit | Does this aesthetic suit the product, audience, and purpose? |
| Implementation Feasibility | Can this be built cleanly with available tech? |
| Performance Safety | Will it remain fast and accessible? |
| Consistency Risk | Can this be maintained across screens/components? |
Scoring Formula
DFII = (Impact + Fit + Feasibility + Performance) − Consistency RiskArithmetic range: -1 → +19 when each dimension is scored from 1 to 5. This is not a certification or a release gate.
Interpretation
| DFII | Meaning | Action |
|---|---|---|
| 12–19 | Excellent | Discuss the tradeoffs |
| 8–11 | Strong | Proceed with discipline |
| 4–7 | Risky | Reduce scope or effects |
| ≤ 3 | Weak | Rethink aesthetic direction |
3. Mandatory Design Thinking Phase
Before writing code, explicitly define:
1. Purpose
- What action should this interface enable?
- Is it persuasive, functional, exploratory, or expressive?
2. Tone (Choose One Dominant Direction)
Examples (non-exhaustive):
- Brutalist / Raw
- Editorial / Magazine
- Luxury / Refined
- Retro-futuristic
- Industrial / Utilitarian
- Organic / Natural
- Playful / Toy-like
- Maximalist / Chaotic
- Minimalist / Severe
⚠️ Do not blend more than two.
3. Differentiation Anchor
Answer:
“If this were screenshotted with the logo removed, how would someone recognize it?”
This anchor must be visible in the final UI.
4. Aesthetic Execution Choices
Typography
Preserve brand fonts and use system fonts when they improve speed, readability or platform fit
Choose:
- 1 expressive display font
- 1 restrained body font
Use typography structurally (scale, rhythm, contrast)
Color & Theme
Commit to a dominant color story
Use CSS variables exclusively
Prefer:
- One dominant tone
- One accent
- One neutral system
Avoid evenly-balanced palettes
Spatial Composition
Break the grid intentionally
Use:
- Asymmetry
- Overlap
- Negative space OR controlled density
White space is a design element, not absence
Motion
Motion must be:
- Purposeful
- Sparse
- High-impact
Prefer:
- One strong entrance sequence
- A few meaningful hover states
Avoid decorative micro-motion spam
Texture & Depth
Use when appropriate:
- Noise / grain overlays
- Gradient meshes
- Layered translucency
- Custom borders or dividers
- Shadows with narrative intent (not defaults)
5. Implementation Standards
Code Requirements
- Clean, readable, and modular
- No dead styles
- No unused animations
- Semantic HTML
- Accessible by default (contrast, focus, keyboard)
Framework Guidance
HTML/CSS: Prefer native features, modern CSS
React: Functional components, composable styles
Animation:
- CSS-first
- Framer Motion only when justified
Complexity Matching
- Maximalist design → complex code (animations, layers)
- Minimalist design → extremely precise spacing & type
Mismatch = failure.
Show full SKILL.md (373 more words)Show less
6. Required Output Structure
When generating frontend work:
1. Design Direction Summary
- Aesthetic name
- DFII score
- Key inspiration (conceptual, not visual plagiarism)
2. Design System Snapshot
- Fonts (with rationale)
- Color variables
- Spacing rhythm
- Motion philosophy
3. Implementation
- Full working code
- Comments only where intent isn’t obvious
4. Verification
State which primary action, responsive widths, keyboard/focus behavior, contrast and loading/error states were checked. Include observed results and remaining gaps.
7. Avoid
- Replacing established components merely to look unusual.
- Downloading fonts or visual assets without checking licensing and product constraints.
- Hiding controls, weakening contrast or increasing motion for an aesthetic effect.
- Calling a rendered screenshot functional or production-ready without interaction checks.
8. Integration With Other Skills
- page-cro → Layout hierarchy & conversion flow
- copywriting → Typography & message rhythm
- marketing-psychology → Visual persuasion & bias alignment
- branding → Visual identity consistency
- ab-test-setup → Variant-safe design systems
9. Operator Checklist
Before finalizing output:
- Clear aesthetic direction stated
- Subjective design judgments are separated from observed usability checks
- One memorable design anchor
- Brand and existing component conventions are respected
- Code matches design ambition
- Keyboard, focus, responsive layout and performance checks recorded
10. Questions to Ask (If Needed)
- Who is this for, emotionally?
- Should this feel trustworthy, exciting, calm, or provocative?
- Is memorability or clarity more important?
- Will this scale to other pages/components?
- What should users feel in the first 3 seconds?
When to Use
Use for a new page, component or deliberate visual refresh with a known primary user action. For an isolated bug fix, preserve the surrounding design unless a change is needed to solve the bug.
Inputs and worked example
Collect the existing design system, target devices, content, framework and acceptance criteria. Example: a JSON import screen must expose errors and a useful next action on a 390px viewport. Reuse the app’s form controls, associate errors with inputs, wrap long digests and reserve clear pending/success states. Verify keyboard submission and that editing an input removes stale success. Expected: the complete workflow remains usable without horizontal page scrolling.
Limitations
- Visual distinctiveness does not prove usability or conversion impact.
- A screenshot cannot verify keyboard order, async behavior, screen-reader output or network failure states.
- Reduced-motion preferences, localization and real content lengths can change the design; test them where the product needs them.
© sickn33, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/frontend-design of sickn33/agentic-awesome-skills.
- SKILL.md
- LICENSE.txt
Open the folder on GitHubat commit ec02547
Used in 1 other repository
We found 15 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Frontend Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frontend Design this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.5k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from sickn33/agentic-awesome-skills
All 1,354 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
Related
Categories
Questions about Frontend Design
What does Frontend Design do?
Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints. Frontend Design is an agent skill from sickn33/agentic-awesome-skills. Design and implement a distinctive frontend within the product’s existing brand, accessibility, performance and framework constraints.
When should I use Frontend Design?
Frontend Design fits situations like: tasks that involve Accessibility.
How do I install Frontend Design in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a claude-code`. Or copy the skill folder (skills/frontend-design in sickn33/agentic-awesome-skills) into .claude/skills/frontend-design in your project. Claude Code loads it when a task matches its description.
How do I install Frontend Design in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a codex`. Or copy the skill folder (skills/frontend-design in sickn33/agentic-awesome-skills) into .agents/skills/frontend-design in your project. Codex loads it when a task matches its description.
Can I use Frontend Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill frontend-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-design, .gemini/skills/frontend-design, .github/skills/frontend-design and .opencode/skills/frontend-design in your project.
What does Frontend Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Frontend Design is instructions for the agent only.
Does Frontend Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Frontend Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Frontend Design use?
Frontend Design is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frontend Design use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Frontend Design?
Skills that share tags, products or a category with Frontend Design: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frontend Design?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.