r2-dev-page

Generating frontend pages from design specifications is done by placing a requirement.page.md file in your module and running the generator. It scaffolds UI components, state management, API clients, types, styles, and tests while preserving existing API contracts and project structure.

Yes, scaffolding type-safe API clients and UI components from a single page spec is supported. The skill produces type definitions and frontend validation scaffolding aligned with API schemas, ensuring end-to-end type-safety across the generated components and data models.

Automating rapid prototyping for modern web apps is handled by translating page requirements into working frontend modules. The skill generates framework-agnostic UI components plus API integrations and data models, enabling designers to turn specs into production-ready code systematically.

Frontend code generation works across modern web frameworks by producing framework-agnostic UI components and state management hooks or composables. It systematically scaffolds frontend code while preserving your existing API contracts and project structure during the design-to-code workflow.

Yes, pyyaml is required as a dependency to scaffold frontend code from page requirements. You need it installed in your environment before running the generator to ensure the specification parsing and code generation processes execute correctly.

Frontend scaffolding preserves existing API contracts during code generation to ensure the generated API client integrations and type definitions remain aligned with your current backend schemas. This prevents breaking changes and maintains end-to-end type-safety across the project structure.