coding-fe

Convert approved Stitch outputs into Next.js App Router UI code.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/lac-minh-studio/lacminh-web --skill coding-fe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-fe
Source: https://github.com/lac-minh-studio/lacminh-web/tree/main/.github/skills/coding-fe
Command: npx skills add https://github.com/lac-minh-studio/lacminh-web --skill coding-fe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved Stitch design outputs into new Next.js App Router UI code for route slices, pages, or components that do not yet exist in the current src/.

Core Features & Use Cases

  • Converts Stitch HTML/PNG artifacts into HeroUI-based frontend slices aligned with the project's tokens.
  • Generates thin, server-first route files with mock data and interfaces to accelerate UI delivery.
  • Useful for creating new routes, sections, or components from approved Stitch rounds when sources exist in .stitch/ metadata.json.

Quick Start

Select the approved Stitch artifacts from .stitch/metadata.json and run the coding-fe skill to generate a new Next.js route slice.

Frequently Asked Questions about coding-fe

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

FAQPage Schema
How do I convert Stitch designs into Next.js App Router UI code?

To convert Stitch designs into Next.js UI code, select approved Stitch artifacts from .stitch/metadata.json and run the generation process to create missing route slices, pages, or components in your src directory.

Can I generate HeroUI components from Stitch artifacts for existing Next.js routes?

No, this process generates HeroUI components exclusively for route slices, pages, or components that do not yet exist in your src directory, ensuring new UI creation from approved Stitch outputs rather than overwriting existing files.

What do I need to generate Next.js frontend code from approved Stitch outputs?

You need approved Stitch HTML or PNG artifacts stored in .stitch/metadata.json, alongside your project's HeroUI tokens, to generate aligned Next.js App Router frontend slices.

Does Stitch to Next.js code generation produce server-first route files with mock data?

Yes, the conversion produces thin, server-first Next.js route files populated with necessary interfaces and mock data to accelerate UI delivery while maintaining a token-safe frontend generation approach.

What are the limitations of generating Next.js UI from Stitch design sources?

Limitations include requiring pre-approved Stitch artifacts in .stitch/metadata.json and strictly targeting missing src files, meaning it cannot update or replace existing Next.js route slices or components.