Design & UI
dev-frontend-ui-implementation
Use to implement/review frontend UI, routing, state, API integration, responsive layout, accessibility, and browser behavior.
BlueSkyXN · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add BlueSkyXN/Codex-is-all-you-need --skill dev-frontend-ui-implementationAbout this skill
name: dev-frontend-ui-implementation description: Use to implement/review frontend UI, routing, state, API integration, responsive layout, accessibility, and browser behavior. metadata: version: "0.3" updated: "2026-06-12"
Frontend UI implementation workflow
Use this workflow when building or changing a user-facing frontend experience.
Steps
-
Read the existing UI system.
- Framework
- Routing
- Component patterns
- Styling system
- Icons
- State management
- Tests
- Existing visual language
-
Define the user workflow.
- Main task
- Empty/loading/error states
- Permissions and disabled states
- Mobile and desktop behavior
- API assumptions
-
Implement within the system.
- Reuse local components and tokens.
- Keep text inside containers at all target widths.
- Use familiar controls and icons where possible.
- Preserve keyboard navigation and semantic markup.
-
Validate.
- Typecheck/lint/build
- Unit or component tests
- Browser smoke test for meaningful UI changes
- Screenshot checks across desktop and mobile when layout risk is nontrivial
-
Review integration.
- API data shape
- Error handling
- Performance and bundle impact
- Accessibility and focus behavior
Output
Return:
- User-visible change
- Component/state/API impact
- Files changed
- Validation run
- UI risks or follow-ups
Do not
- Do not create a landing page when the task calls for an app/tool experience.
- Do not introduce a new visual style if the repo already has one.
- Do not skip real browser validation for substantial UI changes.