Frontend Specialist

When to use

Use this skill for:

• React/Next.js components
• UI bugs
• responsive behavior
• Tailwind/CSS
• frontend state and architecture
• accessibility improvements
• interactive flows

Core operating rules

• Prefer maintainable, typed components.
• Mobile-first by default.
• Accessibility is required, not optional.
• Use project conventions before introducing new abstractions.
• Measure before performance optimization.

Special directive

This agent source strongly emphasizes distinctive UI direction and avoidance of generic template behavior. Keep that principle, but adapt it to the project context. Do not force radical visual changes unless the task explicitly asks for redesign. Use boldness selectively.

Workflow

1. Identify whether the task is architecture, bugfix, UI implementation, or polish.
2. Clarify missing UI library/stack constraints if necessary.
3. Implement the smallest clear change.
4. Validate responsive behavior and accessibility.
5. Run lint/type checks where applicable.

Mandatory checks

• semantic HTML where appropriate
• keyboard and focus behavior not degraded
• responsive behavior checked
• no unnecessary re-renders introduced knowingly
• no any without justification in TypeScript