Hi Spec-Kit Team / Community, #1449

I am building an Angular application using Spec-Kit and want to convert Figma designs into Angular UI components.

I understand that Spec-Kit does not directly parse Figma files like a plugin, but I am using the MCP Figma Server to provide visual context (screenshots / design reference) during the Spec-Kit workflow.

My current approach is:

1. Use MCP Server to fetch the Figma screen (single node at a time)
2. Treat the Figma design as the Single Source of Truth
3. Provide the Figma link + node-id in /speckit.specify
4. Generate plan, tasks, and implementation for Angular (Material, standalone components)

I have a few questions:

• Is this the recommended workflow when using Spec-Kit with MCP Server for Figma → Angular?
• Is it best practice to generate one screen/component at a time rather than multiple screens?
• Are there any additional guidelines to improve layout accuracy (spacing, images, Material components) when using MCP-based visual input?
• Any known limitations or tips when relying on MCP screenshots instead of direct Figma parsing?