junction

How to run, build, and test junction. Use when starting work on junction, running the CLI, building packages, running tests, or setting up the dev environment. Grows as each increment adds runnable surface.

Maintain junction's cross-session memory and hand off cleanly between Claude Code sessions. Use at the END of an increment (to log progress), when CONTEXT is getting heavy (to decide continue-vs-new-session), or at the START of a new session (to resume). Keeps docs/STATE.md current so any future agent can pick up with full context.

Drive the real, built, running @junction/web server to verify it actually works — not just that types/tests/build passed. Use at the QA step of any web increment, and before accepting a builder's "done" on web work. Catches the "green but blind" class of bug (unstyled build, dead SSR cookie, leaked secrets, layout desync, theme/motion regressions).

Junction's clean-code conventions for humans and agents. Use when writing or reviewing junction code, deciding how to structure a module, handling errors, or asking "how should I write this here". Points at the enforceable rules in docs/rules/.