---
name: laflabs-web-design
description: Apply LafLabs public web branding when creating or modifying LafLabs websites and branded web surfaces. Do not use for backend-only work, unrelated third-party products, or dense Admin workflows unless the user explicitly requests the public brand.
---

# LafLabs Web Design

Use the LafLabs public design language without inventing product facts, assets, or component availability.

## Essential constraints

- Preserve official assets, Paper and Ink surfaces, Primary Blue as the sole accent, square geometry, and visible one-pixel rules.
- Keep Korean and English content equivalent, with natural line breaks in both locales.
- Reuse installed LafLabs components when their contracts fit; do not imitate them with lookalikes.
- Keep every action keyboard-accessible, visibly focused, and understandable without color alone.
- Honor reduced motion and show a complete static state.
- Publish only verified claims. Omit or mark unavailable anything the target repository cannot support.

## Workflow

1. Inspect the target repository, its real components, official assets, and factual product content.
2. Read only the references relevant to the requested work.
3. Choose a published Recipe before composing a common documented task; preserve its declared component semantics and task order.
4. Reuse supported components and tokens when available; preserve the target repository's established architecture.
5. Verify desktop and mobile layout, visible copy, keyboard access, focus, and reduced motion before completion.

## References

- Read [references/foundations.md](references/foundations.md) for identity, color, typography, layout, accessibility, motion, voice, and claims.
- Read [references/components.md](references/components.md) when selecting or using LafLabs interface components.
- Read [references/patterns.md](references/patterns.md) when composing page sections or responsive structures.
- Read [references/tokens.json](references/tokens.json) when exact semantic values are required.