Design systems / Design reference library

Refero Styles

Turn a visual reference into a starting system an agent can read.

Documentation reviewed

Source review
Oct 18, 2026

Understand the resource

What it is.

Refero publishes website style references as DESIGN.md files, including typography, color, spacing and components. The useful output is a set of design decisions to inspect before an agent starts building.

When it is useful

You have a clear visual direction but need to explain it consistently across several screens.

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

Select a reference with similar information density, then map its type and spacing choices onto your own brand tokens.

Result to aim for

A reviewed design brief with explicit token choices.

Before you start

What you need.

A browser and an editor for reviewing the downloaded design file.

The practical boundaries

What to watch for.

A reference brand’s identity is not permission to reproduce its logos, imagery or complete interface.
Extracted styles do not establish keyboard behavior, contrast compliance or conversion performance.

Review record

What we could establish.

Public primary documentation reviewed. See the account-free evaluation for executed checks and remaining workflow limits.

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.

Bounded runtime checkedAccount-free · Oct 19, 2026

The public Linear reference opened with color, typography, spacing and guideline sections. This is a usable style-reference browsing result; no downloaded DESIGN.md was executed.

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

Target: https://styles.refero.design/
Version or capture: Unversioned public page observed on 2026-10-19
Integrity scope: sha256:97ded592e5aa6d3d1a45a20b31ddcaf84f00df1d0e8261bd9bdda26e0e26fc96 — 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://styles.refero.design/. 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 “Website Styles & DESIGN.md Library | Refero Styles”. 42 image elements were present; no account was used.
Observed public sample or navigation
pass
Public browser sample: Follow the observed Linear midnight precision instrument link to https://styles.refero.design/style/90ce5883-bb24-4466-93f7-801cd617b0d1.
Observed: The destination returned 200; title: “Linear design system | Refero Styles”. 3 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

Refero Styles attempted requests to 3 additional hosts, including www.googletagmanager.com, images.refero.design, t0.gstatic.com. 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

Review the reference tokens against your own brand before using them in an agent prompt. The sample exposes visual choices, not the original product’s behavior.

Practical caveats

Review the reference tokens against your own brand before using them in an agent prompt. The sample exposes visual choices, not the original product’s behavior.
A reference brand’s identity is not permission to reproduce its logos, imagery or complete interface.

What remains untested

DESIGN.md download completeness, extraction accuracy, account features and MCP access were not tested.
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.
4 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