Automated summary
Turns a design-engine output (e.g. a Stitch screen artifact) into repo-native implementation work, reusing real components and tokens instead of pasting generated markup.
Strengths
- Prioritizes reusing the repo's actual primitives and tokens before creating new visual fragments
- Translates semantics and state model from the artifact rather than porting web markup literally
- Gives concrete mapping guidance for Flutter widgets and theme tokens, shared cards and section headers
- Builds in QA hooks—semantics labels, stable copy, navigable flows—for frontend tests or flutter-mobile-qa
Limitations
- Assumes a design-engine artifact or approved screen brief already exists upstream
- Does not cover producing the design itself or final visual review
- The anti-slop constraints to preserve are referenced but not spelled out in the skill
Use right after a design screen is approved, to convert it into an implementation plan that matches the repo's real stack.
Skip it when no design artifact or brief exists, or when the task is to design the UI rather than implement it.
Security analysis
SafeThis is a purely instructional/documentation skill describing a design-to-implementation handoff workflow. It declares no tools, runs no commands, touches no credentials or network, and contains no destructive or obfuscated content. The only implicit activity is code authoring guidance, which presents no execution risk.
No concerns found
How this analysis is madeExamples
Stitch just returned the checkout screen artifact. Turn it into an implementation plan using our existing Flutter widgets and theme tokens instead of pasting the generated markup.The profile screen brief is approved. Map it to our React components, list what to reuse vs create, and note the QA hooks needed for frontend tests.Here's the design-engine output for the settings page. Translate its hierarchy into our Flutter widgets, map colors and typography to theme extensions, and tell me what's missing for flutter-mobile-qa.name: frontend-design-implementation-handoff description: Translate design-engine output into repo-native implementation work, preferring real components, Flutter widgets, and existing tokens over pasted generated markup.
Frontend Design Implementation Handoff
Purpose
Convert the design-engine result into implementation work that matches the repo's real stack and components instead of copying raw generated artifacts.
When to Use
- After Stitch returns a screen artifact
- After a design screen brief is approved for implementation
- When moving from design state into Flutter, React, or another real UI stack
Instructions
- Prefer existing components and tokens first — Reuse the repo's real primitives before creating new visual fragments.
- Translate semantics, not markup — A generated artifact is a seed. Rebuild it in the target stack using the same hierarchy and state model.
- For Flutter, map into widgets and theme tokens — Use theme extensions, shared cards, section headers, and navigation widgets instead of porting web structure literally.
- Preserve the brief's anti-slop constraints — Distinctive typography, component rhythm, and motion rules should survive the handoff.
- Leave QA hooks behind — Ensure semantics labels, stable copy, and navigable flows are good enough for
flutter-mobile-qaor frontend tests.
Output Format
Deliver:
- Implementation plan
- Components/widgets to create or reuse
- Token/theme mapping
- QA-readiness notes
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/frontend-design-implementation-handoff-mrzxuqne/download' --output '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md.part' && mv '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md.part' '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md' && test -s '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/frontend-design-implementation-handoff' && cp -R '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne' '.claude/skills/frontend-design-implementation-handoff'Cursor
test -f '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md' && test -s '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/frontend-design-implementation-handoff' && cp -R '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne' '.cursor/skills/frontend-design-implementation-handoff'Codex
test -f '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md' && test -s '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/frontend-design-implementation-handoff' && cp -R '.skill-downloads/frontend-design-implementation-handoff-mrzxuqne' '.agents/skills/frontend-design-implementation-handoff'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/frontend-design-implementation-handoff-mrzxuqne'openskills read 'frontend-design-implementation-handoff-mrzxuqne'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/frontend-design-implementation-handoff-mrzxuqne/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.