frontend-ui-functional
Skill130 starsChanged 7 months agoMITView on GitHub
Use when building or refactoring functional React/Vite/Tailwind UI pages, templates, or component libraries that need consistent structure, tokenized styling, accessibility checks, and performance-ready patterns.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- victorGPT/vibeusageword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- victorGPT/vibeusage★ 130100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- openspec/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- find-skillsSkill
- insforge-cliSkill
- insforgeSkill
- vibeusage-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If the repo contains docs/skills/frontend-ui-functional/project-overlay.md, read and apply it before starting.
- Distinctive: line 37
If time is tight, do a thin pass of each step rather than skipping a11y/perf.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend UI Functional
Overview
Provide a lightweight, repeatable workflow for functional React/Vite/Tailwind UI using structure, tokens, accessibility, and performance-ready patterns plus reusable snippets.
Project Overlay (Required)
If the repo contains docs/skills/frontend-ui-functional/project-overlay.md, read and apply it before starting. Project-specific rules override this skill.
When to Use
- Building new UI pages, templates, or component libraries in React/Vite/Tailwind.
- Standardizing layout, token usage, a11y/accessibility, and performance practices across UI.
- Shipping functional UI quickly without skipping baseline a11y/perf checks.
When Not to Use
- Pure copywriting/content strategy tasks.
- Non-React or non-Tailwind stacks.
- Deep visual branding exploration (use the
frontend-designskill).
Workflow (Minimum Pass)
- Project overlay check →
docs/skills/frontend-ui-functional/project-overlay.md(if present) - Structure first →
references/atomic-design.md - Apply styling tokens →
references/styling-tokens.md - A11y pass →
references/a11y-checklist.md - Performance + state pass →
references/perf-and-state.md - Tooling + QA →
references/tooling.md
If time is tight, do a thin pass of each step rather than skipping a11y/perf.
Quick Reference
| Need | Use |
| Project overlay | docs/skills/frontend-ui-functional/project-overlay.md (if present) |
| Structure system | references/atomic-design.md |
| Tokenized styling | references/styling-tokens.md |
| Accessibility/a11y | references/a11y-checklist.md |
| Performance + state | references/perf-and-state.md |
| QA tooling | references/tooling.md |
| Reusable UI snippets | assets/snippets/* |
Reusable Snippets
- Button:
assets/snippets/button.tsx - Card:
assets/snippets/card.tsx - Form:
assets/snippets/form.tsx - Layout:
assets/snippets/layout.tsx - Lazy Route Boundary:
assets/snippets/lazy-route.tsx - Zustand Store:
assets/snippets/zustand-store.ts
Example (Single)
Note: replace literal strings with your project's copy/content source when applicable.
import { Button } from "./button";
import { Card } from "./card";
import { PageLayout } from "./layout";
export function DashboardStub() {
return (
<PageLayout title="Overview" actions={<Button label="Create" />}>
<div className="grid gap-4 md:grid-cols-2">
<Card title="Revenue" description="Last 30 days">
<div className="text-2xl font-semibold text-primary">$128,400</div>
</Card>
<Card title="Active Users" description="Daily active">
<div className="text-2xl font-semibold text-primary">4,812</div>
</Card>
</div>
</PageLayout>
);
}Common Mistakes
- Skipping a11y/perf due to time pressure; do the minimum pass instead.
- Hardcoding colors instead of using tokens from
references/styling-tokens.md. - Mixing layout decisions with visual polish before the structure is stable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

