Skip to content

💫 Toolkit to help you get started with SDD or any other process!

Add Spec Kit Design System extension to community catalog (#4707)

github-actions[bot]103bb048901c
diff --git a/docs/community/extensions.md b/docs/community/extensions.md
index 1c1e2254d..caeaf0f89 100644
--- a/docs/community/extensions.md
+++ b/docs/community/extensions.md
@@ -149,6 +149,7 @@ The following community-contributed extensions are available in [`catalog.commun
| Spec Critique Extension | Dual-lens critical review of spec and plan from product strategy and engineering risk perspectives | `docs` | Read-only | [spec-kit-critique](https://github.com/arunt14/spec-kit-critique) |
| Spec Diagram | Auto-generate Mermaid diagrams of SDD workflow state, feature progress, and task dependencies | `visibility` | Read-only | [spec-kit-diagram-](https://github.com/Quratulain-bilal/spec-kit-diagram-) |
| Spec Inventory | Read-only inventory of live requirement and task IDs, with focused per-task context packs instead of whole-file dumps | `visibility` | Read-only | [spec-kit-inventory-alignment](https://github.com/Yash-Chindam/spec-kit-inventory-alignment) |
+| Spec Kit Design System | Give it an RFC. It runs the Spec Kit workflow and implements the change using your design system. | `integration` | Read+Write | [spec-kit-design-system](https://github.com/artursopelnik/spec-kit-design-system) |
| Spec Kit Discovery Extension | Run technical discovery commands for feasibility, technology selection, scenario-specific technical decisions, legacy codebase assessment, implementation understanding, and proof-of-concept validation | `process` | Read+Write | [spec-kit-discovery](https://github.com/bigsmartben/spec-kit-discovery) |
| Spec Kit Figma | Grounds SpecKit spec/plan/tasks in Figma design context via REST or MCP, on macOS/Linux/Windows. | `integration` | Read+Write | [spec-kit-figma](https://github.com/Fyloss/spec-kit-figma) |
| Spec Kit Memory | Recalls prior specs and decisions from configurable memory tools (e.g. memsearch) before SDLC stages, so planning and specification start from what the project already knows | `docs` | Read+Write | [spec-kit-memory](https://github.com/zaytsevand/spec-kit-memory) |
diff --git a/extensions/catalog.community.json b/extensions/catalog.community.json
index d5725252c..80922298c 100644
--- a/extensions/catalog.community.json
+++ b/extensions/catalog.community.json
@@ -1808,6 +1808,52 @@
"created_at": "2026-08-17T00:00:00Z",
"updated_at": "2026-08-17T00:00:00Z"
},
+ "design": {
+ "name": "Spec Kit Design System",
+ "id": "design",
+ "description": "Give it an RFC. It runs the Spec Kit workflow and implements the change using your design system.",
+ "author": "artursopelnik",
+ "version": "0.1.0",
+ "download_url": "https://github.com/artursopelnik/spec-kit-design-system/archive/refs/tags/v0.1.0.zip",
+ "sha256": "787047d6a52399a7092f8bccca9268fc67f17de66723675fc83a9cd72604de4e",
+ "repository": "https://github.com/artursopelnik/spec-kit-design-system",
+ "homepage": "https://github.com/artursopelnik/spec-kit-design-system",
+ "documentation": "https://github.com/artursopelnik/spec-kit-design-system/blob/main/README.md",
+ "changelog": "https://github.com/artursopelnik/spec-kit-design-system/blob/main/CHANGELOG.md",
+ "license": "MIT",
+ "category": "integration",
+ "effect": "read-write",
+ "requires": {
+ "speckit_version": ">=1.0.0,<2.0.0",
+ "tools": [
+ {
+ "name": "python3",
+ "version": ">=3.9",
+ "required": true
+ },
+ {
+ "name": "bash",
+ "required": true
+ }
+ ]
+ },
+ "provides": {
+ "commands": 4,
+ "hooks": 3
+ },
+ "tags": [
+ "design-system",
+ "design-tokens",
+ "accessibility",
+ "autonomous",
+ "reuse"
+ ],
+ "verified": false,
+ "downloads": 0,
+ "stars": 0,
+ "created_at": "2026-09-23T00:00:00Z",
+ "updated_at": "2026-09-23T00:00:00Z"
+ },
"ears": {
"name": "EARS Requirements Syntax",
"id": "ears",