aigent-team 0.2.0 → 0.4.0

package/templates/teams/fe/examples/component-audit.md

@@ -0,0 +1,35 @@
+---
+name: Component Audit Example
+description: Example output of a frontend component audit report
+skillRef: component-audit
+tags: [fe, performance, accessibility]
+---
+
+# Example: Component Audit Report
+
+## Component: `<DataTable>`
+
+### Summary
+| Metric | Status | Notes |
+|--------|--------|-------|
+| Bundle size | ⚠️ Warning | 42 KB gzipped (target: <30 KB) |
+| Render performance | ✅ Pass | 16ms initial, 4ms re-render (1000 rows) |
+| Accessibility | ❌ Fail | Missing `aria-sort` on sortable columns |
+| Test coverage | ✅ Pass | 87% line coverage |
+
+### Issues Found
+
+1. **[P1] Missing aria-sort on sortable columns**
+   - Impact: Screen readers cannot convey sort state
+   - Fix: Add `aria-sort="ascending|descending|none"` to `<th>` elements
+   - Effort: Small (< 1 hour)
+
+2. **[P2] Bundle size exceeds target**
+   - Impact: Adds ~12 KB over budget to page load
+   - Root cause: Inline SVG icons (14 KB) not tree-shaken
+   - Fix: Replace inline SVGs with icon sprite or lazy-load
+   - Effort: Medium (2-4 hours)
+
+### Recommendations
+- Address P1 before next release (accessibility compliance)
+- Schedule P2 for next sprint (performance budget)

package/templates/teams/fe/references/accessibility.md

@@ -1,3 +1,10 @@
+---
+title: Accessibility (WCAG 2.1 AA)
+description: Keyboard navigation, ARIA patterns, color contrast, screen reader support, and focus management rules.
+whenToRead: When building or reviewing UI components for accessibility compliance
+tags: [frontend, accessibility, wcag, aria]
+---
+
 # Accessibility (WCAG 2.1 AA)
 
 ## Keyboard Navigation

package/templates/teams/fe/references/component-architecture.md

@@ -1,3 +1,10 @@
+---
+title: Component Architecture
+description: Props interface design, file structure conventions, composition patterns, and component responsibility boundaries.
+whenToRead: When designing new components or refactoring existing component structure
+tags: [frontend, components, architecture, react]
+---
+
 # Component Architecture
 
 ## Props Interface Design

package/templates/teams/fe/references/css-styling.md

@@ -1,3 +1,10 @@
+---
+title: CSS and Styling
+description: Tailwind conventions, design token usage, responsive patterns, and styling best practices.
+whenToRead: When writing or reviewing styles, Tailwind usage, or responsive layouts
+tags: [frontend, css, tailwind, styling]
+---
+
 # CSS & Styling
 
 ## Tailwind Conventions

package/templates/teams/fe/references/forms.md

@@ -1,3 +1,10 @@
+---
+title: Forms
+description: React Hook Form with Zod validation patterns, error handling, and form UX best practices.
+whenToRead: When building or reviewing form components and validation logic
+tags: [frontend, forms, validation, react-hook-form]
+---
+
 # Forms
 
 ## Stack: React Hook Form + Zod

package/templates/teams/fe/references/performance.md

@@ -1,3 +1,10 @@
+---
+title: Frontend Performance
+description: Core Web Vitals targets, bundle analysis, render profiling, and lazy loading strategies.
+whenToRead: When optimizing page load speed, bundle size, or runtime rendering performance
+tags: [frontend, performance, web-vitals, optimization]
+---
+
 # Frontend Performance
 
 ## Core Web Vitals Targets

package/templates/teams/fe/references/review-checklist.md

@@ -1,3 +1,10 @@
+---
+title: Frontend Review Checklist
+description: PR review checklist covering component design, rendering, accessibility, security, and testing standards.
+whenToRead: When reviewing pull requests that include frontend component or UI changes
+tags: [frontend, review, checklist, quality]
+---
+
 # Frontend Review Checklist
 
 ### Component Design

package/templates/teams/fe/references/security.md

@@ -1,3 +1,10 @@
+---
+title: Frontend Security
+description: XSS prevention, content sanitization, CSP headers, auth token handling, and client-side security patterns.
+whenToRead: When implementing or reviewing security-sensitive frontend code
+tags: [frontend, security, xss, authentication]
+---
+
 # Frontend Security
 
 ## XSS Prevention

package/templates/teams/fe/references/state-management.md

@@ -1,3 +1,10 @@
+---
+title: State Management
+description: Decision tree for choosing state solutions, server state with React Query, and client state with Zustand/Jotai.
+whenToRead: When deciding on state management approach or reviewing state-related code
+tags: [frontend, state, react-query, zustand]
+---
+
 # State Management
 
 ## Decision Tree

package/templates/teams/fe/references/testing.md

@@ -1,3 +1,10 @@
+---
+title: Frontend Testing
+description: Behavior-driven testing philosophy, AAA pattern, component and integration test strategies, and coverage guidelines.
+whenToRead: When writing or reviewing frontend tests or setting up test infrastructure
+tags: [frontend, testing, vitest, react-testing-library]
+---
+
 # Frontend Testing
 
 ## Testing Philosophy

package/templates/teams/fe/skills/analyze-bundle.md

@@ -1,3 +1,19 @@
+---
+name: Analyze Bundle Size
+description: Analyze JavaScript bundle size and identify optimization opportunities
+trigger: When adding new dependencies, investigating slow page loads, or performing a performance audit.
+useCases:
+  - FE Agent performing dependency audit before a release
+  - Lead Agent requesting a performance review after adding new features
+  - FE Agent investigating slow page load times reported by QA
+tags: [fe, performance, bundle, dependencies]
+governance:
+  version: "1.0.0"
+  owner: fe-team
+  status: active
+  lastReviewedAt: "2025-03-15"
+---
+
 # Skill: Analyze Bundle Size
 
 **Trigger**: When adding new dependencies, investigating slow page loads, or performing a performance audit.

package/templates/teams/fe/skills/component-audit.md

@@ -1,3 +1,14 @@
+---
+name: Component Audit
+description: Audit component library health by finding duplicates, dead code, and quality gaps
+trigger: When reviewing component library health, finding duplicates, or preparing for a design system migration.
+useCases:
+  - FE Agent cleaning up components before a design system migration
+  - Lead Agent assessing codebase health during sprint planning
+  - FE Agent identifying unused components for removal
+tags: [fe, components, design-system, code-quality]
+---
+
 # Skill: Component Audit
 
 **Trigger**: When reviewing component library health, finding duplicates, or preparing for a design system migration.

package/templates/teams/lead/references/cross-team-coordination.md

@@ -1,3 +1,10 @@
+---
+title: Cross-Team Coordination
+description: Patterns for managing API contract alignment, shared specs, and dependency resolution across frontend, backend, and other agent teams.
+whenToRead: When orchestrating multi-team tasks or resolving cross-team dependencies and contract mismatches.
+tags: [lead, coordination, contracts, cross-team]
+---
+
 # Cross-Team Coordination
 
 ## API Contract Alignment (FE ↔ BE)

package/templates/teams/lead/references/quality-gates.md

@@ -1,3 +1,10 @@
+---
+title: Quality Gates
+description: Definition of done checklists and feature completeness criteria for validating subtask and release readiness.
+whenToRead: When reviewing whether a subtask or feature meets completion criteria before sign-off.
+tags: [lead, quality, definition-of-done, checklist]
+---
+
 # Quality Gates
 
 ## Definition of Done (per subtask)

package/templates/teams/lead/references/task-decomposition.md

@@ -1,3 +1,10 @@
+---
+title: Task Decomposition
+description: Framework for analyzing tasks, identifying dependencies, and breaking work into parallelizable single-agent subtasks.
+whenToRead: When breaking down a new feature or task into subtasks for assignment to team agents.
+tags: [lead, decomposition, planning, orchestration]
+---
+
 # Task Decomposition
 
 ## Analysis Framework

package/templates/teams/lead/skills/parallel-orchestration.md

@@ -1,3 +1,14 @@
+---
+name: Parallel Agent Orchestration
+description: Coordinate multiple specialist agents working simultaneously on a shared feature
+trigger: When implementing a feature that requires multiple specialist agents working simultaneously.
+useCases:
+  - Lead Agent coordinating FE and BE agents building a new feature in parallel
+  - Lead Agent managing a cross-team effort with shared API contracts
+  - Lead Agent orchestrating BA, FE, BE, and QA agents for a full-stack deliverable
+tags: [lead, orchestration, coordination, parallel]
+---
+
 # Skill: Parallel Agent Orchestration
 
 **Trigger**: When implementing a feature that requires multiple specialist agents working simultaneously.

package/templates/teams/lead/skills/sprint-review.md

@@ -1,3 +1,14 @@
+---
+name: Sprint Review
+description: Review completed sprint work for quality, completeness, and cross-team alignment
+trigger: When reviewing completed work at the end of a sprint or milestone, assessing quality and completeness.
+useCases:
+  - Lead Agent running end-of-sprint quality assessment across all teams
+  - Lead Agent preparing a sprint summary for stakeholders
+  - Lead Agent identifying carried-over work and technical debt for backlog grooming
+tags: [lead, sprint, review, quality, planning]
+---
+
 # Skill: Sprint Review
 
 **Trigger**: When reviewing completed work at the end of a sprint or milestone, assessing quality and completeness.

package/templates/teams/qa/assets/test-report-template.md

@@ -0,0 +1,63 @@
+---
+name: Test Report Template
+description: Standard template for test execution reports
+format: markdown
+tags: [qa, testing, template]
+---
+
+# Test Report Template
+
+## Test Report: [Feature/Sprint Name]
+
+**Date:** [YYYY-MM-DD]
+**Tester:** [Name or Agent ID]
+**Environment:** [staging / production / local]
+**Build:** [Version or commit hash]
+
+### Summary
+
+| Metric | Value |
+|--------|-------|
+| Total test cases | 0 |
+| Passed | 0 |
+| Failed | 0 |
+| Blocked | 0 |
+| Not executed | 0 |
+| Pass rate | 0% |
+
+### Test Results by Category
+
+#### Unit Tests
+- **Status:** Pass / Fail
+- **Coverage:** [X]%
+- **Notes:** [Summary]
+
+#### Integration Tests
+- **Status:** Pass / Fail
+- **Notes:** [Summary]
+
+#### E2E Tests
+- **Status:** Pass / Fail
+- **Notes:** [Summary]
+
+### Failed Test Cases
+
+| Test ID | Description | Expected | Actual | Severity |
+|---------|-------------|----------|--------|----------|
+| [ID] | [Description] | [Expected] | [Actual] | Critical/High/Medium/Low |
+
+### Blocked Test Cases
+
+| Test ID | Description | Blocker |
+|---------|-------------|---------|
+| [ID] | [Description] | [Reason] |
+
+### Risks and Recommendations
+- [Identified risks]
+- [Recommended actions before release]
+
+### Sign-off
+- [ ] All critical tests passed
+- [ ] No open P0/P1 defects
+- [ ] Performance within acceptable thresholds
+- [ ] Ready for release: Yes / No

package/templates/teams/qa/output-contracts/test-plan-rubric.md

@@ -0,0 +1,36 @@
+---
+name: Test Plan Quality Rubric
+description: Self-validation checklist for QA agent test plan output
+format: checklist
+tags: [qa, quality]
+---
+
+# Output Contract: Test Plan
+
+Before delivering a test plan, validate against this rubric:
+
+## Structure (all required)
+- [ ] Has a clear title and scope statement
+- [ ] Links to the user story or feature being tested
+- [ ] Includes test environment requirements
+- [ ] Specifies entry and exit criteria
+
+## Test Coverage
+- [ ] All acceptance criteria from the user story have corresponding test cases
+- [ ] Happy path is covered with at least one positive test
+- [ ] Error paths are covered (invalid input, network failures, auth failures)
+- [ ] Boundary conditions are identified and tested
+- [ ] Tests are categorized by type: unit, integration, E2E
+
+## Test Cases (each must have)
+- [ ] Unique test case ID
+- [ ] Clear preconditions
+- [ ] Step-by-step actions
+- [ ] Expected result for each step
+- [ ] Priority (critical/high/medium/low)
+
+## Risk Assessment
+- [ ] High-risk areas are identified
+- [ ] Regression scope is defined
+- [ ] Performance test needs are assessed
+- [ ] Security test needs are assessed if applicable

package/templates/teams/qa/references/ci-integration.md

@@ -1,3 +1,10 @@
+---
+title: CI Integration
+description: Pipeline stage design, time budgets, test reporting, and failure response strategies for continuous integration.
+whenToRead: When configuring CI pipeline test stages or troubleshooting test reporting and pipeline performance.
+tags: [qa, ci, pipeline, reporting]
+---
+
 # CI Integration Reference
 
 ## Pipeline Stages

package/templates/teams/qa/references/e2e-testing.md

@@ -1,3 +1,10 @@
+---
+title: E2E Testing
+description: Page Object Model patterns, selector strategies, and flakiness prevention techniques for end-to-end tests.
+whenToRead: When writing or reviewing Playwright/Cypress E2E tests or debugging flaky end-to-end failures.
+tags: [qa, e2e, playwright, page-object-model]
+---
+
 # E2E Testing Reference
 
 ## Page Object Model

package/templates/teams/qa/references/mocking.md

@@ -1,3 +1,10 @@
+---
+title: Mocking
+description: Guidelines for mocking at system boundaries only, using MSW for HTTP mocks, and verifying mock-to-production contract fidelity.
+whenToRead: When deciding what to mock, setting up MSW handlers, or reviewing tests that use mocks.
+tags: [qa, mocking, msw, test-doubles]
+---
+
 # Mocking Reference
 
 ## Core Rule: Mock at System Boundaries Only

package/templates/teams/qa/references/performance-testing.md

@@ -1,3 +1,10 @@
+---
+title: Performance Testing
+description: Load scenario types, k6 script templates, and threshold definitions for smoke, load, stress, soak, and spike tests.
+whenToRead: When writing k6 performance scripts, defining load scenarios, or setting SLO-based thresholds.
+tags: [qa, performance, k6, load-testing]
+---
+
 # Performance Testing Reference
 
 ## Load Scenario Types

package/templates/teams/qa/references/review-checklist.md

@@ -1,3 +1,10 @@
+---
+title: Test Code Review Checklist
+description: Section-by-section checklist for reviewing PRs that add or modify test code, covering level selection, assertions, and isolation.
+whenToRead: When reviewing any pull request that touches test files.
+tags: [qa, review, checklist, code-review]
+---
+
 # Test Code Review Checklist
 
 Use this checklist when reviewing any PR that adds or modifies test code.

package/templates/teams/qa/references/security-testing.md

@@ -1,3 +1,10 @@
+---
+title: Security Testing
+description: OWASP Top 10 test coverage patterns, injection payload examples, and automated DAST scanning guidance.
+whenToRead: When performing a security audit, writing injection tests, or setting up ZAP scans.
+tags: [qa, security, owasp, dast]
+---
+
 # Security Testing Reference
 
 ## OWASP Top 10 — Test Coverage

package/templates/teams/qa/references/test-data.md

@@ -1,3 +1,10 @@
+---
+title: Test Data
+description: Factory pattern examples and strategies for generating self-contained, isolated test data with sensible defaults.
+whenToRead: When building test factories, seeding databases, or solving test data isolation problems.
+tags: [qa, test-data, factories, fixtures]
+---
+
 # Test Data Reference
 
 ## Factory Pattern

package/templates/teams/qa/references/test-strategy.md

@@ -1,3 +1,10 @@
+---
+title: Test Strategy
+description: Test pyramid enforcement ratios, time budgets per CI level, and mutation testing configuration guidance.
+whenToRead: When planning a new test suite, reviewing pyramid balance, or setting up mutation testing.
+tags: [qa, strategy, test-pyramid, mutation-testing]
+---
+
 # Test Strategy Reference
 
 ## Test Pyramid Enforcement

package/templates/teams/qa/skills/flaky-test-diagnosis.md

@@ -1,3 +1,14 @@
+---
+name: Diagnose Flaky Test
+description: Identify and fix the root cause of intermittently failing tests
+trigger: When a test is intermittently failing in CI or locally, passing on retry but failing inconsistently.
+useCases:
+  - QA Agent investigating a test that fails randomly in CI pipelines
+  - FE Agent debugging a component test that passes locally but fails in CI
+  - Lead Agent triaging a flaky test blocking a release
+tags: [qa, testing, flaky-tests, debugging, ci]
+---
+
 # Skill: Diagnose Flaky Test
 
 **Trigger**: When a test is intermittently failing in CI or locally, passing on retry but failing inconsistently.

package/templates/teams/qa/skills/generate-test-data.md

@@ -1,3 +1,18 @@
+---
+name: Generate Test Data
+description: Create factory functions, edge case data sets, and seed scripts for testing
+trigger: When setting up test fixtures, creating seed data for E2E tests, or testing edge cases and boundary conditions.
+useCases:
+  - QA Agent building test fixtures for a new feature's E2E test suite
+  - BE Agent creating seed data for integration tests with complex entity relationships
+  - QA Agent generating boundary-value data sets for input validation testing
+tags: [qa, testing, test-data, fixtures, e2e]
+governance:
+  version: "0.5.0"
+  status: deprecated
+  deprecatedReason: "Replaced by data-factory skill in v2.0"
+---
+
 # Skill: Generate Test Data
 
 **Trigger**: When setting up test fixtures, creating seed data for E2E tests, or testing edge cases and boundary conditions.