chore: restructure 26 agents to 8-section template and trim Project Context per role

[singyichen]

Summary

• Rewrote all 26 agent files under .claude/agents/ to a uniform 8-section template: role paragraph → Project Context → Core Responsibilities → Workflow → Domain Standards → Quality Checklist → Output Format → Communication Style
• Kept tools: / description: frontmatter byte-identical to main; model: sonnet retained; team-lead special sections (FR-131 gate scripts, File Ownership, SDD Phase Sequence, Escalation Rules) relocated verbatim under ## Orchestration Standards
• Trimmed the Project Context Stack/Monorepo lines to a role-relevant subset (commit 1d1e451):
  • Backend agents (backend, dba, api-designer): FastAPI + PostgreSQL + Redis + Celery, backend/ only
  • Frontend agents (frontend, uiux, visual-designer): React + TypeScript + Vite, frontend/ only
  • Non-engineering agents (nlp-research-advisor, ba, pm, po, technical-writer, user-researcher): one-line stack summary, Monorepo line removed
  • Cross-cutting agents (remaining 14): full block unchanged
• Blurb, Modules list, and Constitution NON-NEGOTIABLEs (Generalization-First / Data Fairness) remain in all 26 files

Changed Files

Group	Files
Backend specialists	senior-backend, senior-dba, senior-api-designer
Frontend specialists	senior-frontend, senior-uiux, senior-visual-designer
Non-engineering	nlp-research-advisor, senior-ba, senior-pm, senior-po, senior-technical-writer, user-researcher
Cross-cutting	senior-architect, senior-code-reviewer, senior-debugger, senior-devops, senior-error-resolver, senior-full-stack, senior-i18n, senior-performance, senior-qa, senior-sa, senior-sd, senior-security, senior-tech-lead, team-lead

26 files changed, +1238 / −728 (docs-only: .claude/agents/*.md).

Test Plan

• Docs-only change — no production code touched; backend/frontend test suites not applicable
• Frontmatter tools: and description: fields verified byte-identical to main for all 26 agents
• All 26 files retain blurb, Modules list, and both Constitution NON-NEGOTIABLEs
• Variant distribution verified by grep: 14 full stack lines, 3 backend, 3 frontend, 6 one-line summaries; 19 Monorepo lines (team-lead uses its own compact format without one)
• No trimmed file references tools removed from its Project Context (grep for Playwright/Vitest/pnpm in backend files, pytest/uv/Celery in frontend files — zero hits)

🤖 Generated with Claude Code

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[amazon-q-developer]

Review Summary

This PR successfully restructures 26 agent configuration files to follow a uniform 8-section template while tailoring the Project Context section to each agent's specific role. The changes are documentation-only with no production code modifications.

Key Changes Verified:

• ✅ Uniform 8-section template applied consistently across all 26 files
• ✅ Frontmatter (tools:, description:, model:) preserved byte-identically
• ✅ Project Context appropriately scoped:
  • Backend agents: FastAPI + PostgreSQL + Redis + Celery stack
  • Frontend agents: React + TypeScript + Vite stack
  • Non-engineering agents: Simplified one-line stack summary
  • Cross-cutting agents: Full stack information retained
• ✅ Constitution NON-NEGOTIABLEs (Generalization-First, Data Fairness) maintained in all files
• ✅ Team-lead special sections (File Ownership, Quality Gate Rules, SDD Phase Sequence) properly relocated under Orchestration Standards

Structure Improvements:
The new template provides better organization with clear sections for role definition, responsibilities, workflow, standards, quality checks, output format, and communication style. This enhances agent clarity and maintainability.

No blocking issues identified. The restructuring improves documentation quality and agent guidance without affecting functionality.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[gemini-code-assist]

Code Review

This pull request standardizes and enhances the Claude agent profiles under .claude/agents/ by adding color configurations, detailed project context for the 'Label Suite' platform, core responsibilities, structured workflows, domain-specific standards, quality checklists, and communication styles. The review comments correctly identify a few inconsistencies in the updated profiles, such as mismatched section references in the workflows of the NLP Research Advisor and Senior Technical Writer, and a copy-pasted workflow in the User Researcher profile that does not align with its core responsibilities.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.