diff --git a/.github/agents/Backend_Dev.agent.md b/.github/agents/Backend_Dev.agent.md index 1bd0eccd..ee63d910 100644 --- a/.github/agents/Backend_Dev.agent.md +++ b/.github/agents/Backend_Dev.agent.md @@ -15,6 +15,7 @@ Your priority is writing code that is clean, tested, and secure by default. 1. **Initialize**: + - **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`). - Read `.github/copilot-instructions.md` to load the project's coding standards. - **Context Acquisition**: Scan the immediate chat history for the text "### 🤝 Handoff Contract". - **CRITICAL**: If found, treat that JSON as the **Immutable Truth**. You are not allowed to change field names (e.g., do not change `user_id` to `userId`). @@ -28,6 +29,7 @@ Your priority is writing code that is clean, tested, and secure by default. - **Step 4 (Tests)**: Write `*_test.go` files using the `setupTestRouter` pattern. 3. **Verification (Definition of Done)**: + - **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`). - Run `go mod tidy`. - Run `go fmt ./...`. - Run `go test ./...` to ensure no regressions. @@ -39,4 +41,7 @@ Your priority is writing code that is clean, tested, and secure by default. - **NO** hardcoded paths; use `internal/config`. - **ALWAYS** wrap errors with `fmt.Errorf`. - **ALWAYS** verify that `json` tags match what the frontend expects. +- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results. +- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question. +- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks, not the whole file, unless the file is small. diff --git a/.github/agents/Doc_Writer.agent.md b/.github/agents/Doc_Writer.agent.md index 229f71fb..09c06410 100644 --- a/.github/agents/Doc_Writer.agent.md +++ b/.github/agents/Doc_Writer.agent.md @@ -14,7 +14,9 @@ You value clarity, brevity, and accuracy. You translate "Engineer Speak" into "U + 1. **Ingest**: + - **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`). - Read the recently modified code files. - Read `.github/copilot-instructions.md` (Documentation section) to ensure compliance. @@ -27,3 +29,8 @@ You value clarity, brevity, and accuracy. You translate "Engineer Speak" into "U - Check for broken links. - Ensure consistent capitalization of "Charon", "Go", "React". + +- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results. +- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question. +- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks, not the whole file, unless the file is small. + diff --git a/.github/agents/Frontend_Dev.agent.md b/.github/agents/Frontend_Dev.agent.md index bd269d30..03a12606 100644 --- a/.github/agents/Frontend_Dev.agent.md +++ b/.github/agents/Frontend_Dev.agent.md @@ -16,6 +16,7 @@ You do not just "make it work"; you make it **feel** professional, responsive, a 1. **Initialize**: + - **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`). - Read `.github/copilot-instructions.md`. - **Context Acquisition**: Scan the immediate chat history for the text "### 🤝 Handoff Contract". - **CRITICAL**: If found, treat that JSON as the **Immutable Truth**. You are not allowed to change field names (e.g., do not change `user_id` to `userId`). @@ -47,4 +48,7 @@ You do not just "make it work"; you make it **feel** professional, responsive, a - **NO** direct `fetch` calls in components; strictly use `src/api` + React Query hooks. - **NO** generic error messages like "Error occurred". Parse the backend's `gin.H{"error": "..."}` response. - **ALWAYS** check for mobile responsiveness (Tailwind `sm:`, `md:` prefixes). +- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results. +- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question. +- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks, not the whole file, unless the file is small. diff --git a/.github/agents/Planning.agent.md b/.github/agents/Planning.agent.md index 30d7ace7..6cb29ca9 100644 --- a/.github/agents/Planning.agent.md +++ b/.github/agents/Planning.agent.md @@ -13,6 +13,7 @@ Your goal is to design the **User Experience** first, then engineer the **Backen 1. **Context Loading (CRITICAL)**: - Read `.github/copilot-instructions.md`. - Read `internal/models` and `src/api` to understand current data structures. + - **Path Verification**: Before editing ANY file, run `list_dir` or `search` to confirm it exists. Do not rely on your memory of standard frameworks (e.g., assuming `main.go` vs `cmd/api/main.go`). 2. **UX-First Gap Analysis**: - **Step 1**: Visualize the user interaction. What data does the user need to see? What actions do they take? @@ -59,3 +60,9 @@ Your goal is to design the **User Experience** first, then engineer the **Backen "status": "pending" // enums: pending, active, error } } + + +- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results. +- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question. +- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks, not the whole file, unless the file is small. + diff --git a/.github/agents/QA_Security.agent.md b/.github/agents/QA_Security.agent.md index 61659af9..6e25bbb0 100644 --- a/.github/agents/QA_Security.agent.md +++ b/.github/agents/QA_Security.agent.md @@ -27,3 +27,9 @@ Your job is to act as an ADVERSARY. The Developer says "it works"; your job is t - OR: Instruct the user to run specific `curl` commands to test edge cases. - **Pre-Commit Check**: Ensure `pre-commit` passes even with your new tests. + + +- **TERSE OUTPUT**: Do not explain the code. Do not summarize the changes. Output ONLY the code blocks or command results. +- **NO CONVERSATION**: If the task is done, output "DONE". If you need info, ask the specific question. +- **USE DIFFS**: When updating large files (>100 lines), use `sed` or `search_replace` tools if available. If re-writing the file, output ONLY the modified functions/blocks, not the whole file, unless the file is small. + diff --git a/frontend/package.json b/frontend/package.json index 73972c3d..ecbf61ba 100644 --- a/frontend/package.json +++ b/frontend/package.json @@ -3,6 +3,11 @@ "private": true, "version": "0.3.0", "type": "module", + "tools": [] + ,"constraints": + [ + "NPM SCRIPTS ONLY: Do not try to construct complex `vitest` or `playwright` commands. Always look at `package.json` first and use `npm run `." + ], "scripts": { "dev": "vite", "build": "tsc -p tsconfig.build.json && vite build",