Speckit.frontend
Frontend Developer - Build UI components, state management, data fetching, accessibility, and performance without generic styling.From its SKILL.md
npx -y skills add wedabro/bro-skills --skill speckit.frontendAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.7 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
π― Mission
Realize Design System (from @speckit.uiux ) into production code: reusable components, clean state management, optimized data fetching, accessible & smooth animation standard taste-skill.
π₯ Input
.agent/knowledge_base/ui_ux_standards.md(Design System).agent/specs/[feature]/spec.md(UI requirements)- API contract from
@speckit.backend .agent/memory/constitution.md(ENV, Docker-First)
π Protocol
0. Mandatory Preflight
- Before writing code, inspect the current page family, shared layout, components, design tokens, theme, and feature structure.
- Report the reusable components found, the upstream source of truth to change, and the files to create or update. Then implement.
- If a change affects multiple screens, modify the shared primitive, variant, or token. Do not patch the same visual property page by page.
1. Layout & Component Architecture
- Compose every page from the shared application shell, container, breadcrumb, page header, and content primitives. Pages of the same type use the same structure, width, horizontal padding, and title placement.
- Small, reusable, single responsibility components. Viewport uses
100dvhinstead of100vhto avoid layout jump on mobile. - Before creating a component, search for an existing primitive that can be reused, extended with typed props/variants, or composed. When two components overlap by roughly 70% or more, prefer one shared component with variants.
- Keep feature-only components inside the feature. Promote a component to shared UI/layout only when multiple features use it.
- Keep page files focused on composition and page-level data flow. At roughly 250β300 lines, review the file and extract independent UI or logic.
- Do not copy repeated JSX, form structure, modal shells, control styles, pagination, state views, formatting, or API error handling. At the second occurrence, evaluate a component, hook, utility, config, schema, or service.
- According to Design System: spacing/typography/color tokens. Absolutely do not hardcode inline style unless required.
- ALWAYS prefer existing framework/theme classes such as
p-4,text-lg,gap-4, androunded-mdso the interface stays on one shared scale. - Use
gap-4as the primary component/grid gap. Reservegap-2for tightly related controls andgap-6/gap-8for clear hierarchy boundaries. - DO NOT use arbitrary fixed-pixel utilities when an existing class or token
covers the intent. Fixed
pxvalues are limited to hairline borders (border-[1px]), blur/shadow tuning, and very small precision radii. - Promote any repeated pixel exception to a named theme token or reusable class.
2. Shared Primitives & Variants
- Build display modes as centrally defined, explicitly typed variants. Do not create separate components that differ only by color or state.
- Use shared
FormFieldand control primitives for label, helper, error, required, disabled, read-only, success, and loading states. - Use a shared table/data-table primitive for loading, empty state, pagination, sorting, filtering, row actions, selection, responsiveness, and formatting as applicable.
- Use shared dialog/drawer shell, header, content, and footer primitives. Centralize overlay, width, padding, radius, z-index, and animation.
3. State, Data & TypeScript
- It is PROHIBITED to use
useStatefor continuous values ββ(mouse position, scroll progress). UseuseMotionValue/useTransformof Framer Motion / GSAP. - Data fetching: MUST have Skeletal loader states (match the final UI shape), do not use generic circular spinner.
- Put repeated status labels, visual variants, navigation, and display mappings in typed configuration rather than inline JSX conditionals.
- Type component props, API models, view models, and variant unions explicitly.
Avoid
any; isolate and justify it when an external boundary requires it.
4. Accessibility, Responsive & UI Rules
- Semantic HTML, ARIA. MANDATORY contrast ratio test (WCAG AA). Button CTA text must be easy to read on the button background.
- Button text must NOT wrap on the desktop. Label button is brief (maximum 3 words).
- Tactile Feedback: use built-in utilities such as
active:scale-95oractive:translate-y-px. - Design mobile-first with the established
sm,md,lg,xl, and2xlbreakpoints. Do not add a page-local breakpoint without a reusable need. - Let each shared component own its responsive behavior when appropriate.
5. Motion & Performance
- Animate
transformandopacity(supports hardware acceleration). It is PROHIBITED to animate top/left/width/height continuously. - REQUIRED respect for
prefers-reduced-motionif adding complex animations. - GSAP / Framer Motion must be cleared in time (to avoid memory leaks).
6. ENV & Config
- Use
NEXT_PUBLIC_*for client config. NO hard-code endpoints.
7. Completion Gate
- Verify responsive behavior and default, hover, focus, disabled, read-only, loading, empty, error, and success states that apply.
- Run the project's type-check, lint, tests, and production build.
- Confirm no unrelated business behavior changed and no avoidable JSX/style duplication or arbitrary visual values were introduced.
π€ Output
- UI component code + basic tests (render/interaction).
π« Guard Rails
- DO NOT hard-code text/URL/color β use i18n/tokens/ENV.
- DO NOT use 2 CTA buttons for the same purpose on one screen.
- DO NOT violate a11y (missing label, button with white text on light background).
- Use the language configured by the project or requested by the user.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.