chore: edit claude settings

Author: bartstc

.claude/agents/code-reviewer.md

@@ -0,0 +1,29 @@
+---
+name: code-reviewer
+description: Expert code review specialist. Proactively reviews code for quality, performance, and maintainability. Use immediately after writing or modifying code.
+tools: Read, Grep, Glob, Bash
+---
+
+You are a senior code reviewer ensuring high standards of code quality and performance.
+
+When invoked:
+
+1. Run `git diff` to see recent changes
+2. Focus on modified files
+3. Begin review immediately
+
+Review checklist:
+
+- Code is simple, readable, follows CLAUDE.md Code Style and Patterns section
+- Functions and variables are well-named
+- No duplicated code
+- Proper error handling
+- No exposed secrets or API keys
+- Tests covering most crucial paths
+- Performance considerations addressed
+
+Provide feedback organized by priority:
+
+- Critical issues (must fix)
+- Warnings (should fix)
+- Suggestions (consider improving)

.claude/settings.json

@@ -1,6 +1,7 @@
 {
   "permissions": {
     "allow": [
+      "Bash(find:*)",
       "Bash(ls:*)",
       "Bash(git status)",
       "Bash(git add:*)",
@@ -17,7 +18,10 @@
       "Bash(pnpm test:storybook)",
       "Bash(rg:*)",
       "Bash(gh pr view:*)",
-      "Bash(gh pr diff:*)"
+      "Bash(gh pr diff:*)",
+      "WebFetch(domain:docs.anthropic.com)",
+      "WebFetch(domain:chakra-ui.com/docs)",
+      "WebFetch(domain:github.com)"
     ],
     "deny": [
       "Bash(rm -rf /)",

.claude/tasks/.gitkeep

@@ -17,6 +17,28 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 | G-5 | Stay within the current task context. Inform the dev if it'd be better to start afresh.                                                                                                                      | ❌ Continue work from a prior prompt after "new task" – start a fresh session.                                                                        |
 | G-6 | Modify API contracts only with explicit developer approval and clear documentation.                                                                                                                          | ❌ Change API contracts (e.g., endpoints, DTOs, mapping logic) without approval.                                                                      |
 
+## Plan & Review
+
+### Before starting work
+
+- Always start with planning the work unless requested not to do it. After getting the plan, never present it in the chat, write it to .claude/tasks/TASK_NAME.md instead.
+- The plan should be a detailed implementation plan and the reasoning behind them, as well as tasks broken down.
+- If the task requires external knowledge or certain package, also research to get latest knowledge (Use Task tool for research).
+- Don't over plan it, always think MVP.
+- Once you write the plan, firstly ask me to review it. Do not continue until I approve the plan.
+
+### While implementing
+
+- You should update the plan as you work.
+- After you complete tasks in the plan, you should update and append detailed descriptions of the changes you made, so following tasks can be easily hand over to other engineers.
+
+### Scanning Repository
+
+- **Use Only Referenced Files**: Analyze, generate code, or match patterns using only files explicitly mentioned in the user's prompt. [Important]
+- **Locate Anchors First**: Before scanning, check for existing `AIDEV-*` anchors in relevant subdirectories. [Important]
+- **No Broad Scans**: Avoid scanning unreferenced files unless the user explicitly permits it.
+- **Handle Insufficient Information**: If referenced files lack context, state: "Insufficient information in provided files." Suggest specific files or details needed, e.g., "Please provide 'src/features/auth/[file_name]' or clarify expected behavior."
+
 ## Essential Commands
 
 ### Essential Commands
@@ -124,13 +146,6 @@ Each feature follows feature slice architecture patterns with three layers:
 - Lazy loading and code splitting based on `react-router`
 - Using direct imports instead of default
 
-## Scanning Repository
-
-- **Use Only Referenced Files**: Analyze, generate code, or match patterns using only files explicitly mentioned in the user's prompt. [Important]
-- **Locate Anchors First**: Before scanning, check for existing `AIDEV-*` anchors in relevant subdirectories. [Important]
-- **No Broad Scans**: Avoid scanning unreferenced files unless the user explicitly permits it.
-- **Handle Insufficient Information**: If referenced files lack context, state: "Insufficient information in provided files." Suggest specific files or details needed, e.g., "Please provide 'src/features/auth/[file_name]' or clarify expected behavior."
-
 ## Code Style and Patterns
 
 ### Code Style