dualdecklisted

# Dualdeck One HTML file. Two modes. **No build step, no CDN, no assets** — it opens from a `file://` path and still works after being emailed. Skill instructions are English; **all user-facing output stays Korean** unless the user asks otherwise. The point is not decoration. A document that must be *read closely* and a document that must be *projected* usually get written twice and drift apart. Dualdeck makes them the same file, so the numbers can't disagree. --- ## Start here — do not author from scratch Copy [`examples/dualdeck/shell.html`](../../../../examples/dualdeck/shell.html) and fill it in. It already contains the mode toggle, 8 palettes, PDF export, shortcuts, the 16:9 stage, and the component CSS. **Reimplementing any of that by hand is the failure mode this skill exists to prevent.** ``` examples/dualdeck/shell.html → <제목>.html ``` Then: replace `<title>`, the `<header>` block, and the demo `<section>`s. Touch nothing else. 섹션 구성이 안 잡히면 [`examples/dualdeck/PATTERNS.md`](../../../../examples/dualdeck/PATTERNS.md) — 비교 리포트 · 기술 설명 자료 · 측정 보고 세 유형의 섹션 순서와, 각 유형에서 자주 망가지는 지점이 적혀 있다. **셸을 유형별로 복제하지 마라** — 팔레트 엔진이 N벌이 된다. --- ## The one structural rule ```html <section data-sec="03 · 짧은라벨"> <!-- 리포트: 구획 · 프레젠테이션: 슬라이드 그룹 --> <div class="sl"><div class="sl-in"> <!-- .sl 하나 = 슬라이드 하나 --> ...내용... </div></div> </section> ``` - `data-sec` is the deck's corner label. Keep it under ~12 characters. - **One `.sl` = one slide.** A section with three