What is using-design-system?

A set of instructions for building feature screens with the project's X-components design system, a shared collection of interface elements, instead of Material3.

Use it when creating Compose UI screens, components, buttons, fields, text, loading states, or other feature-level interface code.

It prevents feature code from using inconsistent UI components and helps match existing design blueprints when they are available.

using-design-system — Skill for Claude Code by ThisIsSadeghi/KMPilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add ThisIsSadeghi/KMPilot --skill using-design-system

Clone the repo

git clone --depth 1 https://github.com/ThisIsSadeghi/KMPilot

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/thisissadeghi/kmpilot/using-design-system/github.svg)](https://agentmods.dev/skills/thisissadeghi/kmpilot/using-design-system)

Your own site

<a href="https://agentmods.dev/skills/thisissadeghi/kmpilot/using-design-system"><img src="https://agentmods.dev/badge/skills/thisissadeghi/kmpilot/using-design-system/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/thisissadeghi/kmpilot/using-design-system"><img src="https://agentmods.dev/badge/skills/thisissadeghi/kmpilot/using-design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.01088
Opus 5.5	$0.00015	$0.00435
Sonnet 5.5	$0.00007	$0.00218
Haiku 4.5	$0.00004	$0.00109

Measured 1mo ago against content hash 26938bbd9f29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

using-design-system scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/using-design-system/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using Design System

Use X-components from :core:designsystem instead of Material3 in feature modules.

Architecture Reference: @../_shared/patterns.md

Design-Aware Mode

If a Stitch design blueprint exists (.claude/docs/{featurename}/designs/{featurename}_blueprint.md with blueprintConsumed == false in stitch-project.json.features[featurename]), implementation skills auto-detect it and use the blueprint's component tree for UI implementation. This skill provides component mappings for existing code.

Core Rule

X-components ONLY in features. NO Material3 components.

Common Replacements

Material3	X-component
`Button`	`XButton` (7 variants)
`TextField`	`XTextField`
`Text`	`XText`
`Scaffold` (feature screen)	`XScreen` (Rule 13 — `XScaffold` is app-shell only)
`CircularProgressIndicator`	`XCircularProgressIndicator`
`coil3.compose.AsyncImage`	`{CORE_DESIGNSYSTEM_PKG}.AsyncImage`

Full mappings: @references/component-mappings.md Usage examples: @references/usage-examples.md

Key Rules

Imports: import {CORE_DESIGNSYSTEM_PKG}.* (avoid Material3 in features)
4-State UI: Uninitialized → Loading → Success → Failed (mandatory)
Theme: Never wrap screens in XTheme (app-level only). Feature screens use XScreen (Rule 13) — never a Scaffold/XScaffold, which would nest a second Scaffold and double the insets
Navigation: Use XNavHost (pre-configured animations)
ScreenRoot Pattern: {Feature}Screen + {Feature}ScreenRoot pair required
Strings (Rule 12): XText/XIcon text args take stringResource(Res.string.*), never literals. Shared strings via DesignSystemResources; ViewModel-origin via UiText. See @../_shared/patterns.md → "Strings & Localization (Rule 12)".
Typography (app-global type scale): text picks an M3 type-scale role — style = MaterialTheme.typography.{role} (or an XTextDefaults preset) — never raw fontSize/fontWeight/fontFamily, except a blueprint-recorded override (…typography.{role}.copy(...)). The font family is global (wired in XTheme.kt), never set per-screen. See @../_shared/patterns.md → "Typography".

Read the full file on GitHub · 69 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 69 lines · 37 tokens per session scan A 26938bbd9f29

Subscribe to this mod's changes

using-design-system is a skill published in the GitHub repository ThisIsSadeghi/KMPilot (56 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,088 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CSS and styling Claude Code Design and UX Frontend ai-agents ai-coding android kotlin template

proceed-video

A workflow for analysing short recordings of a single user-interface animation. It creates frame grids and motion-trail comparisons so the interaction can be studied visually.

niki914/zafiro · 78 tokens

proto-bot-getting-started

A first-conversation guide for starting an interface-prototyping task. It gathers the application, design rules, allowed changes, and preferred delivery format only as needed before producing an initial result.

makecindy/cindy · 43 tokens

proto-bot-ops

A workflow for turning an existing application into interface prototypes, implementing approved page changes, and collecting review evidence. It checks the real code, pages, components, data, and visual states instead of treating a design file as an integrated product.

makecindy/cindy · 38 tokens

using-design-system