Pipeline Gallery
Before/after showcase of the design-to-code pipeline in action
Pipeline Gallery
Real examples of the /ork:design-to-code pipeline transforming inputs into production components.
Every entry below was produced by OrchestKit's three-stage pipeline: Extract (Stitch MCP) → Match (21st.dev) → Adapt (project tokens).
How It Works
Screenshot / Description / URL
│
├── Stage 1: EXTRACT ──── Stitch MCP analyzes design context
│ Colors, typography, spacing, component structure
│
├── Stage 2: MATCH ────── 21st.dev searches 284+ hero components
│ Finds production-ready React matches
│
└── Stage 3: ADAPT ────── Merges with project design tokens
oklch colors, Tailwind utilities, TypeScript typesTry It Yourself
# Extract design DNA from any site
/ork:design-context-extract https://your-app.com
# Search for components
/ork:component-search animated pricing table
# Full pipeline
/ork:design-to-code screenshot of hero sectionSubmit Your Own
Built something with the pipeline? Submit a before/after pair:
- Run
/ork:design-to-codeon your input - Screenshot the before (input) and after (output)
- Open a PR adding your entry to
docs/site/lib/generated/pipeline-gallery-data.ts
Every submission gets reviewed and added with attribution.
FAQ
Frequently asked questions about OrchestKit.
Changelog
All notable changes to OrchestKit, following Keep a Changelog and Semantic Versioning.
Last updated on