dioxus-token-list-project

# dioxus-token-list Project Use this skill for repository-specific execution context. Follow `AGENTS.md` and `.codex/rules/dioxus-0.7-workflow.md` first for Dioxus 0.7 rules. ## Start Here 1. Confirm the current directory is `D:\Documents\Projects\VC\Rust\dioxus-token-list`. 2. Read `.codex/rules/dioxus-0.7-workflow.md` for Dioxus implementation work. 3. Read the files directly involved in the request before editing. 4. Keep web and desktop support intact unless the request is explicitly platform-specific. 5. Prefer the existing `packages/ui`, `packages/web`, and `packages/desktop` boundaries. 6. Use the project scripts before inventing new commands. ## Workspace Map | Path | Use | | ---- | --- | | `packages/ui/src/client/app.rs` | Shared app shell entry component. | | `packages/ui/src/client/components` | Shared Dioxus components. | | `packages/ui/src/client/pages` | Routed pages. | | `packages/ui/src/client/services` | Client token orchestration, storage, localization, online data, and database services. | | `packages/ui/src/server/services` | Optional server functions that can fail gracefully on static hosting. | | `packages/ui/assets` | Shared CSS and token images. | | `packages/web/src/main.rs` | Web entrypoint. | | `packages/desktop/src/main.rs` | Desktop entrypoint. | | `Scripts` | Windows PowerShell setup and run workflows. | ## Dioxus 0.7 Constraints - Use `dioxus = "0.7.1"` patterns. - Do not use `cx`, `Scope`, or `use_state`. - Use `#[component] fn Name(...) -> Element`. - Use `use_signal`, `use_memo`, `use_resource`, and signal `.read()`, `.write()`, `.with_mut()`, or call syntax. - Use `Router::<Route> {}` and `Outlet<Route> {}` for routing. - Use `asset!("/path/from/project/root")` for local assets. - Keep props owned, `Clone`, and `PartialEq`. ## Cache And Loading Behavior - Preserve visible loading affordances during online fetches, cache reads, database writes, and repopulation. - Avoid feedback loops from reactive reads inside cache-write paths; use non-subscribing reads such as `peek()` when the codebase already follows that pattern. - Browser builds currently use localStorage token snapshots instead of browser SQLite. Prefer rendering from snapshot or online data first, then persisting native SQLite in non-wasm builds when available. - Treat stale dev servers as a common source of false browser results. ## Verification Use the narrowest check that proves the change: ```powershell cargo check -p ui --target wasm32-unknown-unknown cargo check -p web --target wasm32-unknown-unknown cargo check -p desktop .\Scripts\Common\RunWeb.ps1 .\Scripts\Common\RunDesktop.ps1 .\Scripts\Other\RunTests.ps1 ``` For browser UI, routing, asset, or cache changes, serve the web app and inspect the actual page when practical. The default web target is: ```powershell dx serve --platform web --addr <this-laptop-ipv4> --port 8080 ``` For fullstack web testing on Windows, use a concrete local IPv4 address instead of `0.0.0.0`; the wildcard address can make backend readiness fail with `os error 10049`. If `8080` is occupied by a stale server, stop that server and restart the project server. ## Response Style Report the changed files, the verification command or browser check used, and any remaining risk. Keep the answer concise and concrete.