Create responsive frontend features
Build semantic interfaces that adapt across viewports, preserve content hierarchy, handle interaction states, and fit the existing component system.
Codex Skills for Web Development give Codex a disciplined way to build responsive interfaces, connect backend services, test important behavior, improve web performance, and prepare changes for deployment. Download the skills and adapt them to your stack, repository, and release process.
task: ship a responsive activity page
inspect:
- existing routes
- data contract
- test commands
verify: build + accessibilityProduction web work crosses markup, styling, state, data, authentication, error handling, responsiveness, accessibility, performance, tests, and deployment configuration. A local code snippet can ignore the connections that make the feature reliable.
These skills teach Codex to inspect the application before editing, follow the project’s conventions, implement the complete behavior, and run checks that match the actual stack.
Build semantic interfaces that adapt across viewports, preserve content hierarchy, handle interaction states, and fit the existing component system.
Work with API routes, validation, authentication boundaries, databases, caching, errors, and loading behavior without losing the contract between layers.
Add focused unit, integration, and end-to-end checks for the paths most likely to break, including forms, navigation, permissions, and data updates.
Run builds, inspect configuration, check environment needs, review performance risks, and document deployment or migration steps before handoff.
Codex starts by locating the route, data flow, shared components, project commands, and existing tests. It then plans the smallest complete change and verifies the result.
Identify the framework, package manager, routing, styling, state, data layer, environment configuration, and project-specific instructions.
Map the user action through the interface, validation, network request, business logic, persistence, response, and visible feedback.
Reuse established components and utilities, keep types and contracts aligned, and cover empty, loading, error, and success states.
Check responsive behavior, keyboard access, tests, production compilation, performance-sensitive code, and deployment requirements.
The workflow is stack-aware rather than framework-loyal. Add the commands and standards that define a correct change in your project.
Work with component frameworks, routing, state, forms, responsive CSS, design systems, accessibility, and browser behavior.
Build endpoints, validation, authentication, business logic, persistence, error contracts, logs, and integration tests.
Handle CMS data, structured content, product flows, search, metadata, forms, checkout boundaries, and caching.
Create dependable dashboards, tables, filters, permissions, bulk actions, imports, exports, and operational workflows.
The workflow supports new builds and careful changes inside established applications.
These skills are for people who want Codex to understand the web application around the requested code.
Build and refine responsive, accessible interfaces while following the project’s component and styling conventions.
Coordinate interface, API, data, authentication, testing, and deployment work within one traceable workflow.
Move between client stacks while preserving each repository’s commands, conventions, and definition of done.
Give Codex a shared implementation process for features, fixes, reviews, tests, and release preparation.
The skills make implementation more systematic, but architecture, security, product decisions, and production access still need qualified human ownership.
Install the skills for one web application or make them available across the different stacks you work with.
Keep SKILL.md together with included checklists, scripts, stack references, and verification instructions.
Use a repository skill when commands and conventions belong to one application. Use the user location for a general web workflow.
Add install, development, test, lint, build, migration, and deployment checks, plus the package manager and environment rules.
Codex detects installed skills automatically. Restart Codex if the new skill does not appear.
State the route, user action, data behavior, responsive needs, permission rules, and checks that define completion.
Answers about frameworks, existing applications, browser testing, backend work, and deployment.
They are designed to adapt to the repository. Add framework-specific commands and conventions for React, Next.js, Vue, Svelte, server frameworks, or a custom stack.
Yes. The workflow starts by inspecting the codebase and following established patterns, which is especially useful for maintenance and feature work.
Yes. They can guide work across APIs, validation, authentication, business logic, databases, errors, and integration tests when those layers are in scope.
The workflow can require browser checks when the environment provides a supported browser tool. It also includes build, automated test, and accessibility verification.
They can prepare and verify deployment work when the necessary tools and authorization are available. Production changes should still follow your release and approval process.
Repository-aware changes. Responsive behavior. Stronger verification. Fewer unfinished edges.