Clarification on Using Figma Designs with Spec-Kit for Angular UI Implementation

[nitesh-snap]

1. In the Spec-Kit workflow, which command is the correct place to provide the Figma design link?
   Should it be included in /speckit.specify or elsewhere?

2. Does Spec-Kit support directly reading or interpreting Figma designs,
   or is the Figma link used only as a reference during the /speckit.specify stage?

3. What is the recommended end-to-end workflow for converting Figma UI designs
   into Angular components using Spec-Kit?
   (Including best practices for component structure and implementation.)

[mnriem]

Moving this to discussions as it is not a bug report nor feature request

[wyy5763]

+1，Same here. Could someone explain the correct expression?

[mnriem]

Out of the box Spec Kit does not know about Figma, but if your coding agent and/or model know about Figma it will use it during specify if so directed.

[shashankshekhar-1911]

Plugging into Figma MCP should be pretty straightforward right? Also, in some cases, the design provided by v0 or stitch might be enough to not go into figma for any further fine-tuning. How do you communicate the design in that case?

[mnriem]

For v0/Stitch output — since those tools produce actual code or markup rather than just a visual reference, you'd include the generated output (or a link to it) as context when running specify. The spec becomes the integration point: describe the design intent, reference the generated component as a starting point, and the agent picks it up during implement.

In both cases the spec is where you communicate design context — Spec Kit is agnostic to the source.

[nitesh-snap]

I have a Figma-to-Code skill (figma-ui-generator) that generates Angular UI from Figma designs.

My proposed Spec Kit workflow is:

/speckit.constitution
The binding implementation authority for all Figma-to-code work is: figma-ui-generator.
Every step in that skill is mandatory.
No business logic — UI structure and styles only.

/speckit.specify
Generate a UI component from a Figma design.

/speckit.plan
Angular 17 + Angular Material 17.

/speckit.tasks

/speckit.implement

Is this the correct approach for integrating a Figma-to-Code skill with Spec Kit?

Also, during the /speckit.implement phase, the skill requires additional inputs such as:

Figma URL
Component Name
Other component-specific parameters

What is the recommended way to handle these inputs? Should they be captured during the /speckit.specify phase and carried forward into implementation, or is it expected that /speckit.implement prompts the user for them when execution begins?