Start from the canonical docs
Read the Developer Guide, Architecture, API reference, and affected package README before editing.
Contribute without getting lost.
FlintTrade spans Python services, a React terminal, Rust tick processing, an evidence-gated native broker gateway whose HTTP surfaces are frozen until Task 9D and Task 7C.2, and a desktop shell. The public docs and MCP tools are designed to get contributors to the right package, tests, and context quickly.
Run focused checks first
Use package-specific pytest, terminal Vitest/typecheck, or the site build before broader Makefile checks.
Open a small PR
Use Conventional Commits, list tests run, update docs when behaviour changes, and include screenshots for UI work.
python scripts/ft.py setup python scripts/ft.py test python scripts/ft.py lint
The cross-platform runner needs no make and no bash, so these lines behave identically in Windows PowerShell, bash and zsh. On POSIX, make setup, make test and make lint are the aliases; make test-fast stops at the first failure.
cd packages/apps/terminal npm run typecheck cd packages/apps/site npm run build
Windows PowerShell has no && chaining, so the directory change and the command it feeds are listed separately rather than joined.