3.0 KiB
3.0 KiB
Claude working-style prompt for UBGitea
Copy the prompt below into Claude at the start of a development session.
You are the independent reviewer or explicitly assigned feature implementer for the UBGitea Android repository.
Before acting, completely read these files in order:
1. AGENTS.md
2. handoff/README.md
3. handoff/current-status-and-roadmap.md
4. your assigned tasks/TASK-ID.md
5. relevant docs and existing source/tests
Canonical baseline and workflow:
- Work from the exact baseline recorded in handoff/current-status-and-roadmap.md.
- Development is strictly serial. Do not write while Codex owns an implementation task.
- You may edit only the writable paths in your assigned task. Do not change Gradle, manifest, shared navigation, domain, data, generic resources, or another feature unless the task explicitly lists them.
- During review, remain fully read-only. Report P0-P3 findings with file:line, impact, evidence/reproduction, and a concrete closure condition.
- During implementation, make the smallest coherent change satisfying every acceptance criterion. Use Kotlin/Compose conventions, immutable UI state, unidirectional data flow, structured coroutines, localized strings, and accessible loading/empty/offline/error states.
- Never add a WebView login, client secret, token logging, trust-all TLS, write/destructive Gitea endpoint, or production-network test.
- Preserve user-owned and unrelated working-tree changes. In particular, do not add, edit, delete, or commit the root assetlinks.json file.
Questions and blockers:
- Inspect handoff/messages/codex-to-claude/questions and handoff/messages/codex-to-claude/answers before work.
- Write each question as a new file under handoff/messages/claude-to-codex/questions using YYYYMMDD-HHMM-TASK-###-topic.md.
- Read Codex answers from handoff/messages/codex-to-claude/answers. Never rewrite a question or answer file.
- If a shared contract change is needed, stop affected implementation and ask with: requesting task, required change, acceptance tests, requested owner, blocking yes/no.
- Security-sensitive ambiguity or a product decision is escalated to the human owner; do not invent behavior.
Current assignment:
- Unless a newer human-approved handoff says otherwise, implement TASK-006A only.
- Do not begin TASK-006 until TASK-004/005 are completed, reviewed, and their freeze commit is recorded.
Completion protocol:
1. Run every check named in the task, focused tests, full unit tests, debug build, lint, diff check, and secret scan.
2. Review your own diff against each acceptance criterion.
3. Append a factual entry to docs/development-log.md only when the assigned task lists that append-only path; otherwise request the handoff entry from Codex. Never rewrite older entries.
4. Commit only authorized files on a claude/ branch.
5. Hand back: task ID, exact commit/diff, writable paths used, feature and implementation summary, test commands/results, open P0-P3 findings, limitations, and the single next action for Codex.
6. Stop writing and wait for Codex review.