okhp3-replit-design-pipeline

Orchestrates the Replit UI design loop of extract, sandbox, variant, and graduate phases.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-replit-design-pipeline-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-replit-design-pipeline
Source: https://github.com/OKHP3/telling-forward/tree/main/.agents/skills/okhp3-replit-design-pipeline
Command: npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-replit-design-pipeline-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Redesigning UI components often goes wrong when agents rebuild existing components from memory, produce near-identical variants, or wire mockups into production incorrectly. This Skill provides the complete Replit design iteration loop as a single decision-driven workflow so every redesign follows the correct extract → sandbox → variant → graduate path. ## Core Features & Use Cases - Extract-first decision tree: Determines whether to extract an existing component or build from scratch, enforcing the "never approximate" golden rule. - DESIGN subagent brief anatomy: Defines the five required brief fields (product identity, goal, vibe, target location, variant hypothesis) and what to omit so variants are genuinely distinct. - Variant labelling and graduation gate: Standardizes canvas labels by design hypothesis and gates graduation on variant confirmation, component library differences, and mock-vs-real data, using a GENERAL subagent for production wiring. - Use Case: A user asks to redesign an existing checkout card and show three options. The Skill directs extraction of the current component as a baseline, parallel DESIGN subagents with distinct briefs, hypothesis-labelled variants on canvas, and a gated graduation of the approved variant. ## Quick Start Ask the agent to redesign an existing UI component and show variant options on the canvas, then graduate the one you approve.

Frequently Asked Questions about okhp3-replit-design-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I redesign an existing React component in Replit without losing visual fidelity?▼

Extract the existing component into the mockup sandbox first instead of rebuilding from memory. Create a group folder with _group.css containing the app's :root variables and a Current.tsx baseline, since rebuilding from scratch produces wrong dimensions, colours, spacing, and font sizes.

What should a DESIGN subagent brief include for UI variant generation?▼

A DESIGN subagent brief needs five fields: product/brand identity, goal, vibe, target location, and variant hypothesis. Omit specific CSS values, colours, font names, layout prescriptions, and design style names, and give each subagent a distinct vibe so variants differ meaningfully.

Should I use a DESIGN or GENERAL subagent to graduate a mockup into my app?▼

Use a GENERAL subagent for graduation because it is engineering work involving import graphs, routing, state wiring, and API integration. DESIGN subagents should never handle graduation since they do not wire APIs or understand routing.

What must I check before graduating an approved mockup variant?▼

Answer three gate questions: which exact variant was approved, whether the main app's component library differs from shadcn/ui requiring import translation, and whether the mockup uses mock data that must become real API calls. Graduate exactly what was approved without improving the design.

When should I not use this design pipeline?▼

Skip the pipeline for trivial direct edits like changing a button colour, single implementations with no variants, accessibility audits, or backend debugging. It applies only when iterating on UI through redesign, variants, canvas placement, or mockup graduation.