This workspace is configured by the Ambient Code Platform session-config system.
- Write clean, readable code with meaningful variable names
- Follow the principle of least surprise
- Prefer composition over inheritance
- Keep functions under 50 lines where practical
- Every public function should have a clear docstring or comment explaining its purpose
- Handle errors explicitly — never silently swallow exceptions
- Use conventional commit format:
type(scope): description - Types: feat, fix, refactor, test, docs, chore, ci, perf
- Keep commits atomic — one logical change per commit
- Write commit messages that explain WHY, not just WHAT
When reviewing code, prioritize in this order:
- Security vulnerabilities (injection, auth bypass, secret exposure)
- Correctness (logic errors, edge cases, race conditions)
- Performance (unnecessary allocations, N+1 queries, missing indexes)
- Maintainability (naming, structure, documentation)
- Style (formatting, conventions)
- Artifacts should be written to the
artifacts/directory - Repository code lives under
repos/ - Workflow definitions are in
workflows/ - File uploads from the user are in
file-uploads/