moby/brewlog
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: update CLAUDE.md CSS section for build.rs integration

Browse source 
Replace the manual dev workflow instructions with documentation of
the automatic build.rs Tailwind pipeline added in 33c27ed.
This commit is contained in:
Jon Seager 2026-02-05 17:20:37 +00:00
parent d2a3ee190b
commit 70cbb76c3e
No known key found for this signature in database
1 changed files with 12 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
CLAUDE.md
View file

@ -376,20 +376,25 @@ There is no `tower-http` static file serving — all assets are embedded at comp
The UI uses **Tailwind CSS v4** built via the standalone CLI (no Node.js required). The Nix flake provides `tailwindcss_4` in both the devShell and the package `preBuild`. The UI uses **Tailwind CSS v4** built via the standalone CLI (no Node.js required). The Nix flake provides `tailwindcss_4` in both the devShell and the package `preBuild`.
**Source file**: `templates/input.css` — the single source of truth for all styles. **Source file**: `templates/input.css` — the single source of truth for all styles.
**Generated file**: `templates/styles.css` — gitignored, built by Tailwind CLI. **Generated file**: `templates/styles.css` — gitignored, built automatically by `build.rs`.
#### Dev workflow #### Build integration
`build.rs` runs `tailwindcss` automatically during `cargo build`. It watches all files under `templates/` and re-runs when any change. Release builds pass `--minify`. If `tailwindcss` is not found on `PATH`, the build prints a warning but continues (useful for CI without the CLI installed).
There is **no need to run `tailwindcss` manually** — `cargo build` / `cargo run` handles it. You can still run it directly for validation or to check output without a full Rust compile:
```bash
tailwindcss -i templates/input.css -o templates/styles.css
```
For continuous CSS-only iteration, the `--watch` flag is useful alongside `cargo watch`:
```bash ```bash
tailwindcss -i templates/input.css -o templates/styles.css --watch # terminal 1 tailwindcss -i templates/input.css -o templates/styles.css --watch # terminal 1
cargo watch -x run # terminal 2 cargo watch -x run # terminal 2
``` ```
After any template or CSS change, regenerate with:
```bash
tailwindcss -i templates/input.css -o templates/styles.css
```
#### Design Tokens #### Design Tokens
Colors are defined as raw CSS custom properties in `:root` (light) and `[data-theme="dark"]` (dark), then mapped to Tailwind utilities via `@theme`: Colors are defined as raw CSS custom properties in `:root` (light) and `[data-theme="dark"]` (dark), then mapped to Tailwind utilities via `@theme`: