Skip to content
🧭
Meg detail route

Design System

Use this page when the missing piece is the design language itself: the PDLP layers, component precedent, and route grammar Meg wants settled before implementation compounds drift.
Validated · Sep 8, 2026The Meg proof still matches the district contract, the rule-before-build split, and the sibling-route exits that keep Review, Handoff, and Scout visible before the lower detail sections begin.
Start here on phone

Keep the design-language answer here, then jump sideways once the question changes into review scope, handoff timing, or delivery follow-through.

ReviewJump here when the route exists and the missing answer is what Meg can judge on the rendered screen.HandoffJump here when the real blocker is timing or request shape instead of the rule itself.ScoutJump here when the design rule is clear and the next move belongs back with the delivery owner.
First question

Use this street when the design language should shape the work before code spreads

Most readers do not need a history lesson about design systems. They need the fast split between rules-before-build, review-after-ship, and handoff mechanics. Start there.

Pick the street by the kind of uncertainty you have

Meg is most useful when Atlas keeps design rules, review scope, and handoff mechanics distinct instead of flattening them into one generic helper page.
Question
The missing piece is the visual language the route should follow before build.
Start with
Start with the design system.
Why
Meg prevents drift most effectively before the route invents local patterns. This street exists to define the design rules first, not to justify them after the UI has already sprawled.
Use this when the question is about tokens, spacing, components, layout hierarchy, or how the page should feel before implementation compounds.
Question
The route already exists and you need Meg to judge the visible result.
Start with
Leave for Meg Capabilities.
Why
That is a review-scope question. Capabilities explains what Meg can audit on a rendered screen and what proof package makes the verdict useful.
Think screenshot audit, proof expectations, and where the design gate stops once the page is real.
Question
The design language is clear, but the handoff to Meg is what feels fuzzy.
Start with
Leave for the Integration Guide.
Why
Integration is the street for timing and handoff shape. It explains when to involve Meg and what a clean request contains without turning Atlas into a command manual.
Use that page when the real blocker is not the rule itself but how to ask for direction or review.
What the PDLP governs

The design system exists to make route-level decisions reusable

Meg's design language is not a palette dump. It is the shared rule set that keeps project-level hierarchy, components, and evidence expectations coherent as more builders touch the product.
Project language comes before component choices

Meg uses the PDLP to define the tone, hierarchy, and visual rules of a project before teams argue about isolated widgets.

The useful first question is what the screen should communicate and prioritize, not which button variant looks nicest in isolation.
Tokens keep recurring decisions from drifting

Color roles, typography, spacing, and density should be named semantically so every route can stay in the same visual system.

Treat tokens as shared language, not as a bag of one-off values copied into whichever page ships next.
Component rules describe precedent, not just parts

Meg cares about when a pattern should repeat and what kind of UI surface it represents, not only about whether a component technically exists.

That is why design-system guidance often sounds like route grammar: one hero, scan-first sections, and fewer equal-weight boxes.
Evidence expectations are part of the design language

The PDLP is not only static styling. It also shapes what proof is needed before Meg considers a route visually coherent enough to pass.

Direction before build and screenshot review after ship are both consequences of the same design-system contract.
Boundaries

Meg sets the visual rules, but this street does not own the whole delivery path

The design system matters because it prevents drift early. It should not turn into a catch-all page for implementation steps, runtime details, or ownership questions that belong somewhere else.

Continue through the Meg cluster

Meg Capabilities

See what Meg can review, what proof she expects, and where the design gate stops.

Open Meg Capabilities
Integration Guide

Learn how a builder asks for direction before build or a screenshot audit after ship.

Open Integration Guide
Scout District

Return to the delivery owner once the design rules and boundaries are clear.

Open Scout District