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.
npx skills add oyi77/1ai-skills --skill frontend-ui-designgit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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.
[](https://agentmods.dev/skills/oyi77/1ai-skills/frontend-ui-design)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/frontend-ui-design"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/frontend-ui-design/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.
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/frontend-ui-design"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/frontend-ui-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 134 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00051 | $0.01991 |
| Opus 5 | $0.00026 | $0.00996 |
| Sonnet 5 | $0.00010 | $0.00398 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
frontend-ui-design 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Ui Design
When to Use
Trigger phrases:
-
"frontend ui design"
-
"Design and build production-grade UI components using React, Vue, or vanilla HTM"
-
When building UI components or pages from scratch
-
When creating a design system or component library
-
When implementing responsive layouts
-
When improving accessibility of existing UI
When NOT to Use
- For backend logic (use backend skills)
- For database design (use data skills)
- For mobile-native apps (use mobile development skills)
Overview
Production-grade frontend UI design bridges visual design and engineering, transforming wireframes into accessible, responsive, and performant interfaces. This skill covers the full lifecycle — from component architecture and design tokens through CSS implementation, accessibility auditing, and design system distribution.
Modern frontend development spans two dominant ecosystems: React (with its component composition model and hook-based state management) and Vue (with its progressive framework and reactive system), alongside vanilla HTML/CSS for lightweight projects. Each requires mastery of component hierarchy, state management patterns, responsive layout strategies, and cross-browser compatibility testing.
Key capabilities include implementing design tokens via CSS custom properties or Tailwind configuration, building accessible components that meet WCAG 2.1 AA standards, creating responsive layouts using CSS Grid and Flexbox, and packaging reusable component libraries for multi-project reuse. CSS architecture choices — Tailwind utility classes, CSS Modules for scoped styles, or CSS-in-JS libraries — each trade locality against bundle size and runtime overhead.
The goal is consistent, keyboard-navigable, performant UIs that work reliably across devices from 320px mobile screens to 4K desktop displays, while remaining maintainable as the codebase grows.
Workflow
- Define requirements — Collect user stories, wireframes, brand guidelines, and target breakpoints. Document component hierarchy with a tree diagram before writing code.
- Select architecture — Choose atomic design for component decomposition, state management approach (React Context, Zustand, Pinia for Vue), and CSS strategy (Tailwind, CSS Modules, styled-components).
- Build design tokens — Define color palette, typography scale, spacing units, and shadows as CSS custom properties or Tailwind config. Verify contrast ratios meet WCAG AA.
- Implement component hierarchy — Build atoms (Button, Input) then molecules (FormField, Card) then organisms (DataTable, Navigation). Prefer composition over inheritance.
- Apply responsive styling — Use CSS Grid for page-level layouts and Flexbox for component-level alignment. Implement mobile-first breakpoints with consistent naming (sm, md, lg, xl).
- Integrate accessibility — Add semantic HTML, ARIA attributes, keyboard event handlers, and focus management. Test with screen readers and colour contrast analysers.
- Test and iterate — Run visual regression tests (Storybook, Chromatic), cross-browser checks, and performance audits (Lighthouse). Collect feedback and refine.
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.
- 9d ago First seen · 187 lines · 51 tokens per session scan A 0b1799056ac1
frontend-ui-design is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,991 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
screenshot-to-code
A tool that turns a UI screenshot or design mockup into component code for Vue, React, or plain HTML.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
unlayer-integration
Integrates Unlayer's email, page, popup, and document builders into web applications through React, Vue, Angular, or plain JavaScript. Use for builder component setup, props, editor access patterns, and multiple instances. For the standalone Image Editor or @unlayer/react-image-editor, use unlayer-image-editor.
frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering…
popular-web-designs
54 production-quality design systems extracted from real websites. Load a template to generate HTML/CSS that matches the visual identity of sites like Stripe, Linear, Vercel, Notion, Airbnb, and more. Each template includes colors, typography, components, layout rules, and ready-to-use CSS values.