ui-component
Skill426 starsChanged 39 days agoMITView on GitHub
Use when creating new UI components under apps/web/src/components/
4 other projects use a version of this.
Adopted by
Most recently taken up by
- NicholasFlemmer/styx-apptheir own version, first seen Oct 9, 2026
- tabler/tablertheir own version, first seen Oct 8, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
- Thegreenpiranha/tasquetheir own version, first seen Jul 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- tabler/tabler★ 42ksame name
- NicholasFlemmer/styx-app★ 31same name
- Adhamxon/claude-code-skills★ 2same name
- Thegreenpiranha/tasque★ 0same name
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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- crawler-scraperSkill
- db-schema-changeSkill
- drizzle-erdSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
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 43
IMPORTANT: Only create .client.tsx when interactivity is required (useState, useEffect, event handlers, etc.).
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI Component Creation Skill
Checklist (MUST complete all)
- Create component file
- Create
*.stories.tsxfor Storybook - Use semantic colors for monetary values (see
AGENTS.md) - Verify Storybook:
pnpm --filter @mf-dashboard/web test:storybook
Component Types
1. Pure UI Components (components/charts/ or components/ui/)
Data-agnostic, reusable components. Receive all data via props.
// components/charts/my-chart.tsx
"use client";
interface MyChartProps {
data: Array<{ label: string; value: number }>;
// ... props only, no data fetching
}
export function MyChart({ data }: MyChartProps) {
return (/* pure rendering */);
}2. Data-Fetching Components (components/info/)
| File | Purpose |
foo.tsx | Server Component - fetches data via lib/queries |
foo.client.tsx | Client Component - handles interactivity (ONLY if needed) |
foo.stories.tsx | Storybook - uses mock data |
IMPORTANT: Only create .client.tsx when interactivity is required (useState, useEffect, event handlers, etc.). If the component only displays data, keep it as a Server Component.
Server Component Only (no interactivity)
// components/info/my-info.tsx
import { getMyData } from "../../lib/queries";
export function MyInfo() {
const data = getMyData();
return (
<Card>
<CardHeader>
<CardTitle>My Info</CardTitle>
</CardHeader>
<CardContent>{/* render data */}</CardContent>
</Card>
);
}With Client Component (interactivity required)
// components/info/my-info.tsx
import { getMyData } from "../../lib/queries";
import { MyInfoClient } from "./my-info.client";
export function MyInfo() {
const data = getMyData();
return <MyInfoClient data={data} />;
}// components/info/my-info.client.tsx
"use client";
interface MyInfoClientProps {
data: MyData;
}
export function MyInfoClient({ data }: MyInfoClientProps) {
const [state, setState] = useState(/* ... */);
return (/* interactive UI */);
}File Locations
- Pure charts:
apps/web/src/components/charts/ - UI primitives:
apps/web/src/components/ui/ - Data-fetching:
apps/web/src/components/info/ - Queries:
apps/web/src/lib/queries.ts
Storybook Template
// components/info/my-info.stories.tsx
import type { Meta, StoryObj } from "@storybook/react";
import { MyInfoClient } from "./my-info.client";
const meta = {
component: MyInfoClient,
} satisfies Meta<typeof MyInfoClient>;
export default meta;
type Story = StoryObj<typeof meta>;
export const Default: Story = {
args: {
data: {
// mock data here
},
},
};Semantic Colors (MUST use)
| Purpose | Class |
| Income amount | text-income |
| Expense amount | text-expense |
| Positive balance | text-balance-positive |
| Negative balance | text-balance-negative |
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.

