go run ./cmd/unic
go test ./...
make buildUse branch-naming-harness.md for branch names.
Preferred format:
<work-type>/<issue-number>-<short-description>
Always start repository work from main in a fresh git worktree.
- Fetch or verify the intended
mainbase. - Create a new worktree and task branch from
mainororigin/main. - Make all edits for that task inside the new worktree.
- Keep one worktree per issue, feature, refactor, or PR-sized change.
Do not implement new work directly in the primary checkout or on an existing
feature branch. If a task appears to depend on another unmerged branch, still
start from main first and document the dependency before applying any stacked
changes.
- Add service or feature constants in
internal/domain/model.go - Register the feature in
internal/domain/catalog.go - Add AWS repository methods and UI-facing models in
internal/services/aws/ - Wire new state and screen transitions in
internal/app/ - Add tests for repository behavior and screen transitions
- Update documentation when behavior is user-visible
If you change:
- a user-facing command
- auth/config behavior
- supported AWS services/features
- screen structure or navigation
then update at least:
README.md- the relevant file in
docs/
Use documentation-harness.md as the required checklist for deciding which docs must move with the implementation.
Prefer tests for:
- repository methods with mocked AWS clients
- config and auth helpers
- TUI transition logic when a feature adds or changes a flow
- context add/setup flows when auth types or auth-specific branches change
README.md: concise user-facing entrypointdocs/: canonical detailed documentation.kiro/: internal compatibility pointers and steering helpers