agentleFS
Boxline-devBoxline-dev/examples/skills/design/SKILL.md

design

Skill1 starsChanged 35 days agoMITView on GitHub

Extract a website's design system into DESIGN.md - colors, fonts, type scale, spacing, radii, shadows, CSS design tokens and the look of its buttons, inputs and cards - measured from computed styles in a real browser (Boxline). Use when asked to copy, match, document or audit a site's look. Usage /design <url> [more pages].

  • Reads credentials

197 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use banner-design, ui-styling and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 38 projects that use this

  • MicrosoftSkill

    ui-styling

    Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

    Also in 39 projects that use this

  • seikaikyoSkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 43 projects that use this

  • mayankjain1815-commitsSkill

    infra-audit

    Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.

    Also in 3 projects that use this

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 42 projects that use this

  • AnthropicSkill

    design-system

    Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.

    Also in 49 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write DESIGN.md from what the site's pages really use, measured in a Boxline browser.

    line 8
  2. Very specific:

    Measure: Run this skill's script from this skill's folder (Node 18+, BOXLINE_API_KEY set):

    line 14
  3. Distinctive:

    Only measured values; leave out a section with no data.

    line 84

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/design: a site's design system

Write DESIGN.md from what the site's pages really use, measured in a Boxline browser.

Steps

  1. The address. Take the URL the user gave (add https:// when it has no scheme). One to three pages of the same site measure better than one: the home page plus, say, pricing and a docs page.
  2. Measure. Run this skill's script from this skill's folder (Node 18+, BOXLINE_API_KEY set):

    npx -y -p @boxline/sdk node measure.mjs <url> [<url> …] > /tmp/design.json

    It opens each page at 1440×900 and prints, for each:

    • page: background, text color, base font;
    • colors: backgrounds weighted by area, text colors by amount of text, borders;
    • fonts: families for headings, body and code, sizes and weights by use;
    • spacing, radii, shadows: values by how often they occur;
    • components: distinct button styles, inputs and cards;
    • tokens: CSS custom properties on :root;
    • darkMode: whether the style sheets have dark-mode rules.

    With only the MCP server: session_create, browser_navigate, then browser_act with one evaluate action whose expression is the MEASURE expression from measure.mjs ({"action": "evaluate", "expression": MEASURE}; the value it returns follows the step's line), then session_stop.

  3. Read it as a designer.
    • Neutral: the page background and the most-used text color.
    • Accent: the background of the most prominent buttons, and colored links.
    • Type scale: the sizes in order.
    • Spacing scale: the values that recur, in order (ignore one-offs).
    • Radii and shadows: the ones that recur.
    • Buttons: primary is the filled one with the accent background; secondary the outlined or plain one.
  4. Write DESIGN.md in the project root, in the format below.

Format

# DESIGN.md

> Design system of <url>, measured with Boxline on <YYYY-MM-DD> (pages: …)

## Colors
- Background: #…  · Text: #…  · Muted text: #…
- Accent: #… (primary buttons, links)
- Borders: #…

## Typography
- Headings: <family> · Body: <family> · Code: <family>
- Sizes: 14px, 16px, 20px, 32px, 48px
- Weights: 400, 500, 700

## Spacing
4px, 8px, 16px, 24px, 48px

## Radii
- Buttons and inputs: 6px · Cards: 12px · Pills: 9999px

## Shadows
- Cards: <value>

## Components
### Buttons
- Primary: background #…, text #…, radius 6px, padding 10px 16px, 600 weight
- Secondary: …
### Inputs
### Cards

## Design tokens
| Token | Value |
|---|---|

## Dark mode
The site has dark-mode styles (prefers-color-scheme).

Rules

  • Only measured values; leave out a section with no data. Never invent a value.
  • Colors in hex, sizes in px. Say which page a value comes from when pages differ.
  • Tokens: list the ones that look like design tokens (colors, fonts, sizes, radii), at most 40.
  • No emojis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.