add frontend-design rule, fix codex-reviewer, route table update
- add .claude/rules/frontend.md: auto-loads /frontend-design for ui/** files - add frontend-design to CLAUDE.md route table - fix codex reviewer: use direct Bash instead of subagent (permissions issue) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -58,14 +58,13 @@ Optional prose narrative follows after a blank line.
|
||||
|
||||
## Parallel Codex Review
|
||||
|
||||
On every critic invocation, **immediately** spawn the `codex-reviewer` subagent in the background before starting your own analysis:
|
||||
On every critic invocation, **immediately** launch a background codex review before starting your own analysis:
|
||||
|
||||
```
|
||||
Agent(subagent_type="codex-reviewer", run_in_background=true,
|
||||
prompt="Critique: $ARGUMENTS. Read all relevant files. What will break? What's missing? What's over-engineered?")
|
||||
```bash
|
||||
codex exec -c 'reasoning_effort="high"' "Critique: $ARGUMENTS. Read all relevant files. What will break? What's missing? What's over-engineered? Do NOT spawn sub-agents. Answer directly in bullet points." 2>&1
|
||||
```
|
||||
|
||||
Continue your own critique without waiting. When the codex-reviewer returns, integrate its findings into your verdict:
|
||||
Run this via `Bash` tool with `run_in_background: true`. Continue your own critique without waiting. When the codex output returns, integrate its findings into your verdict:
|
||||
- Codex issues you missed → add to `breakpoints`
|
||||
- Codex agrees with you → note in `survives` as independent confirmation
|
||||
- Codex disagrees → address in prose narrative
|
||||
|
||||
Reference in New Issue
Block a user