Frontend Agent
ListedAutomates frontend development tasks like code generation, testing, and deployment based on design specifications.
Install on your platform
frontend-agent. first-fluke/oh-my-agent has no skill named "frontend-agent" any more. It was renamed, moved or deleted upstream.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-30. We don't show a command we know will fail.
What we know about this skill
Publisher
first-fluke
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
What it does
The Frontend Agent is designed to automate frontend development tasks, specifically focusing on building user interfaces and components based on design specifications. It assists with client-side logic, state management, styling (using TailwindCSS v4 + shadcn/ui), form validation, and integrating with backend APIs. The agent prioritizes performance and accessibility throughout the development process.
When to use it
This skill is useful for:
- Building user interfaces and components
- Implementing client-side logic and state management
- Creating responsive designs
- Handling form validation and user interactions
- Integrating frontend code with backend APIs
Key capabilities
- Utilizes shadcn/ui components, extending them via cva variants or composition.
- Enforces a 1:1 mapping of code to Design Tokens.
- Defaults to Server Components for performance optimization.
- Mandates semantic HTML and accessibility best practices (ARIA labels, keyboard navigation).
- Leverages pre-made hooks from ahooks.
- Employs es-toolkit for utility functions; custom logic requires >90% test coverage.
- Uses TanStack Query for server state management.
Example prompts
- "Create a component for displaying user profile information, following the design tokens."
- "Implement form validation using Zod and @tanstack/react-form for this signup page."
- "Generate a loading skeleton component for the product listing feature."
Tips & gotchas
- Component Strategy: Prioritize Server Components unless interactivity or API integration is required.
- Design Tokens: Always refer to
packages/design-tokens(OKLCH) as the source of truth for colors and avoid hardcoding them directly in your code. - Testing: Custom utility logic requires a minimum of 90% unit test coverage.