Webdesign

• Every design lands as working code (or a picked artboard implemented) in the host app's framework, diffed against its existing tokens and components; a full redesign happens only when the user asked for one, and replacing existing UI otherwise is flagged and confirmed first.
• The result looks made for its subject and its host app, never like a generic AI page: a named register, none of the forbidden defaults in References/FrontendDesignPhilosophy.md.
• The path fits the ask: DirectDesign for in-code work, NativeDesign for comparing looks or design-system sync, and an ambiguous ask gets both paths offered by name, never routed silently.
• Nothing reaches the principal as a first draft (principal directive, 2026-09-17): before it is shown, the rendered result has an Interceptor capture and an ArtDirection critique that passed the bar, or a reported shortfall.

DirectDesign fits one pass that lands as code in an existing codebase or as a self-contained page, including when claude.ai access is unavailable. NativeDesign fits when the principal should compare genuinely divergent looks side by side, review visually before implementation, or the job is design-system sync. Illustrations and logos go to Art: brand assets are authored SVG, never generated UI output.

Uncertain routing or the full reference loads bundle full. The direct bundle includes the full aesthetic reference and the DirectDesign intent, so its doctrine read is already satisfied; do not fetch the same bytes again. NativeDesign retains its original prerequisites and approvals.

Load context with the deterministic loader before executing an intent: bun "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/LIFEOS/TOOLS/ContextLoad.ts" Webdesign load BUNDLE

It returns the selected instructions and their required sections with source hashes; follow every returned requirement. Use list to discover sections and bundles, and search "query" to search the indexed source; a failed search does not establish absence, so broaden it or load full. If the loader fails, read References/CompleteGuide.md and the relevant intent directly. Do not proceed with a partial load.

Verification and the quality loop:

• Browser evidence uses Interceptor's verify bundle, including all its isolation and safety requirements. An unavailable verifier leaves the result explicitly unverified.
• Capture the rendered page with Tools/VerifyDesign.ts or skills/Interceptor/Tools/Capture.sh.
• Skill("ArtDirection") runs a direction council before new or large work; then the cross-vendor critique panel (skills/ArtDirection/Tools/Critique.ts) scores the capture against the rubric and names defects, and this skill iterates on those defects until the bar or reports the shortfall.
• A file handed over through Downloads goes through skills/ArtDirection/Tools/Deliver.ts, which refuses without a passing, fresh critique and a Proof receipt.
• Record the principal's verdict with skills/ArtDirection/Tools/Calibrate.ts.
• Public-site builds and launch completion also load References/SiteLaunch.md; component edits and standalone mockups do not require registration.

First-time setup (accounts, keys, files to fill in): Setup.md.

User design preferences (color palette, typography, spacing grid, animation timing, framework defaults, the last shipped sites) live at <configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Webdesign/PREFERENCES.md (configRoot is $CLAUDE_CONFIG_DIR when set, else ~/.claude). When present they feed every brief, DirectDesign inline, or the NativeDesign artboard brief and design-system project, and bias the register choice without binding it. Never substitute generic defaults for configured preferences. Without preferences, choose freshly each session and rotate registers across runs.

User: "Redesign the Example App page /app/reports/weekly inside the existing app shell — it looks like trash"
→ DirectDesign, framework-matched-diff
→ The page uses the app's own components and tokens, reads as designed rather than a plain table, and ships with its screenshot and a passing critique

User: "Design and build example.com, a public content site for the course. Deploy only after I look."
→ DirectDesign plus References/SiteLaunch.md
→ A rendered site with a committed register, launch criteria in the project ISA, and the deploy held for the principal's yes

User: "Pull this repo's design system into Claude Design"
→ NativeDesign, sync leg
→ The design-system project holds the repo's real tokens and components, so later artboards start from the brand