Design systems / Design system extractor

DesignMD

Inspect a website’s visual system before drafting new screens.

Documentation reviewed

Source review
Oct 18, 2026

Understand the resource

What it is.

DesignMD describes a website-to-design-system workflow: a URL becomes a DESIGN.md file, an HTML specimen and a Figma import. Use those outputs as a starting inventory to compare with the site before adopting its visual decisions.

When it is useful

You have an approved public reference and want concrete style values to review.

A proposed application

Put it to work.

This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.

Try this

Extract an owned marketing site, compare heading sizes with the live page, and remove accidental one-off colors before adopting the result.

Result to aim for

A corrected token inventory and implementation brief.

Before you start

What you need.

A public website URL; generation and optional exports may require service access.

The practical boundaries

What to watch for.

The publisher’s claims of exact extraction were not independently tested.
A crawl can miss authenticated states, responsive behavior and interaction semantics; use public, authorized inputs.

Review record

What we could establish.

Current primary documentation describes extraction from websites. No generation, export or account workflow was tested.

Source coverage and runtime coverage are separate

The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.

Check current access, terms, licensing and data handling before using a resource with your own material.

Runtime and security evaluation

What the evaluation covers.

Limited evaluationAccount-free · Oct 19, 2026

The Discover route opened a public collection of design systems, with reference images loading. The URL-to-design-system generator remained outside the test.

Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.

Target: https://designmd.me/
Version or capture: Unversioned public page observed on 2026-10-19
Integrity scope: sha256:898ec88e2f1a3885af8b397cb2edfbd9b9c5d208ba548f286ca74b5b42412ef3 — initial HTTP 200 response body only; not whole-application integrity.

Test conditions

Chromium 155.0.8059.82, 1365×900 desktop viewport.
Separate fresh, ephemeral browser contexts for entry and interaction; no owner profile, credentials or stored session.
Only GET/HEAD network requests allowed; forms, downloads, WebSockets and service workers blocked. Some analytics endpoints also blocked.
Short bounded waits; no mobile, assistive-technology, cross-browser or performance certification.

Individual checks and observations

Public HTTP response
pass
Public HTTP response: Anonymous GET with redirects followed, response-body SHA-256 and selected security-header summaries; no cookies retained.
Observed: The standalone client received 200 at https://designmd.me/. This establishes response delivery only.
Fresh browser entry
pass
Public browser sample: Open the catalog URL in a new anonymous Chromium context with read-only network guards and no inherited profile.
Observed: The document returned 200 and identified itself as “DesignMD — Generate DESIGN.md Files with AI”. 6 image elements were present; no account was used.
Observed public sample or navigation
pass
Public browser sample: Follow the observed Discover link to https://designmd.me/discover.
Observed: The destination returned 200; title: “Discover design systems — DesignMD | DesignMD”. 13 page image elements had decoded during the bounded wait. This count is not a catalog size or performance benchmark.

Security findings and boundaries

Passive inspection of the initial public document’s response headers and anonymous browser request hostnames, with read-only guards. No source exploitation, account access, dependency audit or private data.

Observed · info

Public response protections

The initial browser page used HTTPS. Its response included HSTS. No enforcing Content-Security-Policy response header was observed. This records the sampled response only; meta policies, backend authorization and exploit resistance were not assessed.

Observed · info

Request surface in the anonymous visit

DesignMD attempted requests to 3 additional hosts, including www.googletagmanager.com, www.google.com, api.designmd.me. Host counts include requests stopped by the test guard; they do not establish what data a service retained.

Practical advice · caution

Before using this reference

Use Discover to inspect an existing reference before deciding whether to submit a site for extraction.

Practical caveats

Use Discover to inspect an existing reference before deciding whether to submit a site for extraction.
The publisher’s claims of exact extraction were not independently tested.

What remains untested

No URL was submitted, no generation credit used and no HTML or Figma export produced; account and export requirements remain unverified.
Results describe the observed public pages and a bounded action, not the entire product or the referenced designs.

Security limits

No authentication, authorization, tenant separation, data retention or backend handling was tested.
Header presence or absence is a sampled configuration observation, not a security certification or an exploit finding.
3 blocked-request records were retained across entry and interaction checks. Guards may alter normal page behavior; the logs do not represent unrestricted traffic.

Evaluation sources

Download this evaluation record (JSON)

Follow the evidence

Sources and further reading.

Primary product page

Keep exploring