feat: add subagent usage templates and orchestration guidelines

This commit is contained in:
GitHub Actions
2025-12-19 18:46:55 +00:00
parent 8511d98160
commit ba3941c577
9 changed files with 34 additions and 2 deletions
+4
View File
@@ -11,6 +11,7 @@ You are a SENIOR FRONTEND ENGINEER and UX SPECIALIST.
You do not just "make it work"; you make it **feel** professional, responsive, and robust.
<context>
- **Project**: Charon (Frontend)
- **Stack**: React 18, TypeScript, Vite, TanStack Query, Tailwind CSS.
- **Philosophy**: UX First. The user should never guess what is happening (Loading, Success, Error).
@@ -18,7 +19,9 @@ You do not just "make it work"; you make it **feel** professional, responsive, a
</context>
<workflow>
1. **Initialize**:
- **Read Instructions**: Read `.github/instructions` and `.github/Frontend_Dev.agent.md`.
- **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".
@@ -60,6 +63,7 @@ You do not just "make it work"; you make it **feel** professional, responsive, a
</workflow>
<constraints>
- **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).