From 2663fe7f7b7eb438dc295fe9dea221aa8b8b8f81 Mon Sep 17 00:00:00 2001 From: Adam Malczewski Date: Sun, 7 Jun 2026 14:07:12 +0900 Subject: docs(harness): add frontend-styling rule + parallel-build verify caveat - add .dispatch/rules/frontend-styling.md (DaisyUI v5 + dracula; thin components) - package-agent: verify section explains whole-project svelte-check under parallel builds (judge only YOUR files) --- .dispatch/package-agent.md | 8 ++++++-- .dispatch/rules/frontend-styling.md | 12 ++++++++++++ 2 files changed, 18 insertions(+), 2 deletions(-) create mode 100644 .dispatch/rules/frontend-styling.md diff --git a/.dispatch/package-agent.md b/.dispatch/package-agent.md index c98b326..73e960c 100644 --- a/.dispatch/package-agent.md +++ b/.dispatch/package-agent.md @@ -61,8 +61,12 @@ the read — STOP and write the need in your report, then end. - **Strict TS:** respect `exactOptionalPropertyTypes` + `noUncheckedIndexedAccess`. ## Verify before finishing — YOUR UNIT IN ISOLATION -Run, and paste the output into your report: -- `bunx svelte-check --tsconfig ./tsconfig.json` → 0 errors +Sibling units may be built IN PARALLEL, so do NOT judge yourself by the whole project. +`svelte-check` is whole-project: if it reports errors in files OUTSIDE your unit's directory, +that is concurrent work-in-progress — IGNORE it and ensure only YOUR files (plus any existing +consumer you must not break) are error-free. The SCOPED checks below are your authoritative +signals. Run them, and paste the output into your report: +- `bunx svelte-check --tsconfig ./tsconfig.json` → 0 errors in YOUR files - `bunx vitest run src/` → all pass (count goes up) - `bunx biome check src/` → clean The orchestrator runs the authoritative full `typecheck`/`test`/`check`/`build`. diff --git a/.dispatch/rules/frontend-styling.md b/.dispatch/rules/frontend-styling.md new file mode 100644 index 0000000..e123619 --- /dev/null +++ b/.dispatch/rules/frontend-styling.md @@ -0,0 +1,12 @@ +# Rule: styling is DaisyUI v5 + the dracula theme (UI units only) + +The global stylesheet already enables **DaisyUI v5** with the **dracula** theme +(`data-theme` on ``). Do NOT add or change theme config, re-import Tailwind/DaisyUI, +or hand-roll a design system — just apply DaisyUI / Tailwind utility classes in your +`.svelte` files (e.g. `select`, `textarea`, `btn btn-primary`, `tabs`, `chat chat-start` / +`chat-end` + `chat-bubble`). + +Keep components THIN: a `.svelte` file wires props/events to pure logic and applies classes +— it holds NO business logic (that stays in `logic/` / the reducer). Render plain semantic +HTML decorated with classes. biome lints `.ts`/`.js` only; `.svelte` correctness is +`svelte-check`'s job. -- cgit v1.2.3