agentmods.dev

design-taste-frontend-v1

design-taste-frontend-v1 is a skill for Claude Code, Codex from wedabro/bro-skills. It costs 61 tokens per session (5,125 once invoked), scanned A, a copy of design-taste-frontend-v1, MIT.

A set of frontend design rules for building interfaces with a distinctive visual style, controlled motion, and deliberate spacing and typography. It is the original version kept for projects that need its exact behavior.

In plain words
What is it for?
Use it when generating or editing frontend code and when you need a specific balance of visual variety, animation, and information density. It also requires checking the project's package file before using third-party libraries.
Why use it?
It gives an agent a consistent design baseline and prevents it from making arbitrary visual choices or assuming that libraries are already installed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

not rated 2repo 16d ago A scan 61 tokens copy · 97% MIT

Good fit Use it when generating or editing frontend code and when you need a specific balance of visual variety, animation, and information density. It also requires checking the project's package file before using third-party libraries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wedabro/bro-skills/design-taste-frontend-v1
View source ↗ wedabro/bro-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wedabro/bro-skills --skill design-taste-frontend-v1
Clone the repo
git clone --depth 1 https://github.com/wedabro/bro-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-taste-frontend-v1

README.md
[![agentmods](https://agentmods.dev/badge/skills/wedabro/bro-skills/design-taste-frontend-v1/github.svg)](https://agentmods.dev/skills/wedabro/bro-skills/design-taste-frontend-v1)
Your own site
<a href="https://agentmods.dev/skills/wedabro/bro-skills/design-taste-frontend-v1"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/design-taste-frontend-v1/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-taste-frontend-v1

Your own site · 80×15
<a href="https://agentmods.dev/skills/wedabro/bro-skills/design-taste-frontend-v1"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/design-taste-frontend-v1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,125 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.05125
Opus 5 $0.00030 $0.02563
Sonnet 5 $0.00012 $0.01025
Haiku 4.5 $0.00006 $0.00513

Measured 12d ago against content hash d03fc304c6e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-taste-frontend-v1 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to design-taste-frontend-v1 — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/design-taste-frontend-v1/SKILL.md · 227 lines

How it starts

The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.

High-Agency Frontend Skill

1. ACTIVE BASELINE CONFIGURATION

  • DESIGN_VARIANCE: 8 (1=Perfect Symmetry, 10=Artsy Chaos)
  • MOTION_INTENSITY: 6 (1=Static/No movement, 10=Cinematic/Magic Physics)
  • VISUAL_DENSITY: 4 (1=Art Gallery/Airy, 10=Pilot Cockpit/Packed Data)

AI Instruction: The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.

2. DEFAULT ARCHITECTURE & CONVENTIONS

Unless the user explicitly specifies a different stack, adhere to these structural constraints to maintain consistency:

  • DEPENDENCY VERIFICATION [MANDATORY]: Before importing ANY 3rd party library (e.g. framer-motion, lucide-react, zustand), you MUST check package.json. If the package is missing, you MUST output the installation command (e.g. npm install package-name) before providing the code. Never assume a library exists.
  • Framework & Interactivity: React or Next.js. Default to Server Components (RSC).
    • RSC SAFETY: Global state works ONLY in Client Components. In Next.js, wrap providers in a "use client" component.
    • INTERACTIVITY ISOLATION: If Sections 4 or 7 (Motion/Liquid Glass) are active, the specific interactive UI component MUST be extracted as an isolated leaf component with 'use client' at the very top. Server Components must exclusively render static layouts.
  • State Management: Use local useState/useReducer for isolated UI. Use global state strictly for deep prop-drilling avoidance.
  • Styling Policy: Use Tailwind CSS (v3/v4) for 90% of styling.
    • TAILWIND VERSION LOCK: Check package.json first. Do not use v4 syntax in v3 projects.
    • T4 CONFIG GUARD: For v4, do NOT use tailwindcss plugin in postcss.config.js. Use @tailwindcss/postcss or the Vite plugin.
  • ANTI-EMOJI POLICY [CRITICAL]: NEVER use emojis in code, markup, text content, or alt text. Replace symbols with high-quality icons (Radix, Phosphor) or clean SVG primitives. Emojis are BANNED.
  • Responsiveness & Spacing:
    • Standardize breakpoints (sm, md, lg, xl).
    • Contain page layouts using max-w-[1400px] mx-auto or max-w-7xl.
    • Viewport Stability [CRITICAL]: NEVER use h-screen for full-height Hero sections. ALWAYS use min-h-[100dvh] to prevent catastrophic layout jumping on mobile browsers (iOS Safari).
    • Grid over Flex-Math: NEVER use complex flexbox percentage math (w-[calc(33%-1rem)]). ALWAYS use CSS Grid (grid grid-cols-1 md:grid-cols-3 gap-6) for reliable structures.
  • Icons: You MUST use exactly @phosphor-icons/react or @radix-ui/react-icons as the import paths (check installed version). Standardize strokeWidth globally (e.g., exclusively use 1.5 or 2.0).

Read the full file on GitHub · 227 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 227 lines · 61 tokens per session scan A d03fc304c6e8

Subscribe to this mod's changes

design-taste-frontend-v1 is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 16d ago), licensed MIT. It adds 61 tokens to every session and 5,125 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to design-taste-frontend-v1, differing in 6 lines, and is treated as a copy.

CSS and stylingDesign and UXFrontendagentai-agentsclaudeclaude-skillscodex-skillskills
Related

Other skills, from other repositories

web-design-engineer

Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…

ConardLi/garden-skills · 96 tokens

webflow-mcp:interactions

Create, update, list, and delete Webflow IX3 interactions (GSAP animations) through Webflow MCP. Use when the user wants click/hover/load/scroll/mouse-move animations, interaction timelines, or datainteractionstool / createinteraction payloads. Requires beta MCP + ff-ix3-interaction-apis during dogfood.

webflow/webflow-skills · 79 tokens

webflow-mcp:flowkit-naming

Apply Flowkit CSS naming system in Webflow. Use when creating classes, auditing existing naming, or building new components following Flowkit conventions. Flowkit is Webflow's official CSS framework with utility-first approach. Runs headlessly against a page ID — no Designer connection required, except for the…

webflow/webflow-skills · 81 tokens

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.

tobihagemann/turbo · 48 tokens

ardot-style-guide

A design-system workflow for choosing and applying colors, fonts, spacing, and page layouts in Ardot projects.

balabalabalading/huuuuuuho-skills · 123 tokens

slop-eval

Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…

fabricioctelles/skills · 142 tokens