dembrandt
Skill1 starsChanged 3 months agoMITView on GitHub
Extract and analyze live website design systems into design tokens, brand identity, typography, colors, spacing, surfaces, components, WCAG reports, DESIGN.md, Tailwind v4 themes, DTCG JSON, drift reports, and HTML or brand-guide artifacts. Use when asked to reverse-engineer, document, compare, audit, or enforce a website’s visual system from a URL, or when Dembrandt CLI/MCP workflows are needed.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dembrandt/dembrandt-skillstheir own version, first seen Jul 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dembrandt/dembrandt-skills★ 194same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use Dembrandt to measure a website’s observed design system rather than inventing one.
- Very specific: line 14
Prefer the Dembrandt MCP tools: when they are available in the current agent environment.
- Distinctive: line 15
Use the CLI through the shell: when MCP is unavailable, when files must be written locally, or when a reproducible CI command is required.
- Distinctive: line 17
Read references/mcp-tools.md for the MCP tool contract, references/cli-and-exports.md for CLI options and output selection, and …
- Very specific: line 22
Select the observation context: Use desktop by default. Add mobile when responsive behavior matters, dark-mode when the dark theme is in …
- Very specific: line 24
Extract machine-readable evidence: Prefer --json-only for agent processing and --save-output when a durable artifact is needed.
- Distinctive: line 27
Verify the result: Check that the output exists, is parseable, and matches the requested scope.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dembrandt
Use Dembrandt to measure a website’s observed design system rather than inventing one. It renders the target with a real browser, reads computed DOM styles, and returns evidence for colors, typography, spacing, borders, radii, shadows, motion, components, responsive behavior, branding, frameworks, and icons.
Authorization rule: Analyze only sites the user owns or is authorized to inspect, and only where automated access is permitted. Respect the site’s Terms of Service,
robots.txt, rate limits, copyright, and third-party brand rights. Treat cookies, API keys, and extracted brand assets as sensitive.
Choose the execution route
- Prefer the Dembrandt MCP tools when they are available in the current agent environment. Use the extraction tools for live pages, then poll the returned job with
get_job_statusunless the user explicitly needs a blocking result. - Use the CLI through the shell when MCP is unavailable, when files must be written locally, or when a reproducible CI command is required. Use
npx dembrandt ...for an ephemeral install or the globally installeddembrandtcommand for a project that already depends on it. - Use pure analysis tools such as
compute_drift,get_findings,export_dtcg, orgenerate_design_mdon an existing extraction instead of reloading the website. - Read references/mcp-tools.md for the MCP tool contract, references/cli-and-exports.md for CLI options and output selection, and references/ci-drift.md for baseline and CI work.
Standard extraction workflow
- Define the question and scope. Decide whether the user needs a full design system, a focused category, a responsive comparison, an accessibility audit, a brand guide, or a drift check. Confirm the URL and authorization when it is not obvious.
- Select the observation context. Use desktop by default. Add
mobilewhen responsive behavior matters,dark-modewhen the dark theme is in scope,wcagfor contrast evidence, andcrawlor explicit paths when one page is insufficient. Usesitemapwhen navigation links are incomplete. - Prepare the browser. Dembrandt requires Node.js 18 or later and a browser binary matching its bundled
playwright-core. Rundembrandt install-browseronce before the first CLI extraction. In Linux CI, install the matching browser system dependencies or use a compatible Playwright container. If a browser already exists, useBROWSER_CDP_ENDPOINTwith Chromium. - Extract machine-readable evidence. Prefer
--json-onlyfor agent processing and--save-outputwhen a durable artifact is needed. Use--slowfor heavy single-page applications. Preserve the raw extraction before transforming it. - Interpret conservatively. Distinguish observed values from recommendations. Treat confidence, frequency, semantic context, viewport, color scheme, and page coverage as evidence. Do not fill omitted sections with guessed defaults. Account for the limitations below before making design claims.
- Export for the destination. Choose DTCG for token pipelines,
DESIGN.mdfor AI-readable project guidance, Tailwind v4@themeCSS for a Tailwind project,--brand-guidefor a printable summary, and--htmlorrender_reportfor a self-contained review artifact. - Verify the result. Check that the output exists, is parseable, and matches the requested scope. For a comparison, use the same browser, viewport, routes, wait behavior, and Dembrandt version for baseline and candidate whenever possible.
Quick command selection
| Need | Preferred command or operation | Result |
| Full extraction | dembrandt URL --json-only | Raw extraction JSON on stdout |
| Persist JSON | dembrandt URL --save-output | Timestamped JSON under output/ |
| W3C token pipeline | dembrandt URL --dtcg | .tokens.json DTCG export |
| AI-readable design guidance | dembrandt URL --design-md | DESIGN.md |
| Tailwind v4 project | dembrandt URL --tailwind | Observed-value @theme CSS |
| Accessibility review | dembrandt URL --wcag | DOM-based contrast results and grades |
| Responsive or theme comparison | Add --mobile or --dark-mode | Context-specific extraction |
| Multi-page system | dembrandt URL --crawl N or explicit paths | Merged extraction with cross-page evidence |
| Printable summary | dembrandt URL --brand-guide | Brand-guide PDF |
| Drift gate | dembrandt URL --compare baseline.json --json-only | Drift JSON and exit status |
Decision rules and failure handling
Use --slow before concluding that a JavaScript-heavy site is inaccessible. If Chromium is blocked or unreliable, install Firefox and retry with --browser=firefox; use --stealth only when the user is authorized to access the site and the site’s rules permit it. Use --no-sandbox only in an appropriately isolated container or CI runner. For authenticated pages, pass a cookie only when the user has supplied an authorized session value; never expose it in logs or final output.
Treat extraction failure as different from design drift. In CLI drift gates, exit code 1 means drift, 2 means extraction or browser failure, and 67 means a navigation timeout that is generally retryable with --slow. Do not approve or overwrite a baseline merely because extraction failed or because the candidate used a different observation context.
Dembrandt does not fully analyze Canvas/WebGL-rendered interfaces, may miss dynamically loaded content, does not automatically infer dark mode, and reads hover/focus states primarily from CSS rather than complete interactive behavior. The default desktop viewport is 1920×1080; the mobile profile is 390×844. Report these constraints whenever they could affect the user’s conclusion.
MCP operating pattern
Extraction MCP tools return a job_id by default because browser work can take 15–40 seconds. Poll get_job_status until the status is completed, then pass the returned extraction to the pure analysis or export tools. Set sync: true only when blocking is acceptable and the result is small enough to use directly. Keep concurrent live extractions modest; the server limits active jobs to two.
Use focused tools when the user asks for one category, and use get_design_tokens when the complete context is needed. After extraction, prefer this sequence for quality work: get_findings to identify problems, compute_drift to compare against a baseline, then export_dtcg, generate_design_md, or render_report for delivery. See references/mcp-tools.md for the exact catalog.
Output discipline
Label every deliverable with its source URL, extraction context, timestamp, and whether it is raw evidence or an interpretation. Keep raw JSON alongside derived files. When summarizing colors or typography, retain the original notation and semantic context even if the user requests a transformed format. Tailwind output contains observed values only: do not present absent shade ramps, hover variants, or on-color values as if Dembrandt measured them.
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

