Give a project its own design rules with Unslop

Start with the person and the work

Open Unslop with Creative access. Enter the project name, who uses it and the main job they need to finish. Choose App for a working interface or Website for a public content page.

The output uses those details as context for its design rules. It does not replace your project, alter its files or claim that an unseen interface has passed a design review.

Choose a direction you can explain

Editorial lets writing lead, Technical emphasizes aligned work and controls, and Studio gives the output more room. Choose the spacing and, if needed, a six-digit accent color.

The token preview uses the same values as the downloadable CSS. Text/background and action-text contrast are measured from that palette; they are not an accessibility certification for the complete project.

Inspect existing CSS when it helps

Paste an optional stylesheet sample, up to 80,000 characters. The declaration review identifies literal colors outside token definitions, selected pixel values, priority overrides and an unusually broad radius scale.

Findings identify the declaration and a suggested next step. The review does not render your site or prove the entire layout correct. Leave out private values before submitting the stylesheet.

Keep and integrate the files

Download the ZIP for DESIGN.md, tokens.css, REVIEW.md and AGENTS.md. Inspect individual files first or copy the one you need.

Give the rules to your agent and map the reference values into your existing theme and components. Preserve the working framework, data and access checks. Verify the actual main workflow on desktop and a narrow screen after changes.

Copy as Markdown