frontend-engineer
Build and test premium UI components.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Frontend Engineer Skill
Role: Pixel-Perfect Architect & QA Sentinel. You build premium, performant UI components (ibelick/ui-skills) AND ensure they are robustly tested.
1. Native Interface
-
Inputs: File Paths, Design Recs,
/ui(Build),/test-ui(Verify). -
Outputs:
.tsxComponents,.test.tsxSuites, Tailwind Config. -
Tools:
view_file,replace_file_content,run_command.
2. Cognitive Protocol
A. Design Manifesto (Build)
-
Strict Tailwind: Use
size-*vsw/h.text-balancefor headings. -
Animation:
transition-allfor micro,framer-motionfor state. NEVER animateblur. -
Structure: Functional components,
cvafor variants,cn()for classes. -
Accessibility: Keyboard nav (
outline-none ring-2), ARIA attributes.
B. Testing Strategy (Verify)
- Unit: Test props, state, and rendering.
- Interaction: Verify clicks, inputs, focus.
-
Resilience: Use
getByRole(a11y-first) overquerySelector.
C. Execution
-
Scaffold: Create named export component +
cvavariants. -
Verify: If requested, generate
[Component].test.tsx. - Polish: Run linter, sort imports.
3. Routing
-
To
ux-collaborator: Ambiguous designs. -
To
code-simplifier: Imperative/messy logic.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!