Sekura Design MCP

Get paste-ready component code

get_component_code

Read-only

Retrieve production-ready component code for a chosen framework, including markup, styles, lifecycle wiring, and dependency metadata for correct implementation.

Instructions

Production code for a component in the requested framework. HTML returns reference markup with the required ARIA wiring; CSS returns the production stylesheet written against semantic tokens; framework options return editable reference recipes with native markup and lifecycle wiring. Inspect implementation metadata for dependencies and application responsibilities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Component id.
`framework`	Yes	html: Reference markup. Load sekura.css and the behaviour bundle, then call Sekura.enhance(). \| css: Component CSS. Read implementation.cssDependencies for required child styles, or load sekura.css. \| react: React TypeScript reference recipe with native markup, unique IDs, editable children and controller cleanup. \| vue: Vue reference recipe with native markup, slots and controller cleanup. \| svelte: Svelte reference recipe with native markup, snippets and controller cleanup. \| angular: Angular standalone reference component with native markup and controller cleanup. \| blazor: Blazor reference component. Requires the IIFE bundle and the documented JS lifecycle bridge. \| web-component: Light-DOM reference element with native markup and controller cleanup.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes
`version`	Yes
`framework`	Yes
`componentId`	Yes
`schemaVersion`	Yes
`implementation`	Yes
`initialization`	Yes
`requiredStylesheets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.0Oct 3, 2026

addedOutput schema / properties / implementation / properties / runtime

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "autoSelectors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "controllers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "manualOnly": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "controllers",
+    "autoSelectors",
+    "manualOnly",
+    "notes"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / implementation / required

Previous value: -[
-  "rootClass",
-  "cssDependencies",
-  "svgSymbols",
-  "controller",
-  "behavior",
-  "frameworkOutput",
-  "applicationResponsibilities",
-  "events",
-  "autoMarker",
-  "nativeReactExport"
-]New value: +[
+  "runtime",
+  "rootClass",
+  "cssDependencies",
+  "svgSymbols",
+  "controller",
+  "behavior",
+  "frameworkOutput",
+  "applicationResponsibilities",
+  "events",
+  "autoMarker",
+  "nativeReactExport"
+]

Changed3 schema fields changedv2.1.0Sep 8, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / framework / description

Previous value: -"html: Reference markup with the required ARIA wiring in place. | css: The production stylesheet for this component, written against semantic tokens. | react: TypeScript React component with forwardRef and typed variant props. | vue: Vue 3 single-file component using the composition API. | svelte: Svelte 5 component using runes. | angular: Angular standalone component. | blazor: Blazor Razor component with typed parameters. | web-component: Framework-free custom element wrapping the same classes."New value: +"html: Reference markup. Load sekura.css and the behaviour bundle, then call Sekura.enhance(). | css: Component CSS. Read implementation.cssDependencies for required child styles, or load sekura.css. | react: React TypeScript reference recipe with native markup, unique IDs, editable children and controller cleanup. | vue: Vue reference recipe with native markup, slots and controller cleanup. | svelte: Svelte reference recipe with native markup, snippets and controller cleanup. | angular: Angular standalone reference component with native markup and controller cleanup. | blazor: Blazor reference component. Requires the IIFE bundle and the documented JS lifecycle bridge. | web-component: Light-DOM reference element with native markup and controller cleanup."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "componentId": {
+      "type": "string"
+    },
+    "framework": {
+      "enum": [
+        "html",
+        "css",
+        "react",
+        "vue",
+        "svelte",
+        "angular",
+        "blazor",
+        "web-component"
+      ],
+      "type": "string"
+    },
+    "implementation": {
+      "additionalProperties": false,
+      "properties": {
+        "applicationResponsibilities": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "autoMarker": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "behavior": {
+          "enum": [
+            "native",
+            "controller",
+            "application"
+          ],
+          "type": "string"
+        },
+        "controller": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "cssDependencies": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "events": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "applicationRequired": {
+                "type": "boolean"
+              },
+              "detail": {
+                "additionalProperties": {
+                  "type": "string"
+                },
+                "propertyNames": {
+                  "type": "string"
+                },
+                "type": "object"
+              },
+              "name": {
+                "type": "string"
+              },
+              "source": {
+                "enum": [
+                  "native",
+                  "controller"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "detail",
+              "source",
+              "applicationRequired"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "frameworkOutput": {
+          "const": "reference-recipe",
+          "type": "string"
+        },
+        "nativeReactExport": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "rootClass": {
+          "type": "string"
+        },
+        "svgSymbols": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "rootClass",
+        "cssDependencies",
+        "svgSymbols",
+        "controller",
+        "behavior",
+        "frameworkOutput",
+        "applicationResponsibilities",
+        "events",
+        "autoMarker",
+        "nativeReactExport"
+      ],
+      "type": "object"
+    },
+    "initialization": {
+      "type": "string"
+    },
+    "requiredStylesheets": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "schemaVersion": {
+      "const": 1,
+      "type": "number"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "version",
+    "componentId",
+    "framework",
+    "code",
+    "implementation",
+    "requiredStylesheets",
+    "initialization"
+  ],
+  "type": "object"
+}

First observedv1.0.0Aug 5, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real substance beyond that: it discloses what each framework mode returns (reference markup with ARIA wiring, production stylesheet on semantic tokens, editable recipes with lifecycle wiring) and points to implementation metadata for dependencies and responsibilities.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the core purpose before per-framework behavior and the metadata pointer. Every sentence carries content, though the middle sentence is somewhat packed and could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained; annotations cover the safety profile; and the schema fully documents both parameters. The description completes the picture by noting the metadata pointer for dependencies and application responsibilities, leaving no critical gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the enum descriptions are highly detailed, so the schema carries the parameter semantics. The description only summarizes the framework families (HTML/CSS/framework options) without adding syntax or format detail beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (returns 'Production code') and resource (a component in the requested framework), so the agent knows it produces framework-specific implementation code. It does not explicitly differentiate from siblings like get_component or get_behavior, leaving the boundary slightly inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what each framework option yields (HTML vs CSS vs framework recipes), which implicitly guides selection, but gives no explicit when-to-use vs when-not or named alternative tools. Usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.