@@ -13,7 +13,7 @@ Implement a page from a Figma export in `.figma-to-code/output/`.
## What to read
1.`.figma-to-code/output/$ARGUMENTS/content.md` — the source of truth. Sections in order, text content, image references.
1.`.figma-to-code/output/$ARGUMENTS/content.md` — the source of truth. Sections in order, text content, image references, sizes and positions (relative to each section).
2.`.figma-to-code/output/$ARGUMENTS/design-tokens.json` — colors and font sizes used on this page.
3. Read only the `page.png` referenced in the `content.md` to get the general idea. Let the subagents read and manage the screenshot and assets of each section separately.
@@ -24,7 +24,7 @@ Note: If the user explicitly wants a responsive design, try to get and use the e
- Collect important information about the project for the design implementation.
- Determine the correct route file for this page from the existing routes in.
- Implement section by section, top to bottom, following content.md order, one by one.
- For each section spawn an agent from `agents/section-implementer.md` and give it:
- For each section spawn a subagent from `agents/section-implementer.md` and give it:
- Guidelines from the project to help it write a code that matches the project's standards
- The `content.md` and the specific line range for that section.
- The `design-tokens.json`
@@ -39,4 +39,4 @@ Note: If the user explicitly wants a responsive design, try to get and use the e
## Afterwards
- Ask the user to inspect the result. Some times hidden elements in the design get included in the data, and should be removed manually.
- If explicitly told to, continue with `/improve-design-implementation.md`, otherwise, offer to do that
- If explicitly told to, continue with `improve` skill, otherwise, offer to do that
description:For improving the implementation of an extracted Figma page design.
argument-hint:Page name
disable-model-invocation:true
model:haiku
model:sonnet
---
Improve the implementation of a page from a Figma export in `.figma-to-code/output/` to better match the design.
@@ -13,7 +13,7 @@ Improve the implementation of a page from a Figma export in `.figma-to-code/outp
## What to read
1.`.figma-to-code/output/$ARGUMENTS/content.md` — the source of truth. Sections in order, text content, image references.
1.`.figma-to-code/output/$ARGUMENTS/content.md` — the source of truth. Sections in order, text content, image references, sizes and positions (relative to each section).
2.`.figma-to-code/output/$ARGUMENTS/design-tokens.json` — colors and font sizes used on this page.
3. The images referenced in content.md — view each one before coding the section that uses it.
@@ -24,11 +24,11 @@ Note: If the user explicitly wants a responsive design, try to get and use the e
- Collect important information about the project for the design implementation.
- Determine the correct route file for this page from the existing routes in.
- Use Playwright MCP to get the page snapshot.
- Use `browser_resize` to match the design screenshot width.
- Use `browser_resize` to match the design screenshot width. This is important to get accurate screenshots later.
- Use `browser_navigate` to get to the page.
- Note: Sometimes the user need to manually close the browser. In such case, inform them rather than retrying over and over.
- Use `browser_snapshot` with set depth (should be around 3) to get the refs of the sections.
- For each section spawn an agent from `agents/section-improver.md` and give it:
- For each section spawn a subagent from `agents/section-improver.md` and give it:
- Guidelines from the project to help it write a code that matches the project's standards
- The section's ref from the Playwright snapshot
- The `content.md` and the specific line range for that section.