Frontend Design
udecode/plate
Build web interfaces with genuine design quality, not AI slop.
Create distinctive, production-grade frontend interfaces with high design quality.
$ npx skills add boussadjra/vuestrata --skill i-frontend-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boussadjra/vuestrata i-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/boussadjra/vuestrata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/i-frontend-design .claude/skills/i-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 "i-frontend-design" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-frontend-design into .claude/skills/i-frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-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/boussadjra/vuestrata/tree/main/.github/skills/i-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 boussadjra/vuestrata --skill i-frontend-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boussadjra/vuestrata i-frontend-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/i-frontend-design .agents/skills/i-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 "i-frontend-design" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-frontend-design into .agents/skills/i-frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-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 boussadjra/vuestrata --skill i-frontend-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boussadjra/vuestrata i-frontend-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/i-frontend-design .cursor/skills/i-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 "i-frontend-design" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-frontend-design into .cursor/skills/i-frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-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/boussadjra/vuestrata.git --path .github/skills/i-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 boussadjra/vuestrata --skill i-frontend-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boussadjra/vuestrata i-frontend-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/i-frontend-design .gemini/skills/i-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 "i-frontend-design" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-frontend-design into .gemini/skills/i-frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-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 boussadjra/vuestrata i-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 boussadjra/vuestrata --skill i-frontend-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/i-frontend-design .github/skills/i-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 "i-frontend-design" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-frontend-design into .github/skills/i-frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-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 boussadjra/vuestrata --skill i-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 boussadjra/vuestrata i-frontend-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/i-frontend-design .opencode/skills/i-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 "i-frontend-design" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-frontend-design into .opencode/skills/i-frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-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.
i-frontend-designCreate distinctive, production-grade frontend interfaces with high design quality.
I Frontend Design is an agent skill from boussadjra/vuestrata. Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `reference/color-and-contrast.md`, `reference/interaction-design.md` and `reference/motion-design.md`).
It sits in Frontend & Design, covering Design review and critique and Typography. The repository describes itself as: An opinionated Vue application foundation with enforced architecture, generators, and 12 distinct design personalitie. The licence is MIT.
Read from SKILL.md and the folder at commit 73cbf9f. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
I Frontend Design loads about 2k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 976 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.
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.
The full file from boussadjra/vuestrata at commit 73cbf9f, republished under its MIT licence (© boussadjra). 976 words, ~2,026 tokens.
.claude/skills/i-frontend-design/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.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.
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 that is:
→ Consult typography reference for scales, pairing, and loading strategies.
Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font.
DO: Use a modular type scale with fluid sizing (clamp) DO: Vary font weights and sizes to create clear visual hierarchy DON'T: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults DON'T: Use monospace typography as lazy shorthand for "technical/developer" vibes DON'T: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated
→ Consult color reference for OKLCH, palettes, and dark mode.
Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
DO: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes DO: Tint your neutrals toward your brand hue—even a subtle hint creates subconscious cohesion DON'T: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead DON'T: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature DON'T: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds DON'T: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful DON'T: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions
→ Consult spatial reference for grids, rhythm, and container queries.
Create visual rhythm through varied spacing—not the same padding everywhere. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis.
DO: Create visual rhythm through varied spacing—tight groupings, generous separations DO: Use fluid spacing with clamp() that breathes on larger screens DO: Use asymmetry and unexpected compositions; break the grid intentionally for emphasis DON'T: Wrap everything in cards—not everything needs a container DON'T: Nest cards inside cards—visual noise, flatten the hierarchy DON'T: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly DON'T: Use the hero metric layout template—big number, small label, supporting stats, gradient accent DON'T: Center everything—left-aligned text with asymmetric layouts feels more designed DON'T: Use the same spacing everywhere—without rhythm, layouts feel monotonous
DO: Use intentional, purposeful decorative elements that reinforce brand DON'T: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully DON'T: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional DON'T: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful DON'T: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output DON'T: Use modals unless there's truly no better alternative—modals are lazy
→ Consult motion reference for timing, easing, and reduced motion.
Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.
DO: Use motion to convey state changes—entrances, exits, feedback DO: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration DO: For height animations, use grid-template-rows transitions instead of animating height directly DON'T: Animate layout properties (width, height, padding, margin)—use transform and opacity only DON'T: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly
→ Consult interaction reference for forms, focus, and loading patterns.
Make interactions feel fast. Use optimistic UI—update immediately, sync later.
DO: Use progressive disclosure—start simple, reveal sophistication through interaction (basic options first, advanced behind expandable sections; hover states that reveal secondary actions) DO: Design empty states that teach the interface, not just say "nothing here" DO: Make every interactive surface feel intentional and responsive DON'T: Repeat the same information—redundant headers, intros that restate the heading DON'T: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters
→ Consult responsive reference for mobile-first, fluid design, and container queries.
DO: Use container queries (@container) for component-level responsiveness DO: Adapt the interface for different contexts—don't just shrink it DON'T: Hide critical functionality on mobile—adapt the interface, don't amputate it
→ Consult ux-writing reference for labels, errors, and empty states.
DO: Make every word earn its place DON'T: Repeat information users can already see
Critical quality check: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.
A distinctive interface should make someone ask "how was this made?" not "which AI made this?"
Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.
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.
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 across generations.
Remember: the model 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.
© boussadjra, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files in .github/skills/i-frontend-design of boussadjra/vuestrata.
Open the folder on GitHubat commit 73cbf9f
We found 9 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 9 other GitHub owners. This page covers the copy in boussadjra/vuestrata, which our catalogue first saw on October 7, 2026.
I 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 |
|---|---|---|---|---|---|---|
| I Frontend Design this skillboussadjra/vuestrata | 111 | 9 repos | ~2k | Automated safety check: Pass | MIT | |
| Frontend Designudecode/plate | 17k | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Distinctive UI Buildertw93/Waza | 7.2k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Frontend Designjwynia/agent-skills | 170 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Better Interfacetrycompai/crm | 11k | — | ~2k | Automated safety check: Pass | MIT | |
| Design Craftkipperacademy/skillpper | 149 | — | ~3.8k | Automated safety check: Pass | None |
udecode/plate
Build web interfaces with genuine design quality, not AI slop.
tw93/Waza
Builds or restyles production UI with a clear point of view, checks the result against screenshots and responsive states, and hands document typography to other skills.
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
trycompai/crm
User-invoked, cross-discipline interface review that coordinates better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui.
kipperacademy/skillpper
Opinionated product-design skill for building, reviewing, polishing, and iterating on landing pages, apps, dashboards, AI products, design systems, and brand touchpoints.
ginlix-ai/LangAlpha
Design-quality reference for financial-research visual output: typography, color, composition, and avoiding generic AI aesthetics
boussadjra/vuestrata
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use.
boussadjra/vuestrata
Improve interface performance across loading speed, rendering, animations, images, and bundle size.
boussadjra/vuestrata
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management.
boussadjra/vuestrata
Design or improve onboarding flows, empty states, and first-time user experiences.
boussadjra/vuestrata
One-time setup that gathers design context for your project and saves it to your AI config file.
boussadjra/vuestrata
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
Categories
Create distinctive, production-grade frontend interfaces with high design quality. I Frontend Design is an agent skill from boussadjra/vuestrata. Create distinctive, production-grade frontend interfaces with high design quality.
I Frontend Design fits situations like: the user asks to build web components; tasks that involve Design review and critique; tasks that involve Typography.
Run `npx skills add boussadjra/vuestrata --skill i-frontend-design -a claude-code`. Or copy the skill folder (.github/skills/i-frontend-design in boussadjra/vuestrata) into .claude/skills/i-frontend-design in your project. Claude Code loads it when a task matches its description.
Run `npx skills add boussadjra/vuestrata --skill i-frontend-design -a codex`. Or copy the skill folder (.github/skills/i-frontend-design in boussadjra/vuestrata) into .agents/skills/i-frontend-design in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boussadjra/vuestrata --skill i-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/i-frontend-design, .gemini/skills/i-frontend-design, .github/skills/i-frontend-design and .opencode/skills/i-frontend-design in your project.
SKILL.md names no scripts, command-line tools or credentials: I Frontend Design is instructions for the agent only.
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.
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.
I Frontend Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with I Frontend Design: Frontend Design (udecode/plate, 17k stars), Distinctive UI Builder (tw93/Waza, 7.2k stars), Frontend Design (jwynia/agent-skills, 170 stars) and Better Interface (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
boussadjra (a GitHub user) maintains it in boussadjra/vuestrata, which has 111 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 5, 2026.
Source: boussadjra/vuestrata on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.