layout-system

Designs web UI layouts by extracting structural rules from production references.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill layout-system-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: layout-system
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/layout-system
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill layout-system-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing non-trivial web layouts from memory or generic UI conventions produces disorganized, arbitrary interfaces. This Skill replaces guesswork with a disciplined workflow that inspects real production references, extracts their structural rules, and translates them into your project's design language. ## Core Features & Use Cases - Surface Classification: Categorizes pages into Marketing/LP, Dashboard/Data, Application/Tool, or Swiss/Editorial families, each with dedicated reference guidance. - Reference-Driven Extraction: Inspects rendered production interfaces across multiple viewport widths to derive alignment axes, grid geometry, hierarchy, and responsive transformation rules. - Token Derivation & Verification: Converts repeated layout relationships into semantic CSS tokens and enforces a visual verification gate beyond compile and lint success. - Use Case: When building a SaaS dashboard, use this Skill to inspect two real analytics products, extract their app shell, canvas, and widget layering rules, then implement and visually verify the layout in your own design system. ## Quick Start Use the layout-system skill to design and implement the dashboard page layout based on real production references.

Frequently Asked Questions about layout-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a dashboard layout based on real products?

Classify the surface as Dashboard/Data, then inspect at least two production analytics tools in a browser at multiple viewport widths. Extract the three-layer structure of app shell, dashboard canvas, and widget internals, then translate those rules into your project's tokens.

How to extract grid and spacing rules from an existing website?

Open the rendered page in a browser and inspect computed styles, bounding boxes, grid and flex definitions, gaps, and padding at desktop, laptop, and mobile widths. Prioritize repeated alignment axes over isolated CSS values as evidence of structural rules.

Should I copy pixel values from reference websites directly?

No, copying arbitrary values like a 256px sidebar ignores your project's density, typography, and tokens. Instead, extract the underlying relationship, such as a stable navigation rail with fluid workspace width, and derive the value from your own design system.

What layout families does this approach cover?

It covers four families: Marketing/LP, Dashboard/Data, Application/Tool, and Swiss/Editorial. Mixed products can classify each route separately, such as marketing homepage, application workspace, and analytics dashboard, without forcing one global grid.

Why does my implemented layout still look disorganized after passing tests?

Compile and lint success does not verify visual quality. Check for too many unrelated widths, inconsistent gutters, weak alignment axes, duplicated nested padding, wrong scroll ownership, and arbitrary card sizing, then compare against references at the same viewport.