@pennyfarthing/core 6.6.0

package/pennyfarthing-dist/skills/sprint-context/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: sprint-context
+description: Sprint status, backlog, and story management for Conductor. Use when checking current sprint status, finding available stories, reviewing backlog, or understanding story context and history.
+---
+
+# Sprint Context Skill - Conductor Project
+
+## When to Use This Skill
+
+- Checking current sprint status
+- Finding available stories in backlog
+- Understanding story context and history
+- Reviewing completed work
+- Sprint planning and retrospectives
+
+## Sprint File Locations
+
+| File | Purpose |
+|------|---------|
+| `sprint/current-sprint.yaml` | Active sprint with all stories |
+| `sprint/backlog.yaml` | Future epics and stories |
+| `sprint/completed.yaml` | Archived completed work |
+| `sprint/context/epic-*-summary.md` | Epic-level context summaries |
+| `sprint/context/story-*-summary.md` | Story-level context summaries |
+| `sprint/archive/*.md` | Archived session files |
+
+## Quick Reference
+
+### Check Sprint Status
+```bash
+cat sprint/current-sprint.yaml
+```
+
+### Find Available Stories
+```bash
+# Stories ready for work
+grep -B2 -A5 "status: backlog\|status: ready" sprint/current-sprint.yaml
+```
+
+### Check Story Context
+```bash
+# Epic context
+cat sprint/context/epic-{N}-summary.md
+
+# Story context
+cat sprint/context/story-{X-Y}-summary.md
+```
+
+### Find Related Work
+```bash
+# Search archive for related stories
+grep -r "keyword" sprint/archive/
+grep -r "keyword" sprint/context/
+```
+
+## Sprint YAML Structure
+
+```yaml
+sprint:
+  number: 38
+  goal: "Sprint goal description"
+  start_date: 2025-01-06
+  end_date: 2025-01-17
+
+epics:
+  - id: epic-32
+    title: "Epic Title"
+    stories:
+      - id: "32-1"
+        description: "Story title"
+        points: 3
+        priority: P1
+        status: done | in-progress | backlog | ready
+        repos: api | ui | both
+        jira: MSSCI-12345
+```
+
+## Story Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `backlog` | Not started, available for work |
+| `ready` | Groomed, ready to start |
+| `in-progress` | Currently being worked |
+| `review` | PR created, awaiting review |
+| `approved` | Review passed, ready to finish |
+| `done` | Completed and archived |
+
+## Context File Patterns
+
+### Epic Summary (`sprint/context/epic-{N}-summary.md`)
+- What the epic accomplishes
+- Key technical decisions across stories
+- Patterns established
+- Remaining work
+
+### Story Summary (`sprint/context/story-{X-Y}-summary.md`)
+- What was built
+- Key technical decisions
+- Implementation patterns
+- Files modified
+- Lessons learned
+
+## Common Tasks
+
+### Starting New Work
+1. Check `sprint/current-sprint.yaml` for available stories
+2. Look for `status: backlog` or `status: ready`
+3. Check for epic context in `sprint/context/`
+4. Review related archived work if needed
+
+### Finishing Work
+1. Update story status in `sprint/current-sprint.yaml`
+2. Create story summary in `sprint/context/`
+3. Archive session file to `sprint/archive/`
+
+### Sprint Planning
+1. Review `sprint/backlog.yaml` for upcoming work
+2. Check `sprint/completed.yaml` for velocity reference
+3. Review epic summaries for context

package/pennyfarthing-dist/skills/story-management/SKILL.md

@@ -0,0 +1,208 @@
+---
+name: story-management
+description: Story creation, sizing, and sprint management patterns for Conductor. Use when creating stories, estimating work, or managing the sprint workflow.
+---
+
+# Story Management Skill - Conductor Project
+
+## Overview
+
+This skill covers story creation, sizing, and management patterns for the Conductor project sprint workflow.
+
+## Story Sizing Guidelines
+
+### 1-2 Points (Trivial)
+
+- Single file change
+- Config update
+- Simple bug fix
+- No new tests needed
+- **Skip TEA, go directly to Dev**
+- **Example:** Fix typo, update env variable
+
+### 3 Points (Small)
+
+- Few files changed
+- Single component/handler
+- Straightforward implementation
+- Some tests needed
+- **Example:** Add validation, fix authorization bug
+
+### 5 Points (Medium)
+
+- Multiple files across layers
+- New feature component
+- API + UI changes
+- Comprehensive tests
+- **Example:** New admin page, new API endpoint
+
+### 8 Points (Large)
+
+- Significant feature
+- Multiple components
+- Database changes
+- Cross-repo coordination
+- **Example:** New integration, major refactor
+
+### 13+ Points (Epic-level)
+
+- **SPLIT THIS STORY**
+- Too complex for single story
+- Multiple unknowns
+- Break into 3-5 smaller stories
+
+## Story Templates
+
+### Bug Fix Story
+
+```yaml
+35-N-short-description:
+  status: backlog
+  points: 2-3
+  repos: api|ui|both
+  priority: P0-P2
+  description: "[Symptom] - [Root cause if known]"
+  error_details:
+    symptom: "What user sees"
+    error: "Error message"
+    affected: "Pages/endpoints affected"
+  ac:
+    - "Bug no longer occurs"
+    - "Regression test added"
+    - "Related code audited for same issue"
+```
+
+### Feature Story
+
+```yaml
+35-N-short-description:
+  status: backlog
+  points: 5-8
+  repos: api|ui|both
+  priority: P1-P2
+  description: "User can [action] to [benefit]"
+  ac:
+    - "Feature works as specified"
+    - "UI matches design"
+    - "API documented"
+    - "Tests cover happy path and edge cases"
+    - "Error handling implemented"
+```
+
+### Refactor Story
+
+```yaml
+35-N-short-description:
+  status: backlog
+  points: 3-5
+  repos: api|ui
+  priority: P2
+  description: "Refactor [component] to [improvement]"
+  ac:
+    - "All existing tests pass"
+    - "No behavior changes"
+    - "Code follows new pattern"
+    - "Documentation updated"
+```
+
+## Acceptance Criteria Patterns
+
+### Good AC (SMART)
+
+- "Admin users can access /admin/settings without 403"
+- "API returns 204 No Content on successful DELETE"
+- "Selected client persists in URL query param"
+- "Tests cover admin, manager, analyst roles"
+
+### Bad AC (Vague)
+
+- "Feature works correctly"
+- "No bugs"
+- "Good performance"
+- "User-friendly"
+
+## Priority Guidelines
+
+| Priority | Meaning | SLA |
+|----------|---------|-----|
+| P0 | Production blocker | Same day |
+| P1 | High impact bug/feature | This sprint |
+| P2 | Normal priority | Next sprint OK |
+| P3 | Nice to have | Backlog |
+
+## Cross-Repo Patterns
+
+### API-First Pattern
+
+1. **Story A (API):** Implement backend endpoint
+2. **Story B (UI):** Implement frontend consuming endpoint
+
+### Full-Stack Pattern
+
+1. Single story with `repos: both`
+2. AC covers both API and UI
+3. TEA writes tests for both
+
+## Scale-Adaptive Workflow
+
+Based on story complexity, determine workflow depth:
+
+| Points | Scale | Workflow | Handoff |
+|--------|-------|----------|---------|
+| 1-2 | Trivial | Skip TEA for chores | SM -> Dev directly |
+| 3-5 | Standard | Full TDD flow | SM -> TEA -> Dev |
+| 8+ | Complex | Add Architect review | SM -> Architect -> TEA -> Dev |
+
+## Sprint File Locations
+
+| File | Purpose |
+|------|---------|
+| `sprint/current-sprint.yaml` | Active stories only |
+| `sprint/backlog.yaml` | Future epics/stories |
+| `sprint/completed.yaml` | Done work archive |
+| `sprint/archive/story-X-Y-*.md` | Detailed session archives |
+| `sprint/context/story-X-Y-summary.md` | Quick context summaries |
+
+## Story Key Format
+
+- **Conductor:** `epic-N`, `N-M` stories (e.g., `epic-35`, `35-4`)
+- **Siemulator:** `sim-epic-N`, `sim-N-M` stories (e.g., `sim-epic-10`, `sim-10-1`)
+
+## Lessons Learned
+
+### Authorization Stories
+
+- Always audit related endpoints for same issue
+- Add tests for admin, manager, analyst roles
+- Use centralized utility pattern
+
+### UI Stories
+
+- Check for client selector needs (multi-client users)
+- Verify route configuration
+- Add E2E test for navigation
+
+### Integration Stories
+
+- Plan for mock infrastructure
+- Consider retry/timeout handling
+- Document external dependencies
+
+## Workflow Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/new-work` | Start a new story (SM -> TEA -> Dev) |
+| `/start-epic` | Generate epic technical context |
+
+**Note:** Session completion is handled via `/sm` (finish-story task). Agents auto-detect active work on activation.
+
+## Jira Integration
+
+```bash
+# Claim a story before starting
+./scripts/jira-claim-story.sh 35-4-checklist-configuration-ui --claim
+
+# Sync sprint to Jira
+./scripts/sync-epic-to-jira.sh 35 --with-comments
+```

package/pennyfarthing-dist/skills/testing/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: testing
+description: Test commands and patterns for TDD workflow. This skill should be used when running tests, debugging test failures, setting up test infrastructure, or writing new tests. Provides framework-agnostic patterns that projects customize.
+---
+
+# Testing Skill
+
+## When to Use This Skill
+
+- Running tests (backend, frontend, or all)
+- Debugging test failures
+- Setting up test containers/infrastructure
+- Writing new tests
+- Pre-commit verification
+- Understanding TDD workflow
+
+## TDD Workflow (RED → GREEN → REFACTOR)
+
+```
+1. TEA writes failing tests (RED)
+2. Dev implements code to pass tests (GREEN)
+3. Dev refactors while keeping tests GREEN
+4. Reviewer validates quality
+```
+
+## Quick Reference
+
+```bash
+# Setup test infrastructure (run once per session)
+# Project-specific: check your justfile or package.json
+
+# Run all tests
+just test              # If using just
+npm test               # If using npm
+go test ./...          # If using Go directly
+
+# Run specific test patterns
+just test-api -run "TestName"     # Go pattern
+npm test -- -t "test name"        # Jest/Vitest pattern
+```
+
+## Test Command Patterns
+
+### Go (Backend)
+
+```bash
+# Run all tests
+go test ./...
+
+# Run tests in specific package
+go test ./internal/handlers
+
+# Run tests matching pattern
+go test -run "TestCreate" ./...
+
+# Verbose output
+go test -v ./internal/handlers
+
+# With coverage
+go test -cover ./...
+```
+
+### Node/React (Frontend)
+
+```bash
+# Run all tests (Vitest)
+npm test
+
+# Run tests matching pattern
+npm test -- -t "button"
+
+# Watch mode
+npm test -- --watch
+
+# Coverage
+npm test -- --coverage
+```
+
+## Test File Naming Conventions
+
+| Type | Go Pattern | TypeScript Pattern |
+|------|------------|-------------------|
+| Unit test | `*_test.go` | `*.test.ts`, `*.test.tsx` |
+| Integration | `*_integration_test.go` | `*.integration.test.ts` |
+| E2E | N/A | `*.e2e.test.ts` |
+
+## Reference Documentation
+
+- **Troubleshooting:** See `references/troubleshooting.md`
+- **TDD Policy:** See `references/tdd-policy.md` (project-specific)
+- **Backend Patterns:** See `references/backend-patterns.md` (project-specific)
+- **Frontend Patterns:** See `references/frontend-patterns.md` (project-specific)
+
+## Project Customization
+
+Projects should create their own testing skill in `.claude/project/skills/testing/` with:
+- Project-specific test commands
+- Custom patterns and conventions
+- Infrastructure setup instructions

package/pennyfarthing-dist/skills/testing/references/troubleshooting.md

@@ -0,0 +1,124 @@
+# Test Troubleshooting Guide
+
+## Tests Timing Out
+
+```bash
+# Ensure test infrastructure is running
+just test-setup        # Or project-specific setup command
+
+# Check container status
+docker ps
+
+# Increase timeout if needed
+go test -timeout 60s ./...
+```
+
+## "No Tests to Run" Message
+
+### Go Tests
+
+The `-run` flag filters by **test function name**, not by file or domain:
+- `-run "User"` matches `TestUserCreate` but NOT `TestCreateAccount`
+- The pattern is a regex, case-sensitive
+
+```bash
+# Run ALL tests in a package (no name filter)
+go test ./internal/handlers/...
+
+# Run tests with "Create" in name in specific package
+go test -run "Create" ./internal/handlers
+```
+
+### JavaScript/TypeScript Tests
+
+The `-t` flag filters by test description:
+
+```bash
+# Run tests matching description
+npm test -- -t "should create user"
+
+# Run all tests in a file
+npm test -- path/to/file.test.ts
+```
+
+## Case Sensitivity
+
+### Go
+- `-run "User"` - Correct (matches TestUser...)
+- `-run "user"` - Won't match (Go regex is case-sensitive)
+
+### Jest/Vitest
+- `-t "user"` - Case-insensitive by default
+
+## Package/Path Format
+
+### Go
+```bash
+./internal/handlers      # Correct - relative with ./
+internal/handlers        # May not work without ./
+./internal/handlers/...  # Include subpackages
+```
+
+### Node
+```bash
+src/components           # Relative path
+./src/components         # Also works
+```
+
+## Tests Passing Locally but Failing in CI
+
+1. **Environment differences** - Check env vars
+2. **Race conditions** - Run tests multiple times locally
+3. **Database state** - Ensure clean state between tests
+
+```bash
+# Run full test suite to catch integration issues
+just test
+
+# Run tests with race detection (Go)
+go test -race ./...
+```
+
+## Container Issues
+
+```bash
+# Restart test containers
+docker-compose -f docker-compose.test.yml down
+docker-compose -f docker-compose.test.yml up -d
+
+# Check container logs
+docker logs <container-name>
+
+# Verify connectivity
+docker exec <container-name> pg_isready  # Postgres
+docker exec <container-name> redis-cli ping  # Redis
+```
+
+## Database Connection Errors
+
+```bash
+# Check environment variables
+echo $TEST_DATABASE_URL
+
+# Verify database is accepting connections
+psql $TEST_DATABASE_URL -c "SELECT 1"
+```
+
+## Common Patterns
+
+### Flaky Tests
+
+1. Check for timing dependencies
+2. Look for shared state between tests
+3. Ensure proper cleanup in teardown
+4. Consider using test isolation
+
+### Memory Issues
+
+```bash
+# Run with memory limit (Go)
+go test -memprofile mem.out ./...
+
+# Check for goroutine leaks
+go test -race ./...
+```

package/pennyfarthing-dist/skills/theme/skill.md

@@ -0,0 +1,129 @@
+---
+name: theme
+description: Manage persona themes - list available themes, show current/specific theme details, and set active theme. Use for all theme-related operations.
+---
+
+# Theme Management Skill
+
+## Overview
+
+Pennyfarthing uses themed personas to give each agent a unique character. This skill provides commands to list, view, and change themes.
+
+## Quick Reference
+
+| Action | Command |
+|--------|---------|
+| List all themes | `/list-themes` or see below |
+| Show current theme | `/show-theme` |
+| Show specific theme | `/show-theme <name>` |
+| Set active theme | `/set-theme <name>` |
+| Create new theme | `/theme-maker` (interactive) |
+
+## List Available Themes
+
+To see all available themes:
+
+```bash
+ls pennyfarthing-dist/personas/themes/*.yaml | xargs -I{} basename {} .yaml | sort
+```
+
+To show the current theme:
+
+```bash
+cat .pennyfarthing/config.local.yaml 2>/dev/null || echo "No theme configured"
+```
+
+## Show Theme Details
+
+To display a theme's agent mappings:
+
+```bash
+# Show current theme
+THEME=$(cat .pennyfarthing/config.local.yaml 2>/dev/null | grep "^theme:" | cut -d'"' -f2)
+cat pennyfarthing-dist/personas/themes/${THEME}.yaml
+```
+
+Or for a specific theme:
+
+```bash
+cat pennyfarthing-dist/personas/themes/<theme-name>.yaml
+```
+
+## Set Active Theme
+
+To change the active theme:
+
+1. Verify theme exists:
+   ```bash
+   ls pennyfarthing-dist/personas/themes/<name>.yaml
+   ```
+
+2. Read current config:
+   ```bash
+   cat .pennyfarthing/config.local.yaml 2>/dev/null || echo "FILE_NOT_FOUND"
+   ```
+
+3. Update `.pennyfarthing/config.local.yaml`:
+   - If file exists with `theme:` line: Use Edit tool to replace `theme: <old>` with `theme: <new>`
+   - If file missing or no theme line: Use Write tool to create:
+     ```yaml
+     # Pennyfarthing Local Configuration
+     theme: <name>
+     ```
+
+4. Verify the write succeeded:
+   ```bash
+   cat .pennyfarthing/config.local.yaml
+   ```
+
+5. Start a new agent session to use the new theme
+
+## Theme File Locations
+
+| Location | Purpose |
+|----------|---------|
+| `pennyfarthing-dist/personas/themes/` | Built-in themes (96+) |
+| `.claude/pennyfarthing/themes/` | User-created custom themes |
+| `.pennyfarthing/config.local.yaml` | Theme selection (agent-writable, gitignored) |
+
+## Theme Structure
+
+Each theme YAML defines agents with:
+
+```yaml
+theme:
+  name: theme-name
+  description: Brief description
+
+agents:
+  sm:
+    character: Character Name
+    style: Communication style description
+    quote: Signature quote
+    trait: Key personality trait
+    helper: Helper/assistant description
+  tea:
+    # ...same structure...
+  dev:
+    # ...
+```
+
+## Creating Custom Themes
+
+For creating new themes, use `/theme-maker` which provides:
+- **AI-Driven Mode**: Describe a concept, AI generates all personas
+- **Guided Mode**: Pick from AI-suggested characters
+- **Manual Mode**: Specify every detail yourself
+
+See the `theme-creation` skill for full documentation.
+
+## Common Theme Categories
+
+Themes are available across many categories:
+- **TV/Film**: star-trek-tos, star-trek-tng, breaking-bad, the-wire, firefly, etc.
+- **Literature**: shakespeare, jane-austen, dickens, discworld, dune, etc.
+- **Historical**: ancient-philosophers, military-commanders, renaissance-masters, etc.
+- **Mythology**: greek-mythology, norse-mythology, arthurian-mythos, etc.
+- **Animated**: futurama, the-simpsons, avatar-the-last-airbender, etc.
+
+Run the list command to see all 96+ available themes.