← DevaultCONTENT HISTORY
WHAT CHANGED
Update to Devault
Snapshot Nov 16, 2026 · 18:15 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Devault and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Find a ready-made design system in Devault's DESIGN.md library and deliver it in the format the user's project needs. Use when the user wants a palette, design tokens, a theme, a DESIGN.md file or a starting visual style for a build, in Tailwind, CSS variables, shadcn/ui, design tokens, Figma variables, SwiftUI or Android.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 381
}
],
"name": "apply-design-system",
"skill_md_contents": "---\nname: apply-design-system\ndescription: Find a ready-made design system in Devault's DESIGN.md library and deliver it in the format the user's project needs. Use when the user wants a palette, design tokens, a theme, a DESIGN.md file or a starting visual style for a build, in Tailwind, CSS variables, shadcn/ui, design tokens, Figma variables, SwiftUI or Android.\n---\n\nUse this skill when the user wants a design system or tokens to build with,\nfor example \"give me a dark fintech theme for Tailwind\" or \"I need a DESIGN.md\nfor a warm editorial site\".\n\n## Steps\n\n1. Work out two things: the feel the user wants (for example \"dark saas\n dashboard\" or \"warm editorial\") and the format. The formats are\n `design-md`, `tailwind`, `css`, `shadcn`, `tokens`, `figma`, `swiftui`,\n `android` and `image-prompt`. If the user's stack makes the format obvious,\n use it. Otherwise ask, or use `design-md`.\n2. Call `get_style` with `query` set to the feel and `format` set to the\n format. If the user named an exact system, or pasted a link to a page under\n devault.design/design-md, pass its slug as `style` instead.\n3. If the user wants to choose from several, call `list_styles`, with a\n `category` if they named one, and show the names and taglines. Fetch the one\n they pick with `get_style`.\n4. To look at the design the system was derived from, call `get_screen_image`\n with the `view_token` from the `get_style` result. The image is for you:\n describe it, and point the user to the system's page (`url`) to see it.\n\n## What to deliver\n\n- The system's name, one line on its character, and its page (`url`).\n- The `content` exactly as returned, in a code block, ready to paste. Do not\n rename tokens or change colour values.\n- The contrast results that matter (`contrast`): which text colours pass on\n which surfaces, and any pair that fails.\n- If `alternatives` came back, name one or two in case the first is not right.\n\n## Rules\n\n- Do not invent a system, a token or a contrast grade. Use what the tool\n returned.\n- If nothing matches the query, say so and suggest a broader phrase.\n- When you apply the system to the user's code, keep the token names from the\n export so that a later export stays compatible.\n- An explicit instruction from the user takes priority over these steps.\n"
}SHA-256 of public snapshot: 4d2cbc8b0a913faf57400ed0760152674827bc8f98f16e1afa9191fa2d83091a