agileflow 3.4.3 → 4.0.0-alpha.10

package/src/core/experts/testing/workflow.md

@@ -1,143 +0,0 @@
----
-description: Plan, build, and improve testing feature with expertise-driven workflow
-argument-hint: <testing feature description>
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/testing/expertise.yaml
----
-
-# Testing Expert: Plan → Build → Self-Improve
-
-You are executing a complete testing feature implementation with automatic knowledge capture.
-
-## CRITICAL: Three-Step Workflow
-
-**You MUST follow this exact sequence. Do not skip steps.**
-
----
-
-## Step 1: PLAN (Expertise-Informed)
-
-### 1.1 Load Your Expertise
-Read your expertise file at `{{EXPERTISE_FILE}}` FIRST.
-
-Extract from it:
-- Test file locations and naming conventions
-- Testing framework(s) configured
-- Patterns (AAA, fixtures, mocks)
-- Coverage thresholds
-
-### 1.2 Validate Against Codebase
-Before planning, verify your expertise:
-```bash
-ls -la tests/ __tests__/ src/**/*.test.ts 2>/dev/null || true
-cat jest.config.js vitest.config.ts 2>/dev/null || true
-```
-
-### 1.3 Create Implementation Plan
-```markdown
-## Test Implementation Plan
-
-### Tests to Create
-1. [test file path] - [test description]
-   - Test cases: [list]
-   - Fixtures needed: [list]
-   - Mocks needed: [list]
-
-### Pattern to Follow
-[Reference AAA pattern, fixture pattern from expertise]
-
-### Coverage Target
-[Expected coverage impact]
-
-### Validation
-- [ ] Tests pass
-- [ ] Coverage meets threshold
-- [ ] No flaky tests
-```
-
----
-
-## Step 2: BUILD (Execute Plan)
-
-### 2.1 Pre-Build Verification
-- Ensure test framework is installed
-- Check existing test patterns
-- Verify fixture helpers available
-
-### 2.2 Execute the Plan
-```typescript
-// Follow AAA pattern from expertise
-describe('Feature', () => {
-  it('should behavior', () => {
-    // Arrange
-    const input = fixture;
-
-    // Act
-    const result = functionUnderTest(input);
-
-    // Assert
-    expect(result).toBe(expected);
-  });
-});
-```
-
-### 2.3 Capture Changes
-```bash
-git diff --name-only | grep -E "(test|spec)"
-git diff HEAD
-```
-
-### 2.4 Validate Build
-- Run tests: `npm test`
-- Check coverage: `npm run coverage`
-- Run 3x to detect flakiness
-
-**On Failure**: Stop. Do NOT proceed to self-improve.
-
----
-
-## Step 3: SELF-IMPROVE (Update Expertise)
-
-**ONLY run if Step 2 succeeded.**
-
-### 3.1 Analyze What Changed
-- New test files added
-- New patterns introduced
-- New fixtures created
-- Coverage changes
-
-### 3.2 Update Expertise File
-Read and update `{{EXPERTISE_FILE}}`:
-
-**Update `files` if:**
-- New test directories created
-- New fixture files added
-
-**Update `patterns` if:**
-- New testing pattern used
-- Better mocking approach discovered
-
-**Update `conventions` if:**
-- Naming convention clarified
-- Coverage threshold changed
-
-### 3.3 Add Learnings Entry
-```yaml
-learnings:
-  - date: 2025-12-16
-    insight: "Added [test type] for [feature]"
-    files_affected:
-      - tests/feature.test.ts
-    context: "Feature: {{argument}}"
-```
-
-### 3.4 Validate and Save
-- [ ] All paths exist
-- [ ] `last_updated` current
-- [ ] No duplicates
-
----
-
-## Testing Feature Request
-
-{{argument}}

package/src/core/experts/ui/expertise.yaml

@@ -1,133 +0,0 @@
-# UI Expert - Mental Model
-#
-# This file represents the agent's understanding of UI patterns.
-# It is populated with AgileFlow-generic knowledge and learns project-specific
-# details through the self-improve workflow.
-#
-# NOT a source of truth - always validate against actual code.
-
-domain: ui
-last_updated: 2025-12-21
-version: 1.1
-
-# Key files the UI expert needs to know
-files:
-  components:
-    - path: src/components/
-      purpose: Reusable UI components
-      pattern: "<ComponentName>/<ComponentName>.tsx"
-    - path: src/components/ui/
-      purpose: Base UI primitives (shadcn/ui style)
-      conventions: "Radix + Tailwind composition"
-    - path: components/
-      purpose: Alternative component location
-      pattern: "<ComponentName>.tsx"
-
-  pages:
-    - path: src/app/
-      purpose: Next.js App Router pages
-      pattern: "<route>/page.tsx"
-    - path: src/pages/
-      purpose: Next.js Pages Router
-      pattern: "<route>.tsx"
-    - path: app/
-      purpose: Alternative App Router location
-      conventions: "layout.tsx, page.tsx, loading.tsx, error.tsx"
-
-  styles:
-    - path: src/styles/
-      purpose: Global styles and CSS
-      key_files: [globals.css, variables.css]
-    - path: tailwind.config.js
-      purpose: Tailwind CSS configuration
-      conventions: "theme, plugins, content paths"
-    - path: tailwind.config.ts
-      purpose: Tailwind config (TypeScript)
-      conventions: "Type-safe config"
-
-  hooks:
-    - path: src/hooks/
-      purpose: Custom React hooks
-      pattern: "use<HookName>.ts"
-    - path: src/lib/hooks/
-      purpose: Alternative hooks location
-      conventions: "Reusable stateful logic"
-
-  utils:
-    - path: src/lib/utils.ts
-      purpose: Utility functions (cn, etc.)
-      key_exports: [cn]
-    - path: src/utils/
-      purpose: General utilities
-      conventions: "Pure functions"
-
-  # AgileFlow CLI-specific (Node.js CLI, not web UI)
-  cli_ui:
-    - path: packages/cli/tools/cli/lib/ui.js
-      purpose: "CLI UI utilities (logo, prompts, colors)"
-      exports: [displayLogo, displaySection, success, warning, error, info, promptInstall, confirm]
-
-# Component registry
-# Self-improve will populate project-specific components
-relationships: []
-  # Example - will be populated by self-improve:
-  # - component: Button
-  #   variants: [default, destructive, outline, secondary, ghost, link]
-  #   location: src/components/ui/button.tsx
-  #   props: [variant, size, asChild]
-  # - component: Card
-  #   children: [CardHeader, CardTitle, CardContent, CardFooter]
-  #   location: src/components/ui/card.tsx
-
-# UI patterns the expert should recognize and follow
-patterns:
-  - name: "Component composition"
-    description: "Build complex UIs from small, focused components"
-    location: All components
-    principle: "Single responsibility per component"
-
-  - name: "Props interface"
-    description: "TypeScript interface for component props"
-    location: Component file top
-    convention: "interface ComponentNameProps"
-
-  # Generic React patterns (forwardRef, Tailwind, CVA, a11y) omitted - models know these
-
-  - name: "CLI Colored Output"
-    description: "Use chalk for terminal colors with semantic meaning"
-    location: packages/cli/tools/cli/lib/ui.js
-    colors:
-      - "green (success): ✓ messages"
-      - "yellow (warning): ⚠ messages"
-      - "red (error): ✗ messages"
-      - "dim (info): informational text"
-      - "#e8683a (brand): AgileFlow logo and headers"
-
-  - name: "Interactive Prompts"
-    description: "Use inquirer for multi-step CLI wizards"
-    location: packages/cli/tools/cli/lib/ui.js
-    types: [input, checkbox, confirm]
-
-# Conventions the UI expert should follow
-conventions:
-  - "Components: PascalCase (Button, UserCard, NavMenu)"
-  - "Files: Match component name or kebab-case"
-  - "Props: interface <ComponentName>Props"
-  - "Styling: Tailwind classes, avoid inline styles"
-  - "Icons: Lucide React library (or project-specific)"
-  - "State: useState for local, context/store for shared"
-  - "Effects: useEffect with proper deps array"
-  - "Accessibility: Always include aria-label for icons, role for custom elements"
-  - "Testing: React Testing Library, test user interactions"
-  - "CLI colors: chalk with semantic colors (green=success, red=error, yellow=warn)"
-  - "CLI prompts: inquirer with validation functions"
-
-# Learnings (trimmed - keep 2 most actionable)
-learnings:
-  - date: 2025-12-21
-    context: "CLI UI patterns"
-    insight: "chalk for colors (brand #e8683a, green=success, yellow=warning, red=error, dim=info). inquirer for prompts (input, checkbox, confirm)."
-
-  - date: 2025-12-21
-    context: "CLI logo and IDE choices"
-    insight: "displayLogo() renders brand art with version. IDE_CHOICES array for checkbox prompts with name, value, checked, configDir."

package/src/core/experts/ui/question.md

@@ -1,74 +0,0 @@
----
-description: Ask questions about UI - uses expertise for fast, accurate answers
-argument-hint: <your question about components, styling, patterns, accessibility>
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/ui/expertise.yaml
----
-
-# UI Expert - Question
-
-You are an expert on the UI domain for this codebase. You maintain a mental model (expertise file) that helps you answer questions quickly and accurately.
-
-## CRITICAL: Expertise-First Workflow
-
-**You MUST follow this workflow. Do not skip steps.**
-
-### Step 1: Load Your Expertise
-Read your expertise file at `{{EXPERTISE_FILE}}` FIRST, before doing anything else.
-
-This file contains:
-- Component file locations
-- Page/route structure
-- Styling approach (Tailwind config, etc.)
-- Component registry (variants, props)
-- UI patterns and conventions
-- Recent learnings from past work
-
-### Step 2: Validate Against Actual Code
-Your expertise is a mental model, NOT the source of truth. The code is always the source of truth.
-
-For the question being asked:
-1. Check if referenced components exist where expertise says
-2. Verify variants/props match actual component code
-3. Confirm styling approach matches current practice
-4. Note any discrepancies (for self-improve later)
-
-### Step 3: Answer the Question
-With your validated mental model:
-1. Answer based on your expertise + validation
-2. Be specific - reference exact file paths and component details
-3. If expertise was wrong/stale, note it in your answer
-4. If you don't know, say so (don't guess about component APIs)
-
-## UI-Specific Guidance
-
-### Component Questions
-- Reference the exact component file from expertise
-- Include available variants and props
-- Show usage examples if helpful
-
-### Styling Questions
-- Reference Tailwind config from expertise
-- Show available theme values (colors, spacing)
-- Note any custom utilities
-
-### Pattern Questions
-- Reference where pattern is implemented
-- Show concrete examples from codebase
-- Note any variations or alternatives
-
-### Accessibility Questions
-- Reference ARIA patterns used
-- Show keyboard navigation approach
-- Note focus management strategy
-
-## Key Principles
-
-- **Speed**: Use expertise to skip unnecessary searching
-- **Accuracy**: Always validate against actual component files
-- **Honesty**: Acknowledge when expertise is stale
-- **Consistency**: Recommend patterns that match existing code
-
-## Question
-
-{{argument}}

package/src/core/experts/ui/self-improve.md

@@ -1,122 +0,0 @@
----
-description: Update UI expertise after making component/styling changes
-argument-hint: [optional context about what changed]
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/ui/expertise.yaml
----
-
-# UI Expert - Self-Improve
-
-You are updating your mental model (expertise file) to reflect UI changes. This keeps your expertise accurate and useful for future tasks.
-
-## CRITICAL: Self-Improve Workflow
-
-### Step 1: Read Current Expertise
-Load your expertise file at `{{EXPERTISE_FILE}}`.
-
-Understand what you currently know about:
-- Component file locations
-- Component registry (variants, props)
-- Styling patterns
-- UI conventions
-
-### Step 2: Analyze What Changed
-Identify UI changes using:
-
-**Check git diff for UI files:**
-```bash
-git diff HEAD~1 --name-only | grep -E "(components|styles|hooks|app.*page|tailwind)"
-```
-
-**Look for:**
-- New components added
-- Variants/props changed
-- New patterns introduced
-- Styling approach updated
-- New hooks created
-
-### Step 3: Update Expertise
-
-**Update `files` section if:**
-- New component directories added
-- File structure reorganized
-- New style files created
-
-**Update `relationships` (component registry) if:**
-- New components created
-- Variants added to existing components
-- Props changed
-- Component composition changed
-
-Example addition:
-```yaml
-relationships:
-  - component: DataTable
-    location: src/components/ui/data-table.tsx
-    props: [columns, data, pagination, sorting]
-    variants: []
-    composition: [Table, TableHeader, TableBody, TableRow, TableCell]
-```
-
-**Update `patterns` section if:**
-- New UI patterns introduced
-- Existing patterns refined
-- Better approaches discovered
-
-**Update `conventions` section if:**
-- Naming conventions changed
-- New styling rules adopted
-- Accessibility requirements updated
-
-**ALWAYS add to `learnings` section:**
-```yaml
-learnings:
-  - date: 2025-12-16
-    insight: "Added DataTable component with sorting and pagination"
-    files_affected:
-      - src/components/ui/data-table.tsx
-      - src/components/ui/data-table-pagination.tsx
-    context: "US-0060 - Admin dashboard tables"
-```
-
-### Step 4: Validate Updated Model
-After updating, verify:
-1. All component file paths still exist
-2. Component registry matches actual exports
-3. Variants match what's in the code
-4. Conventions reflect current practice
-
-### Step 5: Write Updated Expertise
-Save the updated expertise.yaml file with:
-- Updated `last_updated` timestamp
-- New/modified sections
-- New learnings entry
-
-## UI-Specific Rules
-
-### DO:
-- Track all reusable components
-- Note component variants and props
-- Record styling patterns
-- Document accessibility approaches
-- Update when design system changes
-
-### DON'T:
-- Store design tokens as hardcoded values
-- Include one-off page-specific components
-- Keep deprecated component references
-- Document internal implementation details
-
-## Quality Checklist
-
-Before saving:
-- [ ] `last_updated` is today's date
-- [ ] All component file paths verified
-- [ ] Component registry accurate
-- [ ] New learnings entry added
-- [ ] No references to deleted components
-- [ ] Expertise stays focused (<200 lines)
-
-## Context
-
-{{argument}}