ac-framework 1.6.0 → 1.8.0

package/framework/.cline/skills/testing-qa/SKILL.md

@@ -0,0 +1,249 @@
+---
+name: testing-qa
+description: Automate the generation and maintenance of unit, integration, and end-to-end tests, as well as test data generation and debugging. Use when writing tests for new features, maintaining existing tests after API/UI changes, generating synthetic test data, or debugging test failures. Essential for ensuring code quality and preventing regressions.
+license: MIT
+metadata:
+  author: AC Framework
+  version: "1.0"
+---
+
+# Testing & QA
+
+Automated test generation, maintenance, and quality assurance for comprehensive code validation.
+
+## When to Use This Skill
+
+Use this skill when:
+- Writing tests for new features or components
+- Maintaining existing tests after API or UI changes
+- Generating synthetic test data for development/testing
+- Debugging failing tests or investigating coverage gaps
+- Setting up test infrastructure for a project
+- Running test suites and analyzing results
+
+## Instructions
+
+### Step 1: Analyze Test Requirements
+
+1. **Review the specification** or change document
+2. **Identify testable components**:
+   - Business logic functions
+   - API endpoints
+   - UI components/interactions
+   - Integration points
+3. **Determine test types needed**:
+   - Unit tests (isolated functions)
+   - Integration tests (component interactions)
+   - E2E tests (user workflows)
+
+### Step 2: Generate Test Cases
+
+For each component, generate tests covering:
+
+**Unit Tests**:
+- Happy path (normal operation)
+- Edge cases (empty input, max values, nulls)
+- Error cases (exceptions, invalid inputs)
+- Boundary conditions
+
+**Integration Tests**:
+- Component interactions
+- Data flow between modules
+- API contract validation
+- Database operations
+
+**E2E Tests**:
+- Critical user workflows
+- Multi-step processes
+- Cross-browser compatibility (if applicable)
+- Mobile responsiveness (if applicable)
+
+### Step 3: Create Test Files
+
+Follow project conventions:
+
+```
+test-file-naming:
+  unit: "*.test.js" or "*.spec.js"
+  integration: "*.integration.test.js"
+  e2e: "*.e2e.test.js" or in "e2e/" folder
+
+test-structure:
+  describe: "Component/Feature name"
+  it: "should [expected behavior] when [condition]"
+```
+
+### Step 4: Generate Test Data
+
+Create realistic test data:
+
+**Static Data**:
+```javascript
+const mockUsers = [
+  { id: 1, name: "John Doe", email: "john@example.com" },
+  { id: 2, name: "Jane Smith", email: "jane@example.com" }
+];
+```
+
+**Dynamic Data** (using factories):
+```javascript
+const generateUser = (overrides = {}) => ({
+  id: faker.datatype.uuid(),
+  name: faker.name.fullName(),
+  email: faker.internet.email(),
+  ...overrides
+});
+```
+
+**Synthetic Data for Load Testing**:
+- Large datasets for performance testing
+- Edge case data (max length strings, special characters)
+- Internationalization test data (Unicode, RTL languages)
+
+### Step 5: Implement Tests
+
+Write tests following best practices:
+
+**Arrange-Act-Assert Pattern**:
+```javascript
+test('should calculate total price with tax', () => {
+  // Arrange
+  const cart = { items: [{ price: 100, quantity: 2 }] };
+  const taxRate = 0.08;
+  
+  // Act
+  const total = calculateTotal(cart, taxRate);
+  
+  // Assert
+  expect(total).toBe(216); // 200 + 16 tax
+});
+```
+
+**Mock External Dependencies**:
+```javascript
+jest.mock('../api/client', () => ({
+  fetchUser: jest.fn()
+}));
+
+beforeEach(() => {
+  fetchUser.mockResolvedValue({ id: 1, name: 'Test User' });
+});
+```
+
+### Step 6: Run Tests and Debug
+
+1. **Execute test suite**:
+   ```bash
+   npm test
+   # or
+   npm run test:unit
+   npm run test:integration
+   npm run test:e2e
+   ```
+
+2. **Analyze failures**:
+   - Read error messages carefully
+   - Check stack traces
+   - Verify mocks are set up correctly
+   - Compare expected vs actual values
+
+3. **Debug failing tests**:
+   - Add console.log for debugging
+   - Use debugger statement
+   - Check test isolation (beforeEach/afterEach)
+   - Verify async handling (await, done callback)
+
+### Step 7: Maintain Tests
+
+When APIs or UI changes:
+
+1. **Identify affected tests** (run test suite)
+2. **Update test expectations** to match new behavior
+3. **Add new tests** for new functionality
+4. **Remove obsolete tests** for removed features
+5. **Update mocks** to match new interfaces
+
+### Step 8: Coverage Analysis
+
+1. **Run coverage report**:
+   ```bash
+   npm run test:coverage
+   ```
+
+2. **Identify gaps**:
+   - Uncovered branches (if/else conditions)
+   - Missing edge cases
+   - Untested error paths
+
+3. **Add tests** to cover gaps
+
+## Integration with OpenSpec
+
+- Use `openspec-verify-change` to validate tests pass
+- Link test files to tasks in tasks.md
+- Include test requirements in design.md
+- Reference test coverage in verification reports
+
+## Guardrails
+
+- **Test behavior, not implementation** - Tests should verify what code does, not how
+- **One assertion per test** (ideally) - Makes failures clearer
+- **Keep tests fast** - Unit tests should run in milliseconds
+- **Mock external systems** - Don't hit real databases/APIs in unit tests
+- **Clean up after tests** - Use afterEach to reset state
+- **Don't test framework code** - Focus on business logic
+
+## Common Patterns
+
+**Testing Async Code**:
+```javascript
+test('should fetch user data', async () => {
+  const user = await fetchUser(1);
+  expect(user).toEqual({ id: 1, name: 'John' });
+});
+```
+
+**Testing React Components**:
+```javascript
+import { render, screen, fireEvent } from '@testing-library/react';
+
+test('should toggle visibility on click', () => {
+  render(<ToggleButton />);
+  const button = screen.getByRole('button');
+  
+  fireEvent.click(button);
+  expect(screen.getByText('Visible')).toBeInTheDocument();
+  
+  fireEvent.click(button);
+  expect(screen.queryByText('Visible')).not.toBeInTheDocument();
+});
+```
+
+**Testing API Endpoints**:
+```javascript
+import request from 'supertest';
+import app from '../app';
+
+test('POST /api/users should create user', async () => {
+  const response = await request(app)
+    .post('/api/users')
+    .send({ name: 'John', email: 'john@example.com' });
+    
+  expect(response.status).toBe(201);
+  expect(response.body).toHaveProperty('id');
+});
+```
+
+## Requirements
+
+- Access to test runner (Jest, Mocha, Vitest, etc.)
+- Test utilities (@testing-library/react, supertest, etc.)
+- Code coverage tool (Istanbul, c8, etc.)
+- Access to the codebase being tested
+
+## See Also
+
+- `test-generator` - Generate initial test suite
+- `openspec-verify-change` - Validate implementation with tests
+- `systematic-debugging` - Debug failing tests
+- `secure-coding-cybersecurity` - Security-focused testing

package/framework/.clinerules/skills/acfm-memory/SKILL.md

@@ -0,0 +1,312 @@
+---
+name: acfm-memory
+description: Autonomous memory system for persistent learning across sessions. Automatically saves architectural decisions, bugfixes, patterns, and insights. Use to recall context from previous work and build institutional knowledge.
+---
+
+# AC Framework Memory System
+
+## Overview
+
+The AC Framework Memory System provides **autonomous persistent memory** for AI agents. It automatically detects and saves valuable knowledge during development, then recalls relevant context when needed.
+
+**Key Capabilities:**
+- **Automatic saving**: Detects and stores important decisions, patterns, and solutions
+- **Full-text search**: Find relevant memories instantly
+- **Context recall**: Get relevant knowledge before starting tasks
+- **Pattern analysis**: Detect recurring themes and errors
+- **Timeline view**: See chronological context around any memory
+
+## When to Use This Skill
+
+### Before Starting Work
+- **Recall relevant context**: `acfm memory recall "<task description>"`
+- **Check for similar changes**: `acfm memory search "<topic>"`
+- **Review patterns**: `acfm memory patterns`
+
+### During Work (Automatic)
+The agent automatically saves memories when:
+- Completing architectural proposals
+- Fixing bugs (especially after multiple attempts)
+- Refactoring code successfully
+- Optimizing performance
+- Discovering important patterns
+
+### After Work
+- **Review learnings**: `acfm memory stats`
+- **Export for sharing**: `acfm memory export team-memory.json`
+- **Find gaps**: `acfm memory patterns --min-frequency 1`
+
+## Memory Types
+
+| Type | Description | Auto-Trigger |
+|------|-------------|--------------|
+| `architectural_decision` | Major design decisions | After proposal/design |
+| `bugfix_pattern` | Solutions to bugs | After fixing error |
+| `refactor_technique` | Successful refactoring patterns | After refactor |
+| `performance_insight` | Optimization learnings | After performance work |
+| `security_fix` | Security vulnerability fixes | After security patch |
+| `api_pattern` | API design patterns | After API work |
+| `convention` | Project conventions | After establishing pattern |
+| `workaround` | Temporary solutions | After implementing hack |
+| `context_boundary` | System limitations | After defining boundaries |
+
+## Commands
+
+### Core Commands
+
+#### Initialize Memory System
+```bash
+acfm memory init
+```
+Creates the SQLite database at `~/.acfm/memory.db`.
+
+#### Save Memory (Manual)
+```bash
+acfm memory save "Descripción de la decisión o patrón" \
+  --type architectural_decision \
+  --importance high \
+  --tags "react,performance"
+```
+
+#### Recall Context
+```bash
+# For specific task
+acfm memory recall "implementing authentication"
+
+# For current project (general context)
+acfm memory recall
+```
+
+#### Search Memories
+```bash
+# Basic search
+acfm memory search "JWT"
+
+# Filtered search
+acfm memory search "database" --type architectural_decision --importance high
+```
+
+### Advanced Commands
+
+#### Timeline View
+```bash
+acfm memory timeline <memory-id>
+```
+Shows what happened before and after a specific memory.
+
+#### Connections
+```bash
+acfm memory connections <memory-id> --depth 2
+```
+Shows related memories as a graph.
+
+#### Pattern Detection
+```bash
+acfm memory patterns
+acfm memory patterns --type bugfix_pattern
+```
+Finds recurring topics and frequent error types.
+
+#### Predictive Recall
+```bash
+acfm memory anticipate "caching strategy"
+```
+Predicts which memories will be relevant for a future task.
+
+#### Statistics
+```bash
+acfm memory stats
+acfm memory stats --project /path/to/project
+```
+
+#### Export/Import
+```bash
+# Export for sharing
+acfm memory export team-memory.json
+
+# Import shared knowledge
+acfm memory import team-memory.json
+```
+
+## Auto-Save Behavior
+
+### What Triggers Auto-Save
+
+The agent evaluates content using a confidence score (0-1):
+
+**High confidence triggers (auto-save):**
+- Contains decision keywords: "decidimos", "optamos", "mejor usar"
+- Describes solution to problem
+- Contains architectural guidance
+- Has error + solution pair
+- Takes >10 minutes to resolve
+
+**Low confidence (skip):**
+- Very short content (<50 chars)
+- Contains specific IDs/UUIDs
+- Temporary TODOs
+- Obvious/common knowledge
+
+### Confidence Scoring
+
+```
+Base: 0.5
++ Decision keywords: +0.25
++ Contains solution: +0.20
++ Bug fix: +0.15
++ Architecture: +0.20
++ Optimization: +0.15
++ Security: +0.25
+- Too short: -0.20
+- Specific IDs: -0.15
+- TODO/FIXME: -0.20
+
+Threshold for auto-save: 0.60
+```
+
+### Notification
+
+When auto-saving, the agent will display:
+```
+💾 Memory saved: [Brief description of what was learned]
+   Type: bugfix_pattern | Confidence: 85%
+```
+
+## Privacy
+
+Content between `<private>` tags is automatically redacted:
+
+```markdown
+Decidimos usar AWS para hosting. <private>Usaremos la cuenta
+producción-env-123</private> para el deployment.
+```
+
+Saved as:
+```
+Decidimos usar AWS para hosting. [REDACTED PRIVATE CONTENT]
+```
+
+## Integration with Spec Workflow
+
+### Before Creating Artifacts
+
+When you request `acfm spec instructions`, the system automatically:
+
+1. Queries memories related to the change topic
+2. Includes relevant memories in the response
+3. Displays them as context for the agent
+
+Example output:
+```json
+{
+  "instruction": "...",
+  "relevantMemories": [
+    {
+      "id": 42,
+      "type": "architectural_decision",
+      "content": "Previous auth system used JWT...",
+      "importance": "high"
+    }
+  ]
+}
+```
+
+### During Apply Phase
+
+When implementing tasks, the system recalls:
+- Patterns from similar previous tasks
+- Bugfixes related to current work
+- Performance insights for optimization tasks
+
+## Best Practices
+
+### For Agents
+
+1. **Always recall before starting**: Check `acfm memory recall` for relevant context
+2. **Let auto-save work**: Don't manually save everything - trust the confidence scoring
+3. **Use topic keys**: When manually saving, use consistent topic keys for deduplication
+4. **Mark importance**: Critical decisions should be marked `critical` or `high`
+5. **Add tags**: Tags improve searchability
+
+### For Users
+
+1. **Initialize once**: Run `acfm memory init` per machine
+2. **Review periodically**: Check `acfm memory stats` to see what's been learned
+3. **Export regularly**: Share knowledge with team via `acfm memory export`
+4. **Prune old data**: Use `acfm memory prune` to archive obsolete memories
+5. **Use private tags**: Mark sensitive content with `<private>` tags
+
+## Examples
+
+### Example 1: Bug Fix
+
+**Agent fixes an authentication bug:**
+```
+💾 Memory saved: JWT refresh token fails when expired during request
+   Type: bugfix_pattern | Confidence: 87%
+   Solution: Implement token refresh interceptor
+```
+
+**Later, similar task:**
+```bash
+$ acfm memory recall "authentication token"
+→ [Memory #42] JWT refresh token fails when expired...
+```
+
+### Example 2: Architectural Decision
+
+**Agent completes proposal:**
+```
+💾 Memory saved: Microservices architecture chosen for scalability
+   Type: architectural_decision | Confidence: 92%
+   Tags: ["architecture", "microservices", "scalability"]
+```
+
+**Weeks later, new service:**
+```bash
+$ acfm memory search "microservices" --type architectural_decision
+→ [Memory #15] Microservices architecture chosen for scalability
+```
+
+### Example 3: Pattern Detection
+
+```bash
+$ acfm memory patterns --type bugfix_pattern
+
+Detected patterns:
+- null-check-react (3×) - Null checks in React components
+- async-race-condition (2×) - Race conditions in async code
+- cors-preflight (2×) - CORS preflight issues
+
+Recommendation: Consider adding ESLint rules for null checks
+```
+
+## Troubleshooting
+
+### Memory not saving
+- Check initialization: `acfm memory init`
+- Content may be below confidence threshold
+- May contain too many specific IDs
+
+### Search not finding results
+- Try broader keywords
+- Use `acfm memory recall` without query for general context
+- Check if memories exist: `acfm memory stats`
+
+### Database locked
+- Close other instances of `acfm`
+- SQLite is single-writer; wait a moment and retry
+
+## Related Skills
+
+- `acfm-spec-workflow` - Foundation for spec-driven development
+- `context-synthesizer` - For managing context in long conversations
+- `systematic-debugging` - For complex problem resolution
+
+## CLI Reference
+
+See `acfm memory --help` for all commands and options.
+
+---
+
+**Remember**: The memory system learns from every interaction. The more you use it, the more valuable it becomes.