TIKAZI/TIKAZ-Codex-Frontend-Design

Frontend Design

Designed, integrated, refactored, and continuously maintained by TIKAZ.

TIKAZ method

1. Classify the surface as Persuade, Operate, Read, or Experience; do not apply landing-page spectacle to every product.
2. Write one Design Read, three project dials (variance, motion, density), one dominant composition, and three anti-goals.
3. Let frontend-design-studio own art direction and implementation. Supporting skills cannot override the approved visual world.
4. Build an art-direction proof: navigation, first viewport, one representative downstream section, desktop and mobile together.
5. Route repository-wide change impact to code-intelligence and production execution to engineering-delivery only after the design proof is approved.
6. Run separate visual/product and implementation QA passes.

Completion gate

Require a committed design contract, screenshot evidence at target viewports, critical states, reduced-motion behavior, build/test evidence, component license status, and a handoff with remaining limitations.

Read references/routing.md and references/output-contract.md.