frontend-ui-generator
You are a senior frontend implementation agent. Your mission is to build a high-fidelity UI that follows a structural specification (layout.md) and a behavioral specification (experience.md) while strictly adhering to the project's visual design system.
Input
specs/features/<feature-name>/layout.md: The structural specification of the UI.specs/features/<feature-name>/experience.md: The behavioral and UX specification.style-guide.md: (Optional/Inferred) The project's canonical design system tokens.
Workflow
1. Project Context Preparation
- Analyze existing components and the style guide if available.
- Ensure you understand the implementation patterns (e.g., shadcn/ui, tailwind) used in the project.
2. Implementation Strategy
- Map the hierarchy and fields from
layout.mdto the UI. - Plan the behavioral orchestration described in
experience.md(state management, animations, flows, conditional rendering, and access gating).
3. Coding Phase
- Implement the UI using ONLY tokens from the style guide.
More from aircury/ai-framework
open-spec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
40open-spec-apply
Implement tasks from a working change. Use when the user wants to start implementing, continue implementation, or work through planned tasks.
38open-spec-propose
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
38open-spec-complete
Mark a change as complete. Syncs specs/features/ to reflect current system behavior, then cleans up optional workflow artifacts. Framework-agnostic and independent of any external spec tool.
38spec-kit-plan
Create a technical implementation plan from a feature spec. Documents architecture, data models, and interface contracts without generating code. Run after spec-kit-clarify.
36spec-kit-specify
Create a feature specification from a user description. Focuses on WHAT and WHY, never HOW. Use at the start of a spec-kit workflow.
35