Supernova skills
Design system skills for your agents
Teach Claude, ChatGPT, Cursor and Codex to audit, document and maintain your design system through Supernova. Install them all at once, free and open source.
- Claude
- ChatGPT
- Cursor
- Codex
- GitHub Copilot
Check what you have
Audit the system, a Figma design or a pull request, and see what to fix first.
Audit your design system
Audits tokens, components, documentation and feedback in one pass and returns a ranked report of what to fix first. Read only.
Review a pull request for design system drift
Reviews a pull request for design system compliance: hand-built copies of library components, raw values, margin on components, component API misuse, accessibility and composition drift. Checks every finding against the tokens, code components and usage guidelines in Supernova, and returns one short review with blocking and advisory comments. Read only in Supernova; posts the review to GitHub only after the user approves the exact text.
Audit a Figma design
Audits a Figma frame, page or file against the design system in Supernova and reports drift and system gaps. It finds detached components, raw values, off-scale type and spacing, accessibility issues and default layer names, and routes system gaps to the design system team. Read only.
Keep docs current
Draft, fix and move documentation, and keep it in step with design and code.
Document new components
Documents components that exist in Figma but not yet in the documentation: creates the canonical component if it is missing, links its imported Figma component, and drafts a basic page with an intro, a Figma preview, its variants and its properties under their exact Figma names, leaving usage guidance as marked 'Needs a human' notes. Writes components, Figma links and unpublished pages in the shared draft after the user approves; never publishes.
Fix documentation gaps
Fixes documentation gaps: missing, copied or placeholder descriptions, thin or unfilled template pages, published placeholder and test pages, guidance copied from another component, and duplicate groups. Works from an audit-design-system report in the conversation, or finds the gaps itself. Writes page descriptions, page content and the page tree in the shared draft after the user approves; never publishes.
Migrate documentation into Supernova
Moves design system documentation into Supernova from a folder of Markdown or MDX files, Confluence, Notion, Figma documentation frames or zeroheight. It maps the source to a page tree and to Supernova blocks, and marks anything that cannot convert as "Needs a human". Writes documentation groups and pages in the shared draft after the user approves; never publishes.
Write release notes
Writes release notes for what changed in the design system since a date or a version: tokens, components and documentation, sorted into Added, Changed, Deprecated and Fixed, each with links. Reads only until the user asks for more; then writes the notes as an unpublished documentation page and/or posts them to a Slack channel the user names, after they approve the exact text; never publishes.
Sync docs with design and code
Compares each component's documentation page with its imported Figma component, its code component and its Storybook stories, and reports drift: changes on one side only, props and variants missing from the page, and renames. For changes where Figma and code agree, drafts the page updates. Writes page content in the shared draft after the user approves; never publishes.
Tokens and variables
Clean up tokens, and replace hard-coded values in Figma and code.
Clean up tokens
Finds token problems in Supernova (bad descriptions and names, unused or deprecated tokens) and plans the cleanup. Checks missing or wrong descriptions, placeholder names, naming and spelling, duplicate values, unused tokens, deprecated leftovers, empty groups, and orphaned tokens whose source is gone or no longer syncs. Writes token descriptions and names, and deletes unused tokens and empty groups, in the design system's shared draft after the user approves.
Migrate a Figma file to variables
Binds hard-coded values in a Figma file to the design system's variables and text styles, chosen by usage. It covers colours, radius, stroke width, spacing, sizing and type, and uses Supernova to pick semantic tokens. Writes variable bindings in Figma, never in Supernova, after the user approves the plan.
Migrate hardcoded values to tokens
Replaces hardcoded colors, spacing, radii, type and shadows in code with Supernova tokens, one small slice at a time. Matches by usage, not by value, prefers semantic tokens over primitives, and stops to ask on every ambiguous match. Read only in Supernova; edits code on a new local branch and commits only after the user approves the diff.
Build with the system
Turn designs into specs and components that follow the system.
Build a design system component
Builds a new design system component from a design spec: checks Supernova for an existing component or variant first, agrees the prop table before any code, then implements it with the system's tokens, every state, accessibility, tests, stories and docs. Read only in Supernova; writes code on a new local branch and commits only after the user approves the diff.
Write a handoff spec
Turns a Figma frame into an engineering handoff spec, checked against the components and guidance in Supernova. It covers the components and variants used, states, responsive behaviour, content edges, interactions, data, accessibility and open questions. Read only.
Close the loop
Turn what agents get stuck on into fixes, and give each team its own context.
Fix what agents report
Reads the unresolved feedback that AI agents left on the design system's MCP servers, groups it into themes, and maps each theme to a concrete fix: a missing documentation section, a wrong page, a missing token or guideline, or an MCP server that serves the wrong sources. Writes documentation fixes to the shared draft and marks the addressed feedback Resolved after the user approves. Never publishes and never deletes feedback.
Set up an MCP server per team
Recommends one MCP server per team (for example Payments or Android): which documentation pages, components, tokens, themes, knowledge files and workspace knowledge skills each team's agents should see, and which skills are missing. Creates or updates those MCP servers (Supernova Contexts) and their scope after the user approves.
Questions & answers
Give your agents a system worth following
See how Supernova documents, syncs, and serves your system in one place.