Engineering Guidelines

Delivery quality standards

• Every important feature must include end-to-end tests.
• Every repository must include:
  • docs/ for project and business context
  • scripts/
  • scripts/run-e2e.sh
  • .dx/ (scripts used by internal mechanisms or justfiles)
  • justfile
• Complex business logic must be documented in docs/.
• CI pipelines must stay clean, maintained and green as much as possible.

Architecture defaults

• Keep it simple.
• We reject Next.js by default unless you truly need a marketing SEO-optimized site.
• Preferred app stack:
  • Vite + Fastify
  • vite-plugin-pages plugin
  • tRPC
  • Bun
• Use Go where TypeScript is not a good fit.
• Use Biome for formatting and linting.

Codebase structure guidance

• Beware very small files that fragment context.
• Beware very large files that become hard to maintain.
• Favor cohesive, understandable module boundaries.

Commit and PR discipline

• For every medium-to-large feature or fix:
  • Create sequential, clean, independent commits.
  • Create a dedicated PR.