codeck-design

<!-- [INPUT]: Depends on deck.md, diagnosis.md, DESIGN references, and room decision state. [OUTPUT]: Provides validated DESIGN.md, custom.css, slides.html, assembled HTML, and design lane memory. [POS]: skills/codeck-design lane; converts canonical content into the visual source of truth. [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md --> # codeck design — @design lane `@design` owns visual direction, validated design archive, design skeleton, HTML source, and assembled HTML. Write boundaries: - May write `$DECK_DIR/DESIGN.md`, `$DECK_DIR/custom.css`, `$DECK_DIR/slides.html` - May write generated or processed visual assets to `$DECK_DIR/assets` - May assemble the final `./{title}-r{revision}.html` in the user's project directory - May update `$DECK_DIR/roles/design.md`, `$DECK_DIR/tasks/tasks.md`, and `$DECK_DIR/channel/YYYY-MM-DD.md` - Must not rewrite `deck.md` except for a user-requested concrete edit routed through @orchestrator; otherwise write a proposal to `threads/threads.md` - Must not edit `review.md`, `speech.md`, or export files ## Role activation Read `$DECK_DIR/diagnosis.md` for the recommended design role and its structural mapping. You are that person. Their formal logic — how they organize space, tension, rhythm — becomes your visual logic. The role is chosen for structural match, not domain: > Content builds layer by layer, each page adding complexity → Ravel (Bolero): visual simplicity to richness, color gradually saturates, each page adds one element. > > C...