Agent skills

[⏱️ ~4 min] Install the MDK Developer Skill suite so your coding agent knows MDK conventions, component props, and the page recipe

Overview

The MDK Developer Skill suite (@tetherto/mdk-skill) is how an AI coding agent learns to build with MDK. It ships procedural context in the universal Agent Skills format (SKILL.md), so any skills-aware agent (Cursor, Claude Code, and others) becomes fluent in MDK conventions as soon as the suite is installed.

Nothing here calls a network or a model. Each skill is a file the agent reads, bundled with the component registry MDK builds from its own source. Install once, then let the agent do the rest.

Prerequisites

mdk on your PATH (see Install the CLI)

Install

From your project root:

mdk skill add   # Adds both Cursor and Claude Code

Optional flags

Use --client to target a named agent, or --dir to install into another directory, for example:

mdk skill add --client cursor # .cursor/skills/
mdk skill add --client claude # .claude/skills/
mdk skill add --dir path/to/app # target another directory

The CLI reference lists the options. mdk onboard also offers the install as one of its steps.

Skills land flat: one directory per skill, each with its own SKILL.md. Agents discover them automatically, so there is no rule file to wire by hand.

What the suite covers

The suite ships a router plus workflows for device workers, Gateway plugins, UI pages, and stack deployment. Each skill's description frontmatter is its routing trigger, so you state an intent in plain language and the right skill activates; composite prompts route as an ordered chain through the router. See the skill suite for the current inventory and each skill's triggers, and the routing prompts for worked examples.

What the UI skill knows

Use the mdk-ui-component skill to build dashboards. Alongside its workflow it carries:

The React Devkit's generated component registry, listing every agent-ready component with its exact prop names and types, so an agent can't invent props that do not exist. It's generated from the devkit's source on every release and never hand-written.
The page recipe: the layer-by-layer contract a page follows.

A page is composition only: data comes from a Gateway route, a hook shapes the payload, the page is thin glue that calls the hook, and the visuals come from the Devkit. The page recipe spells out each layer's responsibilities.

Verify the install

Open the project in a skills-aware agent and state one of the intents above. The agent should name the skill it activated. If nothing activates, confirm the skill files landed in your project (for example under .cursor/skills/ or .claude/skills/). Those directories are gitignored by default, so the suite is installed per developer, not committed.

Next steps

Build a dashboard: put the skills to work on a real page
See the end-to-end flow the skill follows:
Review each layer's responsibilities:
Browse the components the agent composes