Design System
Design System: Define reusable visual rules for documents. Review brand colors, type, spacing, components, and accessibility constraints and produce a compact design system specification.
--- name: markdown-html-design-system description: Use for design system when asked to define reusable visual rules for documents; produce a compact design system specification. license: MIT metadata: author: Thrive category: markdown-html --- # Design System ## When to use Use this skill for design system when you need to define reusable visual rules for documents. The expected result is a compact design system specification. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect brand colors, type, spacing, components, and accessibility constraints. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Inventory headings, links, tables, code blocks, media, footnotes, and content that must survive conversion. 2. **Decide.** Turn the visual direction into tokens and consistent component rules. 3. **Produce.** Build a compact design system specification from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Choose semantic elements and navigation that preserve reading order. Avoid visual styling that changes meaning. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Preserve source headings, links, tables, and reading order. - Check responsive layout, keyboard access, and content completeness after conversion. ## Verification Check contrast and reuse across representative screens. Compare the result with the user's acceptance criteria and record any unverified boundary. Compare source and output section by section; check links, mobile layout, keyboard access, and print behavior. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a compact design system specification. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->