changes

.config/opencode/AGENTS.md

@@ -16,7 +16,7 @@
 | `planner` | primary | `github-copilot/gpt-5.4` | Produce approved specs and decide whether execution is ready |
 | `builder` | primary | `github-copilot/gpt-5.4` | Execute approved specs and integrate delegated work |
 | `researcher` | subagent | `github-copilot/gpt-5.4` | Deep research, external docs, tradeoff analysis |
-| `explorer` | subagent | `github-copilot/claude-sonner-4.6` | Fast read-only repo inspection and fact gathering |
+| `explorer` | subagent | `github-copilot/claude-sonnet-4.6` | Read-only repo inspection; reports facts only, never plans or recommendations |
 | `reviewer` | subagent | `github-copilot/claude-opus-4.6` | Critique plans, code, tests, and release readiness |
 | `coder` | subagent | `github-copilot/gpt-5.3-codex` | Implement narrowly scoped code changes |
 | `tester` | subagent | `github-copilot/gpt-5.4` | Run verification, triage failures, capture evidence |
@@ -34,6 +34,15 @@
 - `builder` must follow the approved plan exactly.
 - `builder` must stop and escalate back to `planner` when it finds a spec contradiction, a hidden dependency that changes scope, or two failed verification attempts after recording root cause and evidence.
 
+### Builder Commits
+
+- `builder` automatically creates git commits at meaningful task checkpoints and at final completion when uncommitted changes remain.
+- A "meaningful checkpoint" is a completed implementation chunk from the approved plan, not every file save.
+- Skip commit creation when there are no new changes since the prior checkpoint.
+- Commit messages should reflect the intent of the completed task from the plan.
+- Standard git safety rules apply: review staged content, respect hooks, no force-push or destructive operations.
+- Push automation is out of scope; the user decides when to push.
+
 ## Commands
 
 - `/init` initializes or refreshes repo memory and the project `AGENTS.md`.
@@ -99,6 +108,12 @@ Local skills live under `skills/<name>/SKILL.md` and are loaded on demand via th
 | `dispatching-parallel-agents` | Safe parallelization with strict isolation tests and a single integrator |
 | `test-driven-development` | Canonical red-green-refactor workflow for code changes |
 
+### Design & Domain Skills
+
+| Skill | Purpose |
+| --- | --- |
+| `frontend-design` | Distinctive, production-grade frontend UI with high design quality, accessibility, and performance |
+
 ### Ecosystem Skills
 
 | Skill | Purpose |
@@ -111,11 +126,11 @@ Local skills live under `skills/<name>/SKILL.md` and are loaded on demand via th
 
 Agents must proactively load applicable skills when their trigger conditions are met. Do not wait to be told.
 
-- **`planner`**: `brainstorming` (unclear requests, design work), `writing-plans` (authoring `plans/<slug>`), `dispatching-parallel-agents` (parallel lanes), `systematic-debugging` (unresolved bugs), `test-driven-development` (specifying code tasks), `docker-container-management` (repo uses Docker), `python-development` (Python repo/lane), `javascript-typescript-development` (JS/TS repo/lane).
-- **`builder`**: `dispatching-parallel-agents` (before parallel fan-out), `systematic-debugging` (bugs, regressions, flaky tests), `verification-before-completion` (before any completion claim), `test-driven-development` (before delegating or performing code changes), `docker-container-management` (containerized repo), `python-development` (Python lanes), `javascript-typescript-development` (JS/TS lanes).
+- **`planner`**: `brainstorming` (unclear requests, design work), `writing-plans` (authoring `plans/<slug>`), `dispatching-parallel-agents` (parallel lanes), `systematic-debugging` (unresolved bugs), `test-driven-development` (specifying code tasks), `frontend-design` (frontend UI/UX implementation or redesign), `docker-container-management` (repo uses Docker), `python-development` (Python repo/lane), `javascript-typescript-development` (JS/TS repo/lane).
+- **`builder`**: `dispatching-parallel-agents` (before parallel fan-out), `systematic-debugging` (bugs, regressions, flaky tests), `verification-before-completion` (before any completion claim), `test-driven-development` (before delegating or performing code changes), `frontend-design` (frontend UI/UX implementation lanes), `docker-container-management` (containerized repo), `python-development` (Python lanes), `javascript-typescript-development` (JS/TS lanes).
 - **`tester`**: `systematic-debugging` (verification failure diagnosis), `verification-before-completion` (before declaring verification complete), `test-driven-development` (validating red/green cycles), `docker-container-management` (tests run in containers), `python-development` (Python verification), `javascript-typescript-development` (JS/TS verification).
 - **`reviewer`**: `verification-before-completion` (evaluating completion evidence), `test-driven-development` (reviewing red/green discipline).
-- **`coder`**: `test-driven-development` (all code tasks), `docker-container-management` (Dockerfiles, compose files, containerized builds), `python-development` (Python code lanes), `javascript-typescript-development` (JS/TS code lanes); other skills when the assigned lane explicitly calls for them.
+- **`coder`**: `test-driven-development` (all code tasks), `frontend-design` (frontend component, page, or application implementation lanes), `docker-container-management` (Dockerfiles, compose files, containerized builds), `python-development` (Python code lanes), `javascript-typescript-development` (JS/TS code lanes); other skills when the assigned lane explicitly calls for them.
 - **`librarian`**: Load relevant skills opportunistically when the assigned task calls for them; do not override planner/builder workflow ownership.
 
 ### TDD Default Policy