prd-to-app

Solid

Build a complete, production-ready full-stack web application from PRD documents, prototype images, and resource files. Handles the entire pipeline: system design, database schema, seed data, backend API, frontend UI, visual verification against prototypes, and deployment script generation. Use this skill whenever the user: - Provides a PRD (product requirement document) and wants a working app built - Says "build from PRD", "implement this product", "develop this app from requirements" - Has prototype images + requirements and wants full-stack implementation - Wants to turn product specifications into a running web application Triggers: 'prd to app', 'из prd в приложение', 'разработай по prd', 'сделай приложение по макетам', 'build from prd', 'implement from prd'.

AI & Automation 5 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
26
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# PRD-to-App: Full-Stack Application Builder > **Language**: Respond in the same language the user uses. Code comments should match. Build a complete, deployed web application from PRD + prototypes + resources. The result must be fully reproducible via a single `bash start.sh`. **Origin**: Adapted from `zai-org/GLM-skills/glmv-prd-to-app` (Apache 2.0). ZHIPU API dependencies removed; replaced with Playwright + look_at for prototype analysis. --- ## Phase 0: Material Discovery & Analysis Before anything else, understand what you're working with. ### 0a. Locate all inputs ``` ./prd.md ← Product requirement document ./prototypes/*.jpg|*.png ← UI prototype images (the visual truth) ./resources/**/* ← Images, videos, icons, and other assets ``` If the materials are in a different location, adapt accordingly. Read the PRD fully. ### 0b. Deep prototype analysis For **every** prototype image: 1. **Read the image** using the `look_at` tool (or `Read` tool for images) — examine it directly. Extract: page identity, layout structure, component inventory, content inventory, color extraction (hex values), typography, interactive states, data patterns. 2. For each image, document: - **Page identity**: which page/view this represents - **Layout structure**: header, sidebar, main content, footer, modals - **Component inventory**: every button, form, card, table, list, nav element - **Content inventory**: all visible text, numbers...

Details

Author
bestdeejay-design
Repository
bestdeejay-design/agent-skills
Created
1 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

app-prd

Use when the user wants an app idea turned into a Product Requirements Document (PRD) committed to a repo — "create a PRD", "/app-prd", "turn this idea into a PRD", or a raw idea dump ending with "save it to this repo". Produces a complete, section-numbered PRD.md landed via worktree + PR, bootstrapping an empty repo if needed. Stage 1 of the new-app-pipeline.

49 Updated yesterday
richkuo
Web & Frontend Solid

design-prd

Generate Product Requirements Documents through structured conversation for any project. Auto-detects tech stack, existing features, and data model from the codebase. Uses Firecrawl to research competitor products and UX patterns, Context7 to check framework capabilities for feasibility, and Supabase MCP to verify data model feasibility. Produces actionable PRDs with technical feasibility sections informed by real codebase analysis. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.

9 Updated yesterday
kensaurus
Web & Frontend Listed

prd-creator

Turn an app idea into a production-grade PRD, then shard it into per-module briefs that feed module-planner. Use this whenever the user wants to plan a whole app or product — "I want to build a blog / e-commerce app / SaaS", "create a PRD", "help me plan this app", "scope my product idea", "divide the PRD into modules", "shard the PRD" — or describes a product vision spanning multiple features, even if they never say "PRD". It takes the user's points, suggests improvements and standard production features they missed (auth, payments, admin, SEO — the user keeps or rejects each), writes _docs/prd/PRD.md, and on approval shards it into _docs/features/<module>/<module>-module.md briefs tagged backend/frontend/fullstack. Also use it to MODIFY an existing PRD (change scope, add features, re-shard). It does NOT do technical feature planning (that is module-planner), does NOT write code, and does NOT scaffold projects — product scope only, upstream of the whole toolkit.

0 Updated 1 months ago
vipincode