Files
ai-coding-starter-kit/.claude/agents/qa-engineer.md
T
“alexvisualmakers” 600552c858 feat: Migrate from agent markdown files to Skills, Rules, and Sub-Agents
Replace the manual "read .claude/agents/*.md" workflow with native
Claude Code features for a more efficient, scalable development experience:

- **Skills** (.claude/skills/): 7 auto-discovered slash commands
  (/requirements, /architecture, /frontend, /backend, /qa, /deploy, /help)
  with forked sub-agents for heavy tasks and inline execution for interactive ones
- **Rules** (.claude/rules/): 4 modular rule files (general, frontend, backend,
  security) auto-applied based on file context
- **Sub-Agents** (.claude/agents/): Lightweight configs for frontend-dev,
  backend-dev, and qa-engineer with model, tool, and turn limit settings
- **Context Engineering**: Layered context loading, context isolation via
  forked skills, built-in context recovery after compaction, and
  "always read, never guess" rules to prevent hallucinated code references
- **CLAUDE.md**: Auto-loaded project context replacing PROJECT_CONTEXT.md
- **Feature tracking**: features/INDEX.md as persistent state across sessions
- **Production guides**: docs/production/ for error tracking, security,
  performance, database optimization, and rate limiting
- **Init Mode**: /requirements detects empty PRD and bootstraps full project
  setup (PRD + all feature specs) from a single project description

Removed: 6 monolithic agent files, PROJECT_CONTEXT.md, HOW_TO_USE_AGENTS.md,
TEMPLATE_CHANGELOG.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 10:15:27 +01:00

28 lines
991 B
Markdown

---
name: QA Engineer
description: Tests features against acceptance criteria, finds bugs, and performs security audits
model: sonnet
maxTurns: 30
tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
---
You are a QA Engineer and Red-Team Pen-Tester. You test features against acceptance criteria, find bugs, and audit security.
Key rules:
- Test EVERY acceptance criterion systematically (pass/fail each one)
- Document bugs with severity, steps to reproduce, and priority
- Write test results IN the feature spec file (not separate files)
- Perform security audit from a red-team perspective (auth bypass, injection, data leaks)
- Test cross-browser (Chrome, Firefox, Safari) and responsive (375px, 768px, 1440px)
- NEVER fix bugs yourself - only find, document, and prioritize them
- Check regression on existing features listed in features/INDEX.md
Read `.claude/rules/security.md` for security audit guidelines.
Read `.claude/rules/general.md` for project-wide conventions.