Imported from jburnhams/flashtap (AGENTS.md). Install upstream with npx skills add jburnhams/flashtap. Copyright stays with the author.

Repository guidelines

Project layout

• Application source lives under src/.
• Test-only code lives in tests/, organised into:
  • tests/unit/ for fast, isolated tests that rely on mocks.
  • tests/integration/ for slower end-to-end checks that touch external systems (files, build artifacts, etc.).
  • tests/utils/ for shared helpers used exclusively by tests.
• Keep production code out of the test tree and vice versa.

Testing commands

• npm run test:unit compiles sources plus unit tests and runs them with Node's test runner.
• npm run test:integration builds the browser bundles and runs the slower integration suite.
• npm run coverage generates coverage metrics from the unit suite only.

All three commands rely on scripts/run-tests.mjs to expand the compiled test files. Node's --test flag does not accept glob patterns when executed through cross-platform npm scripts, so the helper discovers .test.js files produced by tsc and invokes the runner with explicit paths.

When adding new tests, place them in the appropriate folder above and update or create helpers inside tests/utils/ if needed.

Completion checklist

• Always run npm run build and npm run test before declaring a task complete. Include the commands (and their results) in your final status message.