design-systems skillA
design-systems is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Build UI inside an existing design system — find its tokens and components, reuse before adding, decide between extending a component and introducing a new one, and preserve conventions you did not set. Use when a project already has design tokens, a component library, a theme or a shared Figma library and you are about to add or change UI inside it. Not for establishing a visual direction where no system exists, and not for reviewing an interface's usability..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Working inside a design system A system's value is that everything in it agrees. The expensive mistakes are not ugly components — they are the private token, the one-off override and the sixth button variant, each individually reasonable, which together turn a system back into a pile of CSS. ## When this fires The project already has tokens, a component library, a theme or a shared library, and you are adding or changing UI inside it. It does not fire when there is no system and the decisions are yours — that is `frontend-design`. ## Procedure 1. **Find the system before writing anything.** Locate the token source, the component directory, its documentation, and two or three real usage sites. Say where each lives. If the system is a third-party library, read its current documentation rather than recalling its API — versions move and a guessed prop is a silent fork. 2. **Read the conventions you did not set**: token naming and whether tokens are primitive or semantic, how variants are expressed (props, classes, compound components), how theming and dark mode resolve, file and export layout, and what the existing components already handle that …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/design-systems@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/design-systems@sha256:bebe1e044a418128Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qcci5yovhsdylo7c)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5826 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qcci5yovhsdylo7c GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/design-systems GET https://markdownregistry.com/api/v1/blob/bebe1e044a4181280123ef31347954fa5609157aeff63707317c1bc21e0d4349
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.