[Extension]: Update figma-starter extension

[vibhus]

Extension ID

figma-starter

Extension Name

Figma Starter

Version

1.1.0

Description

Turns a Figma section's screens into Figma-derived specs — per-screen spec.md files, app-level user-stories.md, and a build-order.md — and turns an OpenAPI/Swagger document into an entity model plus per-page UI ↔ API bindings, then hands off to core /speckit.specify.

Author

WaveMaker

Repository URL

https://github.com/OmneWave/spec-kit-figma-starter/

Download URL

https://github.com/OmneWave/spec-kit-figma-starter/archive/refs/tags/v1.1.0.zip

License

MIT

Homepage (optional)

https://github.com/OmneWave/spec-kit-figma-starter

Documentation URL (optional)

https://github.com/OmneWave/spec-kit-figma-starter

Changelog URL (optional)

https://github.com/OmneWave/spec-kit-figma-starter/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

- python (>=3.8) - required

Number of Commands

2

Number of Hooks (optional)

1

Tags

figma, design, design-to-spec, ui, frontend, api, api-binding, ui + api, data-binding, api-integration

Key Features

Figma to spec (figma-starter.import)

• Figma section → per-screen specs — pulls the actual rendered frames from a Figma section and generates one spec.md per screen, plus app-level user-stories.md and build-order.md.
• Prototype-flow tracing — traces Figma prototype navigation (taps/links) into a flow map (pages, dialogs, journeys) rather than relying solely on design tokens/context.
• Design tokens + typography fetched with the help of Figma MCP

Swagger to spec (figma-starter.import-api)

• Figma Specs + Swagger (OpenAPI) spec document → Per screen API binding specs
• Entity extraction from the swagger spec
• Clear BFF layer extraction based to combine multiple endpoints into a single experience API (flag based)

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on:

• macOS 26.3 and 26.5.2 with Spec Kit v0.1.0
• Windows 11 Pro

Test scenarios:

• Installed extension via specify extension add figma-starter --from https://github.com/omnewave/spec-kit-figma-starter/archive/refs/tags/v1.1.0.zip
• Configured settings, added .env in project root with FIGMA_TOKEN
• Ran /speckit.figma-starter.import, provided the figma section url
• Verified generated specs inside the figma-starter directory of project root
• Ran /speckit.figma-starter.import-api, provided the swagger document and the module to generate api binding specs
• handed over to /speckit.specify command for app development

Example Usage

# Install extension
specify extension add figma-starter --from https://github.com/onewave/spec-kit-figma-starter/archive/refs/tags/v1.1.0.zip

# Run the extension command to generate UI specs
/speckit.figma-starter.import <figma-section-url> [-o <module-name>]

# Run the extension command to generate UI specs
/speckit.figma-starter.import-api <swagger-url> -m <module-name> [--out <output-directory-location>]

Proposed Catalog Entry

{
  "figma-starter": {
    "name": "Figma Starter",
    "id": "figma-starter",
    "description": "Turns a Figma section's screens into per-screen specs, and turns an OpenAPI/Swagger document into an entity model plus per-page UI ↔ API bindings, then hands off to /speckit.specify.",
    "author": "Wavemaker",
    "version": "1.1.0",
    "download_url": "https://github.com/omnewave/spec-kit-figma-starter/archive/refs/tags/v1.1.0.zip",
    "repository": "https://github.com/omnewave/spec-kit-figma-starter",
    "homepage": "https://github.com/omnewave/spec-kit-figma-starter",
    "documentation": "https://github.com/omnewave/spec-kit-figma-starter#readme",
    "changelog": "https://github.com/omnewave/spec-kit-figma-starter/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.1.0",
      "tools": [
        { "name": "python3", "version": ">=3.8", "required": true }
      ]
    },
    "provides": {
      "commands": 2,
      "hooks": 1
    },
    "tags": ["figma", "design", "design-to-spec", "ui", "frontend", "api", "api-binding", "ui + api", "data-binding", "api-integration"],
    "verified": false,
    "downloads": 0,
    "stars": 7,
    "created_at": "2026-07-13T12:00:15Z",
    "updated_at": "2026-07-15T12:44:38Z"
  }
}

Additional Context

• Extension is lightweight and simple to use and sits smoothly between the existing speckit commands, i.e. /speckit.constitution and /speckit.specify
• Can easily be used for both Greefield and Brownfield projects
• Does not overload the developer with plenty of new commands and works in the existing speckit workflow.
• Negligible learning curve. Performs differently from existing figma extensions.

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Validation failed for this submission.

• Extension ID format: passed (figma-starter)
• Version format: passed (1.1.0)
• Repository: passed; the public repository exists and contains extension.yml, README.md, and LICENSE
• Release: passed; GitHub release v1.1.0 exists
• Submission checklists: passed; all required checkboxes are checked
• Download URL format: failed. The submitted URL uses https://codeload.github.com/.../zip/refs/tags/v1.1.0, but submissions must use either https://github.com/<owner>/<repo>/archive/refs/tags/v1.1.0.zip or a matching GitHub release asset URL.

Please update the submission with the canonical archive URL, for example https://github.com/OmneWave/spec-kit-figma-starter/archive/refs/tags/v1.1.0.zip, then resubmit for validation. No catalog changes were made.

Generated by 🧩 Add Community Extension from Issue Submission for issue #4463 · 32.2 AIC · ⌖ 10.3 AIC · ⊞ 29.2K · ◷

[vibhus]

@KSchlobohm Updated the download URL in original request, thanks. Is a new issue request required or existing will be enough?