kodelyth-ecc 1.2.0

package/commands/e2e.md

@@ -0,0 +1,268 @@
+---
+description: Legacy slash-entry shim for the e2e-testing skill. Prefer the skill directly.
+---
+
+# E2E Command (Legacy Shim)
+
+Use this only if you still invoke `/e2e`. The maintained workflow lives in `skills/e2e-testing/SKILL.md`.
+
+## Canonical Surface
+
+- Prefer the `e2e-testing` skill directly.
+- Keep this file only as a compatibility entry point.
+
+## Arguments
+
+`$ARGUMENTS`
+
+## Delegation
+
+Apply the `e2e-testing` skill.
+- Generate or update Playwright coverage for the requested user flow.
+- Run only the relevant tests unless the user explicitly asked for the entire suite.
+- Capture the usual artifacts and report failures, flake risk, and next fixes without duplicating the full skill body here.
+    await marketsPage.searchMarkets('xyznonexistentmarket123456')
+
+    // Verify empty state
+    await expect(page.locator('[data-testid="no-results"]')).toBeVisible()
+    await expect(page.locator('[data-testid="no-results"]')).toContainText(
+      /no.*results|no.*markets/i
+    )
+
+    const marketCount = await marketsPage.marketCards.count()
+    expect(marketCount).toBe(0)
+  })
+
+  test('can clear search and see all markets again', async ({ page }) => {
+    const marketsPage = new MarketsPage(page)
+    await marketsPage.goto()
+
+    // Initial market count
+    const initialCount = await marketsPage.marketCards.count()
+
+    // Perform search
+    await marketsPage.searchMarkets('trump')
+    await page.waitForLoadState('networkidle')
+
+    // Verify filtered results
+    const filteredCount = await marketsPage.marketCards.count()
+    expect(filteredCount).toBeLessThan(initialCount)
+
+    // Clear search
+    await marketsPage.searchInput.clear()
+    await page.waitForLoadState('networkidle')
+
+    // Verify all markets shown again
+    const finalCount = await marketsPage.marketCards.count()
+    expect(finalCount).toBe(initialCount)
+  })
+})
+```
+
+## Running Tests
+
+```bash
+# Run the generated test
+npx playwright test tests/e2e/markets/search-and-view.spec.ts
+
+Running 3 tests using 3 workers
+
+  ✓  [chromium] › search-and-view.spec.ts:5:3 › user can search markets and view details (4.2s)
+  ✓  [chromium] › search-and-view.spec.ts:52:3 › search with no results shows empty state (1.8s)
+  ✓  [chromium] › search-and-view.spec.ts:67:3 › can clear search and see all markets again (2.9s)
+
+  3 passed (9.1s)
+
+Artifacts generated:
+- artifacts/search-results.png
+- artifacts/market-details.png
+- playwright-report/index.html
+```
+
+## Test Report
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║                    E2E Test Results                          ║
+╠══════════════════════════════════════════════════════════════╣
+║ Status:     PASS: ALL TESTS PASSED                              ║
+║ Total:      3 tests                                          ║
+║ Passed:     3 (100%)                                         ║
+║ Failed:     0                                                ║
+║ Flaky:      0                                                ║
+║ Duration:   9.1s                                             ║
+╚══════════════════════════════════════════════════════════════╝
+
+Artifacts:
+ Screenshots: 2 files
+ Videos: 0 files (only on failure)
+ Traces: 0 files (only on failure)
+ HTML Report: playwright-report/index.html
+
+View report: npx playwright show-report
+```
+
+PASS: E2E test suite ready for CI/CD integration!
+```
+
+## Test Artifacts
+
+When tests run, the following artifacts are captured:
+
+**On All Tests:**
+- HTML Report with timeline and results
+- JUnit XML for CI integration
+
+**On Failure Only:**
+- Screenshot of the failing state
+- Video recording of the test
+- Trace file for debugging (step-by-step replay)
+- Network logs
+- Console logs
+
+## Viewing Artifacts
+
+```bash
+# View HTML report in browser
+npx playwright show-report
+
+# View specific trace file
+npx playwright show-trace artifacts/trace-abc123.zip
+
+# Screenshots are saved in artifacts/ directory
+open artifacts/search-results.png
+```
+
+## Flaky Test Detection
+
+If a test fails intermittently:
+
+```
+WARNING:  FLAKY TEST DETECTED: tests/e2e/markets/trade.spec.ts
+
+Test passed 7/10 runs (70% pass rate)
+
+Common failure:
+"Timeout waiting for element '[data-testid="confirm-btn"]'"
+
+Recommended fixes:
+1. Add explicit wait: await page.waitForSelector('[data-testid="confirm-btn"]')
+2. Increase timeout: { timeout: 10000 }
+3. Check for race conditions in component
+4. Verify element is not hidden by animation
+
+Quarantine recommendation: Mark as test.fixme() until fixed
+```
+
+## Browser Configuration
+
+Tests run on multiple browsers by default:
+- PASS: Chromium (Desktop Chrome)
+- PASS: Firefox (Desktop)
+- PASS: WebKit (Desktop Safari)
+- PASS: Mobile Chrome (optional)
+
+Configure in `playwright.config.ts` to adjust browsers.
+
+## CI/CD Integration
+
+Add to your CI pipeline:
+
+```yaml
+# .github/workflows/e2e.yml
+- name: Install Playwright
+  run: npx playwright install --with-deps
+
+- name: Run E2E tests
+  run: npx playwright test
+
+- name: Upload artifacts
+  if: always()
+  uses: actions/upload-artifact@v3
+  with:
+    name: playwright-report
+    path: playwright-report/
+```
+
+## PMX-Specific Critical Flows
+
+For PMX, prioritize these E2E tests:
+
+**CRITICAL (Must Always Pass):**
+1. User can connect wallet
+2. User can browse markets
+3. User can search markets (semantic search)
+4. User can view market details
+5. User can place trade (with test funds)
+6. Market resolves correctly
+7. User can withdraw funds
+
+**IMPORTANT:**
+1. Market creation flow
+2. User profile updates
+3. Real-time price updates
+4. Chart rendering
+5. Filter and sort markets
+6. Mobile responsive layout
+
+## Best Practices
+
+**DO:**
+- PASS: Use Page Object Model for maintainability
+- PASS: Use data-testid attributes for selectors
+- PASS: Wait for API responses, not arbitrary timeouts
+- PASS: Test critical user journeys end-to-end
+- PASS: Run tests before merging to main
+- PASS: Review artifacts when tests fail
+
+**DON'T:**
+- FAIL: Use brittle selectors (CSS classes can change)
+- FAIL: Test implementation details
+- FAIL: Run tests against production
+- FAIL: Ignore flaky tests
+- FAIL: Skip artifact review on failures
+- FAIL: Test every edge case with E2E (use unit tests)
+
+## Important Notes
+
+**CRITICAL for PMX:**
+- E2E tests involving real money MUST run on testnet/staging only
+- Never run trading tests against production
+- Set `test.skip(process.env.NODE_ENV === 'production')` for financial tests
+- Use test wallets with small test funds only
+
+## Integration with Other Commands
+
+- Use `/plan` to identify critical journeys to test
+- Use `/tdd` for unit tests (faster, more granular)
+- Use `/e2e` for integration and user journey tests
+- Use `/code-review` to verify test quality
+
+## Related Agents
+
+This command invokes the `e2e-runner` agent provided by ECC.
+
+For manual installs, the source file lives at:
+`agents/e2e-runner.md`
+
+## Quick Commands
+
+```bash
+# Run all E2E tests
+npx playwright test
+
+# Run specific test file
+npx playwright test tests/e2e/markets/search.spec.ts
+
+# Run in headed mode (see browser)
+npx playwright test --headed
+
+# Debug test
+npx playwright test --debug
+
+# Generate test code
+npx playwright codegen http://localhost:3000
+
+# View report
+npx playwright show-report
+```

package/commands/eval.md

@@ -0,0 +1,23 @@
+---
+description: Legacy slash-entry shim for the eval-harness skill. Prefer the skill directly.
+---
+
+# Eval Command (Legacy Shim)
+
+Use this only if you still invoke `/eval`. The maintained workflow lives in `skills/eval-harness/SKILL.md`.
+
+## Canonical Surface
+
+- Prefer the `eval-harness` skill directly.
+- Keep this file only as a compatibility entry point.
+
+## Arguments
+
+`$ARGUMENTS`
+
+## Delegation
+
+Apply the `eval-harness` skill.
+- Support the same user intents as before: define, check, report, list, and cleanup.
+- Keep evals capability-first, regression-backed, and evidence-based.
+- Use the skill as the canonical evaluator instead of maintaining a separate command-specific playbook.

package/commands/evolve.md

@@ -0,0 +1,178 @@
+---
+name: evolve
+description: Analyze instincts and suggest or generate evolved structures
+command: true
+---
+
+# Evolve Command
+
+## Implementation
+
+Run the instinct CLI using the plugin root path:
+
+```bash
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate]
+```
+
+Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):
+
+```bash
+python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]
+```
+
+Analyzes instincts and clusters related ones into higher-level structures:
+- **Commands**: When instincts describe user-invoked actions
+- **Skills**: When instincts describe auto-triggered behaviors
+- **Agents**: When instincts describe complex, multi-step processes
+
+## Usage
+
+```
+/evolve                    # Analyze all instincts and suggest evolutions
+/evolve --generate         # Also generate files under evolved/{skills,commands,agents}
+```
+
+## Evolution Rules
+
+### → Command (User-Invoked)
+When instincts describe actions a user would explicitly request:
+- Multiple instincts about "when user asks to..."
+- Instincts with triggers like "when creating a new X"
+- Instincts that follow a repeatable sequence
+
+Example:
+- `new-table-step1`: "when adding a database table, create migration"
+- `new-table-step2`: "when adding a database table, update schema"
+- `new-table-step3`: "when adding a database table, regenerate types"
+
+→ Creates: **new-table** command
+
+### → Skill (Auto-Triggered)
+When instincts describe behaviors that should happen automatically:
+- Pattern-matching triggers
+- Error handling responses
+- Code style enforcement
+
+Example:
+- `prefer-functional`: "when writing functions, prefer functional style"
+- `use-immutable`: "when modifying state, use immutable patterns"
+- `avoid-classes`: "when designing modules, avoid class-based design"
+
+→ Creates: `functional-patterns` skill
+
+### → Agent (Needs Depth/Isolation)
+When instincts describe complex, multi-step processes that benefit from isolation:
+- Debugging workflows
+- Refactoring sequences
+- Research tasks
+
+Example:
+- `debug-step1`: "when debugging, first check logs"
+- `debug-step2`: "when debugging, isolate the failing component"
+- `debug-step3`: "when debugging, create minimal reproduction"
+- `debug-step4`: "when debugging, verify fix with test"
+
+→ Creates: **debugger** agent
+
+## What to Do
+
+1. Detect current project context
+2. Read project + global instincts (project takes precedence on ID conflicts)
+3. Group instincts by trigger/domain patterns
+4. Identify:
+   - Skill candidates (trigger clusters with 2+ instincts)
+   - Command candidates (high-confidence workflow instincts)
+   - Agent candidates (larger, high-confidence clusters)
+5. Show promotion candidates (project -> global) when applicable
+6. If `--generate` is passed, write files to:
+   - Project scope: `~/.claude/homunculus/projects/<project-id>/evolved/`
+   - Global fallback: `~/.claude/homunculus/evolved/`
+
+## Output Format
+
+```
+============================================================
+  EVOLVE ANALYSIS - 12 instincts
+  Project: my-app (a1b2c3d4e5f6)
+  Project-scoped: 8 | Global: 4
+============================================================
+
+High confidence instincts (>=80%): 5
+
+## SKILL CANDIDATES
+1. Cluster: "adding tests"
+   Instincts: 3
+   Avg confidence: 82%
+   Domains: testing
+   Scopes: project
+
+## COMMAND CANDIDATES (2)
+  /adding-tests
+    From: test-first-workflow [project]
+    Confidence: 84%
+
+## AGENT CANDIDATES (1)
+  adding-tests-agent
+    Covers 3 instincts
+    Avg confidence: 82%
+```
+
+## Flags
+
+- `--generate`: Generate evolved files in addition to analysis output
+
+## Generated File Format
+
+### Command
+```markdown
+---
+name: new-table
+description: Create a new database table with migration, schema update, and type generation
+command: /new-table
+evolved_from:
+  - new-table-migration
+  - update-schema
+  - regenerate-types
+---
+
+# New Table Command
+
+[Generated content based on clustered instincts]
+
+## Steps
+1. ...
+2. ...
+```
+
+### Skill
+```markdown
+---
+name: functional-patterns
+description: Enforce functional programming patterns
+evolved_from:
+  - prefer-functional
+  - use-immutable
+  - avoid-classes
+---
+
+# Functional Patterns Skill
+
+[Generated content based on clustered instincts]
+```
+
+### Agent
+```markdown
+---
+name: debugger
+description: Systematic debugging agent
+model: sonnet
+evolved_from:
+  - debug-check-logs
+  - debug-isolate
+  - debug-reproduce
+---
+
+# Debugger Agent
+
+[Generated content based on clustered instincts]
+```

package/commands/feature-dev.md

@@ -0,0 +1,49 @@
+---
+description: Guided feature development with codebase understanding and architecture focus
+---
+
+A structured feature-development workflow that emphasizes understanding existing code before writing new code.
+
+## Phases
+
+### 1. Discovery
+
+- read the feature request carefully
+- identify requirements, constraints, and acceptance criteria
+- ask clarifying questions if the request is ambiguous
+
+### 2. Codebase Exploration
+
+- use `code-explorer` to analyze the relevant existing code
+- trace execution paths and architecture layers
+- understand integration points and conventions
+
+### 3. Clarifying Questions
+
+- present findings from exploration
+- ask targeted design and edge-case questions
+- wait for user response before proceeding
+
+### 4. Architecture Design
+
+- use `code-architect` to design the feature
+- provide the implementation blueprint
+- wait for approval before implementing
+
+### 5. Implementation
+
+- implement the feature following the approved design
+- prefer TDD where appropriate
+- keep commits small and focused
+
+### 6. Quality Review
+
+- use `code-reviewer` to review the implementation
+- address critical and important issues
+- verify test coverage
+
+### 7. Summary
+
+- summarize what was built
+- list follow-up items or limitations
+- provide testing instructions

package/commands/flutter-build.md

@@ -0,0 +1,164 @@
+---
+description: Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
+---
+
+# Flutter Build and Fix
+
+This command invokes the **dart-build-resolver** agent to incrementally fix Dart/Flutter build errors with minimal changes.
+
+## What This Command Does
+
+1. **Run Diagnostics**: Execute `flutter analyze`, `flutter pub get`
+2. **Parse Errors**: Group by file and sort by severity
+3. **Fix Incrementally**: One error at a time
+4. **Verify Each Fix**: Re-run analysis after each change
+5. **Report Summary**: Show what was fixed and what remains
+
+## When to Use
+
+Use `/flutter-build` when:
+- `flutter analyze` reports errors
+- `flutter build` fails for any platform
+- `dart pub get` / `flutter pub get` fails with version conflicts
+- `build_runner` fails to generate code
+- After pulling changes that break the build
+
+## Diagnostic Commands Run
+
+```bash
+# Analysis
+flutter analyze 2>&1
+
+# Dependencies
+flutter pub get 2>&1
+
+# Code generation (if project uses build_runner)
+dart run build_runner build --delete-conflicting-outputs 2>&1
+
+# Platform builds
+flutter build apk 2>&1
+flutter build web 2>&1
+```
+
+## Example Session
+
+````text
+User: /flutter-build
+
+Agent:
+# Flutter Build Resolution
+
+## Initial Diagnostics
+
+```
+$ flutter analyze
+Analyzing project...
+
+  error • lib/features/user/data/user_repository_impl.dart:34:16 •
+    A value of type 'String?' can't be assigned to a variable of type 'String'. •
+    invalid_assignment
+
+  error • lib/features/cart/presentation/cart_page.dart:58:5 •
+    The method 'add' isn't defined for the type 'List<Item>'.
+    Try correcting the name to the name of an existing method, or defining a method named 'add'. •
+    undefined_method
+
+2 errors found.
+```
+
+## Fix 1: Null Safety
+
+File: lib/features/user/data/user_repository_impl.dart:34
+Error: A value of type 'String?' can't be assigned to type 'String'
+
+Changed:
+```dart
+final id = response.id;
+```
+To:
+```dart
+final id = response.id ?? '';
+```
+
+```
+$ flutter analyze
+1 error found.
+```
+
+## Fix 2: Immutable List
+
+File: lib/features/cart/presentation/cart_page.dart:58
+Error: The method 'add' isn't defined for the type 'List<Item>'
+Cause: State holds an unmodifiable list; mutation goes through Cubit
+
+Changed:
+```dart
+state.items.add(item);
+```
+To:
+```dart
+context.read<CartCubit>().addItem(item);
+// Note: Cubit exposes named methods (addItem, removeItem);
+// .add(event) is the BLoC event API — don't mix them.
+```
+
+```
+$ flutter analyze
+No issues found!
+```
+
+## Final Verification
+
+```
+$ flutter test
+All tests passed.
+```
+
+## Summary
+
+| Metric | Count |
+|--------|-------|
+| Analysis errors fixed | 2 |
+| Files modified | 2 |
+| Remaining issues | 0 |
+
+Build Status: PASS ✓
+````
+
+## Common Errors Fixed
+
+| Error | Typical Fix |
+|-------|-------------|
+| `A value of type 'X?' can't be assigned to 'X'` | Add `?? default` or null guard |
+| `The name 'X' isn't defined` | Add import or fix typo |
+| `Non-nullable instance field must be initialized` | Add initializer or `late` |
+| `Version solving failed` | Adjust version constraints in pubspec.yaml |
+| `Missing concrete implementation of 'X'` | Implement missing interface method |
+| `build_runner: Part of X expected` | Delete stale `.g.dart` and rebuild |
+
+## Fix Strategy
+
+1. **Analysis errors first** — code must be error-free
+2. **Warning triage second** — fix warnings that could cause runtime bugs
+3. **pub conflicts third** — fix dependency resolution
+4. **One fix at a time** — verify each change
+5. **Minimal changes** — don't refactor, just fix
+
+## Stop Conditions
+
+The agent will stop and report if:
+- Same error persists after 3 attempts
+- Fix introduces more errors
+- Requires architectural changes
+- Package upgrade conflicts need user decision
+
+## Related Commands
+
+- `/flutter-test` — Run tests after build succeeds
+- `/flutter-review` — Review code quality
+- `/verify` — Full verification loop
+
+## Related
+
+- Agent: `agents/dart-build-resolver.md`
+- Skill: `skills/flutter-dart-code-review/`