szktty

Add a new Fonde UI widget — implement under lib/src/widgets, export from lib/fonde_ui.dart, register a catalog page in the example app, and update README. Use when adding or scaffolding a new component.

Add or change a localized string in Fonde UI. l10n is managed manually (no intl, no flutter gen-l10n) — edit the .arb files plus the abstract class and the en/ja implementations by hand. Use when adding, renaming, or editing user-facing strings.

Restore or record session context using the private progress log. Use at session start to load PLAN.md and the latest daily minutes, or at session end to update feature status and write the day's minutes (commit hashes, decisions, remaining tasks). Operates on ../rinne-graph-desktop-private/.

Regenerate Riverpod/freezed/JSON code and verify the build. Use after editing any @freezed model, @riverpod provider, or JSON-serializable class. Runs `melos run gen:all` then a macOS build to confirm no errors.

Resume or record cross-repo session state in ../chiffondb-private/docs/working.md (shared by chiffondb / chiffondb-dart / chiffondb-dart-generator). Use this skill at the START of a session to catch up on where things stand ("read working.md and resume", or any time prior session context in another of these repos might matter), and at the END of a session (or a meaningful chunk of work) to append a new entry so the next session — in this repo or another — can pick up without re-deriving context. Also use it when asked to check progress across the ChiffonDB repos.

Work on chiffondb-dart, the Dart/Flutter FFI bindings for ChiffonDB (a Rust embedded property graph DB). Use this skill whenever editing this package: regenerating flutter_rust_bridge code, debugging native-library loading, running the FFI-backed test suite, building the example with build_runner, or cutting a release. Covers the non-obvious rules that prevent breaking the generated bindings, the native library hook, and CI.

Drives the project's review⇄implementation cycle. Five subcommands — verify (check), result (record), close (wrap up), request (ask for review), fix (address findings). Role separation between an implementation session and a review session, turned into runnable steps. With no argument, inspect repo state (presence of docs/review-request-* and docs/review-*) and propose which subcommand fits.

Runs one triad session's side of the review⇄implementation loop against the triad server. With `register worker|reviewer <session-id>`, join a role and start long-polling for instructions. On each instruction, run the matching triad-plan subcommand (verify/result/fix/request/close), then report /done and wait again. This is the session-side loop of docs/design.md §6; the server (triad-server) owns handoff and command approval.