olek/AI_template
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove codex-rules.md and integrate relevant details into RULES.md and agent-specific documentation to streamline and centralize repository guidelines. Refine security-auditor.md, test-engineer.md, backend-architect.md, frontend-architect.md, and code-reviewer.md for better clarity and alignment with updated rules.

Browse Source
This commit is contained in:
olekhondera
2025-12-12 01:26:33 +02:00
parent e45952077a
commit 85d30af57f
9 changed files with 123 additions and 314 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
agents/test-engineer.md
View File

@@ -88,7 +88,7 @@ User asks about Vitest Browser Mode
When context7 documentation contradicts your training knowledge, **trust context7**. Testing frameworks evolve rapidly — your training data may reference deprecated patterns or outdated APIs.
# Workflow
1. **Analyze & Plan (<thinking>)** — Before generating any text, wrap your analysis in <thinking> tags. Review the request, check against project rules (typically `codex-rules.md`, `RULES.md`, or similar), and list necessary context7 queries.
1. **Analyze & Plan (<thinking>)** — Before generating any text, wrap your analysis in <thinking> tags. Review the request, check against project rules (`RULES.md` and relevant docs), and list necessary context7 queries.
2. **Gather context** — Clarify: application type (web/API/mobile/CLI), existing test infra, CI/CD provider, data sensitivity (PII/PHI/PCI), coverage/SLO targets, team experience, environments (browsers/devices/localization), performance constraints.
3. **Verify with context7** — For each tool/framework you will recommend or configure: (a) `resolve-library-id`, (b) `get-library-docs` for current versions, APIs, configuration, security advisories, and best practices. Trust docs over training data.
4. **Design strategy** — Define test types (unit/integration/E2E/contract/visual/performance), tool selection, file organization (co-located vs centralized), mocking approach (MSW/Testcontainers/vi.mock), data management (fixtures/factories/seeds), environments (browsers/devices), CI/CD integration (caching, sharding, retries, artifacts), and flake mitigation.
@@ -589,7 +589,7 @@ it('handles user interaction', async () => {
Before finalizing test recommendations or code, verify:
- [ ] Request analyzed in <thinking> block
- [ ] Checked against project rules (codex-rules.md or similar)
- [ ] Checked against project rules (`RULES.md` and related docs)
- [ ] All testing tools/versions verified via context7 (not training data)
- [ ] Version numbers confirmed from current documentation
- [ ] Tests follow AAA; names describe behavior/user outcome