-
Notifications
You must be signed in to change notification settings - Fork 0
Development Guide
OpenClaw edited this page Feb 15, 2026
·
1 revision
- Read
AGENTS.mdin repo root — non-negotiable - Check
CHANGELOG.mdfor recent changes - Run
git log --oneline -10to understand current state - Check
docs/sprints/for current sprint goals
-
TypeScript strict — no
any, no@ts-ignore - Max 300 lines per file — split into modules if larger
-
Conventional commits —
feat:,fix:,docs:,test:,refactor:,chore: - All exports must be typed — no implicit any returns
- Error handling everywhere — try/catch with meaningful errors
- No console.log in production — use structured logging
For every new file:
- Under 300 lines
- Has corresponding test file
- Exports are typed
- Has JSDoc for public functions
- Error handling for async operations
- Loading states for UI components
- Create sprint branch:
sprint/YYYY-MM-DD-description - Implement features with tests
- Ensure 100% test coverage
- Run full test suite
- Update CHANGELOG.md
- Squash merge to main
- Update wiki Sprint Log
- Tag release if significant
# Build and run dev container
docker compose up dev --build
# Build and run staging
docker compose up staging --build
# Run tests against container
npm run test:e2e
# Promote dev to staging (after tests pass)
docker compose down staging
docker compose up staging --build- Branch:
sprint/YYYY-MM-DD-short-description - Commits: conventional format, frequent, atomic
- Main: always deployable
- Tags:
v0.X.0for sprint completions
Every 30 minutes:
- Check Claude Code session status
- If running: note progress, no intervention
- If finished: analyze output, plan next sprint
- If failed: diagnose, restart with fix
After each sprint:
- Review what was built
- Check test coverage
- Identify gaps and issues
- Plan next sprint (1-3 focused features)
- Update wiki Sprint Log
- Create GitHub issues for known problems
Only when:
- Need credentials or external access
- Usage approaching 80%
- Sprint completed with demo-ready features
- Daily report
- Writes application code
- Implements features
- Fixes bugs
- Refactors for quality
- Writes Playwright E2E tests
- Writes Vitest unit tests
- Researches MCPs and tools
- Web research for best practices
- Sprint planning and prioritization
- Progress monitoring (heartbeats)
- Quality gate (reviews before merge)
- Communication with Ciprian
- Wiki and documentation maintenance
- GitHub issues management