production-frontend-orchestrator

Generating a frontend prototype from app documentation requires translating scattered user stories and schemas into a single actionable spec. This skill automates that end-to-end production process by discovering repository context and orchestrating a design-direction-based subagent to produce convergent UI.

Ensuring a frontend matches real data models requires comprehensive repository discovery before code generation. This skill analyzes actual app requirements, data schemas, and user interactions to produce a production-ready spec that drives a deterministic frontend implementation.

You can orchestrate a frontend production subagent by selecting a specific design direction during the generation flow. This skill dispatches and manages the subagent based on your chosen design direction, with built-in support for iteration and transfer intent.

Consolidating scattered repository context into a production-ready frontend spec involves automating the discovery of data models, UI paths, and user stories. This skill structurally processes your app docs to create a convergent specification suitable for deterministic prototyping.

This frontend prototyping approach works without predefined UI component libraries by deriving its structure directly from actual app requirements and data models. It relies on your repository's existing documentation and schemas to generate a convergent design direction.

You should avoid automating frontend spec generation when your app documentation is incomplete or lacks defined user stories and data schemas. This skill requires comprehensive repository discovery and actual app requirements to produce a deterministic, production-ready frontend prototype.