Document a website’s design with AI
Turn the patterns already in your frontend into a shared design guide, with file references and a record of any disagreements between code and existing guidance.
Document a website’s design with AI when the answer to “what does this button look like?” is scattered across several files. The design-md skill reads the frontend, checks representative screens and traces decisions to the fonts, styles and components that implement them.
The outcome depends on what is already there. A consistent interface can be documented as it stands. Existing guides are merged without discarding their local rules. A new project gets a proposal to approve before its design direction is written into the final guide.
What it does
- Trace a spacing or type rule to the file that defines it.
- Keep a brand decision that appears only in an older document.
- Flag a mismatch between the documented component and the version on screen.
- Write a page-review checklist whose items can be checked in the code.
- Add a separate general frontend craft guide where the project has no equivalent.
Install and use
- Install the skill in a file-capable agent and open an authorised copy of the frontend. Reading the project and writing Markdown files are sufficient; no design-service account is required.
- Ask: “Document our current navigation and typography. Flag any conflict with the brand guide.”
- Review the resulting DESIGN.md. If the project already has an AGENTS.md, the skill adds a pointer so future contributors can find the guide.
FAQ
Source
Made by Nolly Studio (Jordan Gilliam). Original skill: design-md, published on GitHub under the MIT licence.
View on GitHub