dryui-build

DryUI Page Layout: Fixture First

Build the supplied design image as a finished DryUI app page. Optimize for a clean build, lint-safe layout, and responsive shell fidelity before visual embellishment.

Harness Rule

Run bun run build before final. Do not run dev servers, browser checks, extra audits, or broad package searches. The harness captures mobile, tablet, and desktop after you finish.

Stage 1: Pick One Recipe

Identify the page as one of these recipes and keep the fixed shell:

• dashboard: metrics in primary, chart/table panels below, activity in secondary.
• settings: nav in navigation, form/status panels in primary, help/activity in secondary.
• crm: pipeline/list panels in primary, deal summary in secondary.
• kanban: board columns in primary, project health in secondary.
• knowledge: documents/search/results in primary, source summary in secondary.

Use this shell exactly:

<main data-layout="app-shell">
	<div data-layout-area="page">
		<header data-layout-area="topbar">...</header>
		<nav data-layout-area="navigation">...</nav>
		<section data-layout-area="primary">...</section>
		<aside data-layout-area="secondary">...</aside>
	</div>
</main>

Stage 2: Build With Safe Elements

Use these imports only unless build reports a missing import:

import {Badge} from '@dryui/ui/badge'; import {Button} from '@dryui/ui/button'; import {Heading} from
'@dryui/ui/heading'; import {Image} from '@dryui/ui/image'; import {Input} from '@dryui/ui/input'; import
{Link} from '@dryui/ui/link'; import {Separator} from '@dryui/ui/separator'; import {Table} from '@dryui/ui/table';
import {Text} from '@dryui/ui/text';

Do not use raw text/media/link elements: no <p>, <span>, <strong>, <img>, <a>, <ul>, or <li>. Use Heading, Text, Image, Link, Button, Badge, and Table.

Raw structural elements are allowed only when they have data-layout or data-layout-area and that layout name exists in src/layout.css.