codingwithagent 1.0.0

package/templates/antigravity/standard/.agent/rules/testing.md

@@ -0,0 +1,197 @@
+---
+trigger: always_on
+---
+
+# Testing Standards and Requirements
+
+## Testing Philosophy
+
+- Tests ensure code quality and prevent regressions
+- Unit tests must accompany all new code
+- Tests are living documentation
+- Coverage should increase or maintain, never decrease
+- Write tests that would catch real bugs
+
+## Coverage Requirements
+
+- Maintain unit test threshold for modern codebases
+- Aim for 80%+ coverage on new code
+- Report previous and current coverage in PRs
+- 100% coverage = previous not needed in PR
+- Coverage decrease requires justification
+
+## Unit Testing Standards
+
+### What to Test
+
+- All exported functions and utilities
+- Component rendering with various props
+- Conditional logic and edge cases
+- Event handlers and user interactions
+- State changes and Redux actions
+- Error handling and boundary conditions
+- PropTypes validation
+
+### What NOT to Test
+
+- Third-party library internals
+- Trivial getters/setters
+- Constant values
+- External API implementations (mock these)
+
+### Unit Test Best Practices
+
+- **Shallow render preferred**: Use shallow unless hooks require mount
+- **Single instance per scope**: Reuse component instance, update props/state
+- **No long timeouts**: Keep setTimeout < 100ms if needed
+- **Avoid snapshots**: Remove when possible, update reluctantly
+- **Mock external dependencies**: APIs, Redux store, third-party libraries
+- **Clean up mocks**: Use beforeEach and afterAll to reset
+
+### Test Structure
+
+```javascript
+describe("ComponentName", () => {
+  let wrapper;
+  let props;
+
+  beforeEach(() => {
+    props = {
+      // default props
+    };
+  });
+
+  afterAll(() => {
+    jest.clearAllMocks();
+  });
+
+  it("should render correctly with default props", () => {
+    wrapper = shallow(<ComponentName {...props} />);
+    expect(wrapper.exists()).toBe(true);
+  });
+
+  it("should call onClick handler when button clicked", () => {
+    const mockOnClick = jest.fn();
+    wrapper = shallow(<ComponentName {...props} onClick={mockOnClick} />);
+    wrapper.find("button").simulate("click");
+    expect(mockOnClick).toHaveBeenCalledTimes(1);
+  });
+});
+```
+
+### Dates in Tests
+
+- Do NOT mock dates in the future
+- Override moment.now in tests if current date used
+- Use consistent date formats
+- Test timezone handling
+
+### Component Testing
+
+- Test all user interactions
+- Verify proper prop handling
+- Test conditional rendering paths
+- Verify event handlers fire correctly
+- Test error states and loading states
+- Accessibility: Test keyboard navigation, ARIA labels
+
+### Integration Testing
+
+- Test user journeys across multiple components
+- Verify data flow through Redux
+- Test routing and navigation
+- Verify API integration with mocked responses
+
+### Testing Tools
+
+- Jest: Test runner and assertion library
+- React Testing Library: Component testing (preferred)
+- Enzyme: Shallow/mount rendering (legacy, minimize use)
+- React Hooks Testing Library: For custom hooks
+- Mock Service Worker (MSW): API mocking
+
+### Test Naming Conventions
+
+- Describe blocks: Component or function name
+- It blocks: "should [expected behavior] when [condition]"
+- Be specific and descriptive
+- Avoid "works correctly" or "is defined"
+
+```javascript
+// GOOD
+it("should display error message when form submission fails", () => {});
+it("should disable submit button when form is invalid", () => {});
+
+// BAD
+it("works correctly", () => {});
+it("handles errors", () => {});
+```
+
+## Mocking Best Practices
+
+### When to Mock
+
+- External API calls
+- Redux store and actions
+- Browser APIs (localStorage, window, document)
+- Third-party libraries
+- Time-dependent functions (Date, moment)
+- File system operations
+
+### How to Mock
+
+```javascript
+// Mock module
+jest.mock("../utils/api", () => ({
+  fetchData: jest.fn(),
+}));
+
+// Mock with implementation
+const mockFn = jest.fn((a, b) => a + b);
+
+// Restore after tests
+afterEach(() => {
+  jest.clearAllMocks();
+});
+
+afterAll(() => {
+  jest.restoreAllMocks();
+});
+```
+
+### What NOT to Mock
+
+- Component's own functions (test real behavior)
+- Simple utility functions (test actual implementation)
+- PropTypes validation
+- React internals
+
+## Testing Anti-Patterns
+
+### Avoid These
+
+- Testing implementation details instead of behavior
+- Testing third-party library internals
+- Snapshot tests without review
+- Excessive mocking that doesn't reflect real usage
+- Tests that pass regardless of code correctness
+- setTimeout without cleanup
+- Tests depending on execution order
+
+### Do This Instead
+
+- Test user-visible behavior
+- Mock external dependencies only
+- Explicit assertions over snapshots
+- Realistic mocks reflecting actual API responses
+- Assertions that would fail if code breaks
+- Immediate assertions or controlled timing
+- Independent, isolated tests
+
+### Accessibility Testing
+
+- Test keyboard navigation (Tab, Enter, Space, Escape)
+- Verify ARIA labels and roles
+- Test screen reader announcements
+- Verify focus management
+- Test with accessibility testing libraries

package/templates/antigravity/standard/README.md

@@ -0,0 +1,39 @@
+# Antigravity - Standard Profile ⭐
+
+Recommended baseline for production code with comprehensive rules.
+
+## What's Included
+
+5 detailed rule files:
+
+- `accessibility.md` - WCAG 2.1 AA standards
+- `code-quality.md` - Naming, patterns, best practices
+- `react-components.md` - Hooks, JSX, component design
+- `testing.md` - 80%+ coverage, testing patterns
+- `pull-request-review.md` - PR standards and review checklist
+
+## Installation
+
+```bash
+npx codingwithagent init
+# Select tool: 3. Antigravity
+# Select profile: 2. Standard
+```
+
+## Files created
+
+```
+.agent/rules/
+├── accessibility.md
+├── code-quality.md
+├── react-components.md
+├── testing.md
+└── pull-request-review.md
+```
+
+## Best For
+
+- Production applications
+- Team projects
+- Enterprise development
+- Long-term maintenance

package/templates/antigravity/strict/.agent/README.md

@@ -0,0 +1,46 @@
+# Antigravity - Strict Profile
+
+Maximum enforcement with zero tolerance for violations.
+
+## What's Included
+
+6 comprehensive rule files:
+
+- `accessibility.md` - WCAG 2.1 AAA standards
+- `code-quality.md` - 90% coverage, TypeScript mandatory
+- `react-components.md` - 100% component coverage, strict hooks
+- `testing.md` - 90% minimum, zero flaky tests
+- `pull-request-review.md` - 2+ approvals, strict SLA
+- `security.md` - OWASP compliance, zero vulnerabilities
+
+## Installation
+
+```bash
+npx codingwithagent init
+# Select tool: 3. Antigravity
+# Select profile: 3. Strict
+```
+
+## Files created
+
+```
+.agent/rules/
+├── accessibility.md
+├── code-quality.md
+├── react-components.md
+├── testing.md
+├── pull-request-review.md
+└── security.md
+```
+
+## Requirements
+
+- TypeScript (no `any` type)
+- Components max 150 lines
+- Lighthouse accessibility: 100
+- Security vulnerabilities: 0
+- Performance score: >90
+
+## Warning
+
+Only use if committed to maximum quality.

package/templates/antigravity/strict/.agent/rules/accessibility.md

@@ -0,0 +1,199 @@
+---
+trigger: always_on
+---
+
+# Accessibility Standards - STRICT (Zero Tolerance)
+
+## Compliance Requirements - MANDATORY
+
+- WCAG 2.1 Level AA MINIMUM (AAA when possible)
+- 100% keyboard accessibility (no exceptions)
+- ALL features tested with screen readers before PR approval
+- Automated accessibility tests REQUIRED in CI/CD
+- Manual accessibility testing MANDATORY for all UI changes
+
+## POUR Principles - Strict Enforcement
+
+### Perceivable - MUST BE ACCESSIBLE
+
+- ALL images MUST have alt text (or alt="" if decorative) - NO EXCEPTIONS
+- ALL videos MUST have captions
+- ALL audio MUST have transcripts
+- Color contrast MUST be 4.5:1 minimum (7:1 for AAA preferred)
+- NEVER use color alone to convey information
+- Text MUST be resizable up to 200% without loss of content
+
+### Operable - MUST WORK WITH KEYBOARD
+
+- ALL functionality MUST work with keyboard only
+- Visible focus indicators REQUIRED (minimum 2px outline)
+- Focus order MUST be logical
+- NO keyboard traps (zero tolerance)
+- NEVER use `tabIndex > 0` (PR rejection if found)
+- NO time limits unless user can control them
+
+### Understandable - MUST BE CLEAR
+
+- Proper heading hierarchy (h1 > h2 > h3, NO skipping)
+- Semantic HTML MANDATORY (header, nav, main, footer, button)
+- Form labels REQUIRED for ALL inputs
+- Error messages MUST be clear and actionable
+- Language attribute MUST be set on all pages
+
+### Robust - MUST WORK EVERYWHERE
+
+- Valid HTML (pass W3C validator)
+- Test with NVDA, JAWS, VoiceOver, TalkBack (ALL required)
+- Works with assistive technologies
+- Compatible with all major browsers + screen readers
+
+## Implementation Requirements - STRICT
+
+### Screen Reader Support - MANDATORY
+
+- Use semantic HTML FIRST (button, not div with onClick)
+- ARIA ONLY when semantic HTML insufficient
+- role="alert" MUST be used sparingly (overuse = PR rejection)
+- Announce ALL state changes (loading, success, error)
+- Test EVERY feature with screen reader before PR
+
+### Form Accessibility - ZERO TOLERANCE
+
+- ALL form fields MUST have associated labels (no visual-only labels)
+- Required fields MUST be indicated programmatically
+- Error messages MUST be associated with inputs (aria-describedby)
+- Form validation MUST happen on blur or submit (not on every keystroke)
+- Success confirmations MUST be announced to screen readers
+
+### Interactive Elements - STRICT REQUIREMENTS
+
+- Buttons MINIMUM size: 44x44 CSS pixels (WCAG AAA)
+- Links MUST have descriptive text (no "click here", "read more")
+- External links MUST indicate new window/tab
+- Custom controls MUST have proper ARIA attributes
+- ALL custom actions MUST be keyboard accessible
+
+### Mobile Accessibility - MANDATORY
+
+- Touch targets MINIMUM 44x44 pixels
+- Pinch-to-zoom MUST be enabled (no viewport user-scalable=no)
+- Test with VoiceOver (iOS) AND TalkBack (Android)
+- Orientation changes MUST be supported
+- Touch gestures MUST have keyboard alternatives
+
+## Testing Requirements - MANDATORY
+
+### Automated Testing - REQUIRED
+
+- axe-core or jest-axe in ALL unit tests
+- Lighthouse accessibility score MUST be 100
+- pa11y in CI/CD pipeline (build fails on errors)
+- ESLint jsx-a11y plugin with ALL rules enabled
+- NO eslint-disable for a11y rules without architect approval
+
+### Manual Testing - REQUIRED BEFORE PR
+
+- Keyboard navigation test (Tab, Shift+Tab, Enter, Space, Escape)
+- Screen reader test with NVDA (Windows) OR VoiceOver (Mac)
+- Color contrast analyzer (ALL text and UI elements)
+- Zoom to 200% test (content must remain readable)
+- Test with CSS disabled (content must be understandable)
+
+### Testing Checklist - ALL REQUIRED
+
+- [ ] Keyboard navigation works for ALL functionality
+- [ ] Visible focus indicators present
+- [ ] Focus order is logical
+- [ ] Screen reader announces content correctly
+- [ ] Color contrast passes 4.5:1 (7:1 preferred)
+- [ ] Alt text provided for ALL meaningful images
+- [ ] Form labels properly associated
+- [ ] Error messages clear and associated
+- [ ] NO automatic timeouts
+- [ ] NO flashing content
+- [ ] Semantic HTML used throughout
+- [ ] Zoom to 200% tested and working
+- [ ] Mobile touch targets 44x44px minimum
+
+## Prohibited Practices - IMMEDIATE PR REJECTION
+
+### NEVER DO THESE
+
+- NEVER use `tabIndex > 0`
+- NEVER use color alone to convey information
+- NEVER disable zoom (viewport user-scalable=no)
+- NEVER use flashing/blinking content
+- NEVER create keyboard traps
+- NEVER use non-semantic HTML for interactive elements
+- NEVER skip heading levels (h1 to h3)
+- NEVER use `role="presentation"` on interactive elements
+- NEVER use placeholder as label
+- NEVER auto-play audio/video
+- NEVER mock screen reader implementations with aria-label hacks
+
+## ARIA - Use ONLY When Necessary
+
+### First Rule of ARIA: Don't Use ARIA
+
+- Use semantic HTML FIRST
+- ARIA only when semantic HTML insufficient
+- NEVER change semantic meaning with ARIA
+- ALL ARIA controls MUST be keyboard accessible
+
+### Allowed ARIA Patterns (Only These)
+
+- `aria-label`: When visual label not present
+- `aria-labelledby`: Associate existing label
+- `aria-describedby`: Additional description
+- `aria-live`: Dynamic content announcements (polite or assertive only)
+- `aria-expanded`: Collapsible content state
+- `aria-hidden="true"`: Hide decorative elements ONLY
+- `aria-invalid`: Form validation errors
+
+### ARIA Violations = PR Rejection
+
+- Incorrect role usage
+- Missing required ARIA attributes
+- ARIA on non-interactive elements
+- Conflicting ARIA and HTML semantics
+
+## Color Contrast - STRICT REQUIREMENTS
+
+### Minimum Ratios (AAA Preferred)
+
+- Normal text: 4.5:1 minimum (7:1 for AAA)
+- Large text (18pt+ or 14pt+ bold): 3:1 minimum (4.5:1 for AAA)
+- UI components: 3:1 minimum
+- Icons: 3:1 minimum
+- States (hover, focus, active): 3:1 minimum
+
+### Testing Required
+
+- Use Color Contrast Analyzer tool
+- Test ALL color combinations
+- Test hover/focus/active states
+- Test with grayscale view
+- Test with color blindness simulators
+
+## Enforcement
+
+### PR Review Requirements
+
+- Accessibility checklist MUST be completed
+- Screen reader testing video/screenshots required for UI changes
+- Automated tests MUST pass (100 Lighthouse score)
+- Manual testing MUST be documented
+- Architect review REQUIRED for custom ARIA usage
+
+### Build Pipeline
+
+- Builds FAIL on accessibility violations
+- axe-core violations block merge
+- Lighthouse score < 100 blocks merge
+- ESLint a11y errors block merge
+
+## Resources - MANDATORY READING
+
+- WCAG 2.1: https://www.w3.org/WAI/WCAG21/quickref/
+- ARIA Authoring Practices: https://www.w3.org/WAI/ARIA/apg/
+- WebAIM: https://webaim.org/