Agent skill

I Frontend Design

by boussadjra in boussadjra/vuestrata

Create distinctive, production-grade frontend interfaces with high design quality.

MITAuto-check passedFrontend & Design

Install I Frontend Design

skills CLI
$ npx skills add boussadjra/vuestrata --skill i-frontend-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install boussadjra/vuestrata i-frontend-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
i-frontend-design
GitHub stars
111
Used in
9 other repos
Token cost
~2k tokens
SKILL.md length
976 words
Files
8
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Create distinctive, production-grade frontend interfaces with high design quality.

  • The user asks to build web components
  • SKILL.md covers Design Direction, Frontend Aesthetics Guidelines, The AI Slop Test and Implementation Principles
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Design review and critique

What it does

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.

When your agent uses it

  • The user asks to build web components
  • Tasks that involve Design review and critique
  • Tasks that involve Typography

Example prompts

  • “/i-frontend-design”

What it can do on your machine

Read from SKILL.md and the folder at commit 73cbf9f. 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

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.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~2k

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 boussadjra/vuestrata at commit 73cbf9f, republished under its MIT licence (© boussadjra). 976 words, ~2,026 tokens.

Download SKILL.mdSave it as .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.
name
i-frontend-design
description
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.

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.

Design Direction

Commit to a BOLD aesthetic direction:

  • Purpose: What problem does this interface solve? Who uses it?
  • Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
  • Constraints: Technical requirements (framework, performance, accessibility).
  • Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?

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:

  • Production-grade and functional
  • Visually striking and memorable
  • Cohesive with a clear aesthetic point-of-view
  • Meticulously refined in every detail

Frontend Aesthetics Guidelines

Typography

→ 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

Color & Theme

→ 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

Layout & Space

→ 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

Visual Details

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

Show full SKILL.md (393 more words)Show less
Motion

→ 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

Interaction

→ 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

Responsive

→ 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

UX Writing

→ 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


The AI Slop Test

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.


Implementation Principles

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

Files

SKILL.md and 7 other files in .github/skills/i-frontend-design of boussadjra/vuestrata.

  • SKILL.md
  • reference/color-and-contrast.md
  • reference/interaction-design.md
  • reference/motion-design.md
  • reference/responsive-design.md
  • reference/spatial-design.md
  • reference/typography.md
  • reference/ux-writing.md

Open the folder on GitHubat commit 73cbf9f

Used in 9 other repositories

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.

Compare with similar skills

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.

I Frontend Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
I Frontend Design this skillboussadjra/vuestrata1119 repos~2kAutomated safety check: PassMIT
Frontend Designudecode/plate17k—~3.6kAutomated safety check: PassCustom licence
Distinctive UI Buildertw93/Waza7.2k—~3.7kAutomated safety check: PassMIT
Frontend Designjwynia/agent-skills170—~3.2kAutomated safety check: PassMIT
Better Interfacetrycompai/crm11k—~2kAutomated safety check: PassMIT
Design Craftkipperacademy/skillpper149—~3.8kAutomated safety check: PassNone

Similar skills

  • Frontend Design

    udecode/plate

    Build web interfaces with genuine design quality, not AI slop.

    17k GitHub stars~3.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • 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.

    7.2k GitHub stars~3.7k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Frontend & DesignAuto-check passed
  • Better Interface

    trycompai/crm

    User-invoked, cross-discipline interface review that coordinates better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui.

    11k GitHub stars~2k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Design Craft

    kipperacademy/skillpper

    Opinionated product-design skill for building, reviewing, polishing, and iterating on landing pages, apps, dashboards, AI products, design systems, and brand touchpoints.

    149 GitHub stars~3.8k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • UI Design

    ginlix-ai/LangAlpha

    Design-quality reference for financial-research visual output: typography, color, composition, and avoiding generic AI aesthetics

    1.8k GitHub stars~2.9k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from boussadjra/vuestrata

All 21 skills in this repo
  • I Delight

    boussadjra/vuestrata

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use.

    111 GitHub starsUsed in 11 repos~2.6k tokens
    Auto-check passed
  • I Optimize

    boussadjra/vuestrata

    Improve interface performance across loading speed, rendering, animations, images, and bundle size.

    111 GitHub starsUsed in 11 repos~1.9k tokens
    Auto-check passed
  • I Harden

    boussadjra/vuestrata

    Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management.

    111 GitHub starsUsed in 7 repos~2.3k tokens
    Auto-check passed
  • I Onboard

    boussadjra/vuestrata

    Design or improve onboarding flows, empty states, and first-time user experiences.

    111 GitHub starsUsed in 7 repos~2k tokens
    Auto-check passed
  • I Teach Impeccable

    boussadjra/vuestrata

    One-time setup that gathers design context for your project and saves it to your AI config file.

    111 GitHub starsUsed in 6 repos~672 tokens
    Auto-check passed
  • I Animate

    boussadjra/vuestrata

    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

    111 GitHub starsUsed in 4 repos~2.1k tokens
    Auto-check passed

Questions about I Frontend Design

What does I Frontend Design do?

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.

When should I use I Frontend Design?

I Frontend Design fits situations like: the user asks to build web components; tasks that involve Design review and critique; tasks that involve Typography.

How do I install I Frontend Design in Claude Code?

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.

How do I install I Frontend Design in Codex?

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.

Can I use I 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 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.

What does I Frontend Design need to run?

SKILL.md names no scripts, command-line tools or credentials: I Frontend Design is instructions for the agent only.

Does I 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 I 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 I Frontend Design use?

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.

How many tokens does I Frontend Design use?

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.

What are the alternatives to I Frontend Design?

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.

Who maintains I Frontend Design?

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.