@pennyfarthing/core 9.2.0 → 9.3.0

package/pennyfarthing-dist/workflows/project-setup/steps/step-06-task-runner.md

@@ -1,279 +0,0 @@
-# Step 6: Create Task Runner (justfile/Makefile)
-
-<purpose>
-Create a justfile or Makefile in the orchestrator that proxies commands to subrepos, providing a single entry point for common operations.
-</purpose>
-
-<instructions>
-1. Detect existing task runners (justfile, Makefile, package.json scripts)
-2. Generate task runner with recipes for all subrepos
-3. Include common orchestrator patterns (test all, build all, dev)
-4. Allow user to customize recipes
-5. Write to project root
-</instructions>
-
-<output>
-- justfile or Makefile created/updated
-- Recipes for each subrepo
-- Common orchestrator commands (test-all, build-all, dev)
-- User has approved the configuration
-</output>
-
-## TASK RUNNER DETECTION
-
-Check for existing task runners:
-
-```bash
-ls -la justfile Justfile Makefile makefile package.json 2>/dev/null
-```
-
-### Prefer justfile over Makefile
-
-**Why justfile:**
-- Modern syntax, easier to read
-- Better error messages
-- Cross-platform (Windows support)
-- Native variables and interpolation
-- Recipes are isolated by default
-
-## JUSTFILE STRUCTURE FOR ORCHESTRATORS
-
-```just
-# justfile for {project_name}
-# Generated by Pennyfarthing project-setup workflow
-
-# Default recipe - show help
-default:
-    @just --list
-
-# ============================================
-# ALL REPOS
-# ============================================
-
-# Run tests in all repos
-test-all:
-    @echo "Testing all repos..."
-    just test-api
-    just test-ui
-
-# Build all repos
-build-all:
-    @echo "Building all repos..."
-    just build-api
-    just build-ui
-
-# Install dependencies in all repos
-install-all:
-    @echo "Installing dependencies..."
-    cd {api_path} && npm install
-    cd {ui_path} && npm install
-
-# ============================================
-# API ({api_path})
-# ============================================
-
-# Run API tests
-test-api:
-    cd {api_path} && {api_test_command}
-
-# Build API
-build-api:
-    cd {api_path} && {api_build_command}
-
-# Start API development server
-dev-api:
-    cd {api_path} && {api_dev_command}
-
-# Lint API
-lint-api:
-    cd {api_path} && {api_lint_command}
-
-# ============================================
-# UI ({ui_path})
-# ============================================
-
-# Run UI tests
-test-ui:
-    cd {ui_path} && {ui_test_command}
-
-# Build UI
-build-ui:
-    cd {ui_path} && {ui_build_command}
-
-# Start UI development server
-dev-ui:
-    cd {ui_path} && {ui_dev_command}
-
-# Lint UI
-lint-ui:
-    cd {ui_path} && {ui_lint_command}
-
-# ============================================
-# ORCHESTRATOR
-# ============================================
-
-# Start both API and UI (background API, foreground UI)
-dev:
-    just dev-api &
-    just dev-ui
-
-# Run linting in all repos
-lint-all:
-    just lint-api
-    just lint-ui
-
-# Clone missing subrepos
-clone-repos:
-    @echo "Cloning subrepos..."
-    test -d {api_path} || git clone {api_git_url} {api_path}
-    test -d {ui_path} || git clone {ui_git_url} {ui_path}
-
-# Check repo status across all repos
-status:
-    @echo "=== Orchestrator ===" && git status --short
-    @echo "=== API ===" && cd {api_path} && git status --short
-    @echo "=== UI ===" && cd {ui_path} && git status --short
-```
-
-## GENERATION FROM REPOS.YAML
-
-For each repo in repos.yaml, generate recipes:
-
-```yaml
-# repos.yaml input:
-repos:
-  api:
-    path: conductor-api
-    test_command: npm test
-    build_command: npm run build
-    dev_command: npm run dev
-    lint_command: npm run lint
-```
-
-Generates:
-```just
-test-api:
-    cd conductor-api && npm test
-
-build-api:
-    cd conductor-api && npm run build
-```
-
-## COMMON ORCHESTRATOR RECIPES
-
-### Sprint Management Integration
-
-```just
-# ============================================
-# PENNYFARTHING / SPRINT
-# ============================================
-
-# Show current sprint status
-sprint:
-    @.pennyfarthing/scripts/sprint/sprint-cli.sh status
-
-# List available stories
-backlog:
-    @.pennyfarthing/scripts/sprint/sprint-cli.sh backlog
-
-# Start Cyclist visual terminal
-cyclist:
-    cd {cyclist_path} && npm run dev:once
-```
-
-### CI/CD Recipes
-
-```just
-# ============================================
-# CI/CD
-# ============================================
-
-# Run full CI check
-ci: lint-all test-all build-all
-    @echo "CI passed!"
-
-# Create release
-release version:
-    @echo "Creating release {{version}}..."
-    # Add release logic here
-```
-
-## INTERACTIVE CUSTOMIZATION
-
-```
-📋 Task Runner Configuration
-═════════════════════════════
-
-Detected: {existing_runner or "none"}
-Recommended: justfile
-
-Generated recipes:
-  ✓ test-all, build-all, install-all
-  ✓ Per-repo: test-{repo}, build-{repo}, dev-{repo}
-  ✓ Orchestrator: dev, status, clone-repos
-  ✓ Sprint: sprint, backlog, cyclist
-
-Options:
-[A] Accept and write justfile
-[E] Edit recipes
-[M] Generate Makefile instead
-[P] Preview full file
-[S] Skip - I'll create my own
-```
-
-### Edit Flow
-
-```
-Which recipe to edit?
-
-[1] test-all
-[2] build-all
-[3] test-api
-[4] Add new recipe
-[5] Remove a recipe
-
-> 4
-
-Recipe name: deploy-staging
-Recipe commands:
-> cd api && npm run deploy:staging
-> cd ui && npm run deploy:staging
-
-Added recipe 'deploy-staging'
-```
-
-## MAKEFILE ALTERNATIVE
-
-If user prefers Makefile:
-
-```makefile
-# Makefile for {project_name}
-# Generated by Pennyfarthing project-setup workflow
-
-.PHONY: test-all build-all install-all test-api build-api dev-api
-
-# Default target
-help:
-	@echo "Available targets:"
-	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "  %-20s %s\n", $$1, $$2}'
-
-test-all: test-api test-ui ## Run tests in all repos
-
-test-api: ## Run API tests
-	cd {api_path} && {api_test_command}
-
-test-ui: ## Run UI tests
-	cd {ui_path} && {ui_test_command}
-```
-
-## SUCCESS CRITERIA
-
-✅ Task runner created (justfile preferred)
-✅ All repos have standard recipes (test, build, dev, lint)
-✅ Aggregated commands work (test-all, build-all)
-✅ Orchestrator commands included
-✅ User has reviewed and approved
-
-## NEXT STEP
-
-After task runner is created, proceed to `step-07-theme.md` to configure the persona theme.

package/pennyfarthing-dist/workflows/project-setup/steps/step-07-theme.md

@@ -1,200 +0,0 @@
-# Step 7: Configure Persona Theme
-
-<purpose>
-Select and configure a persona theme for the project's AI agents. Themes provide character-based personas that make interactions more engaging and memorable.
-</purpose>
-
-<instructions>
-1. List available themes
-2. Suggest themes based on project type
-3. Allow user to browse/preview themes
-4. Configure selected theme
-5. Update persona-config.yaml
-</instructions>
-
-<output>
-- Theme selected and configured
-- persona-config.yaml updated
-- Theme previewed with sample agent
-- User satisfied with selection
-</output>
-
-## THEME SELECTION
-
-### List Available Themes
-
-```bash
-ls -la .pennyfarthing/personas/themes/
-```
-
-### Theme Categories
-
-| Category | Examples | Best For |
-|----------|----------|----------|
-| **Sci-Fi** | dune, star-trek, firefly | Tech-heavy projects |
-| **Fantasy** | tolkien, discworld | Creative projects |
-| **Historical** | victorian, renaissance | Enterprise/formal |
-| **Pop Culture** | office, parks-rec | Team-oriented |
-| **Literature** | sherlock, austen | Analysis-heavy |
-| **Mythology** | norse, greek | Framework/infra |
-
-### Theme Suggestions Based on Project Type
-
-```
-🎭 Theme Suggestions
-════════════════════
-
-Based on your project type ({project_type}), here are recommended themes:
-
-{if api_project}
-  🚀 Sci-Fi themes work well for backend development:
-    - dune (infrastructure, long-term planning)
-    - star-trek (exploration, problem-solving)
-    - firefly (scrappy, get-things-done)
-{/if}
-
-{if ui_project}
-  🎨 Creative themes suit frontend work:
-    - studio-ghibli (visual, artistic)
-    - pixar (user-focused, storytelling)
-    - marvel (dynamic, action-oriented)
-{/if}
-
-{if enterprise}
-  🏛️ Professional themes for enterprise:
-    - victorian (formal, structured)
-    - mad-men (business, strategy)
-    - west-wing (politics, stakeholders)
-{/if}
-
-{if framework}
-  ⚔️ Epic themes for infrastructure:
-    - tolkien (world-building, architecture)
-    - dune (ecology, systems thinking)
-    - norse (reliability, strength)
-{/if}
-```
-
-## THEME PREVIEW
-
-Show sample personas from selected theme:
-
-```
-🎭 Theme Preview: dune
-═══════════════════════
-
-Characters:
-┌─────────────┬────────────────────────────────┬──────────────────────────────────┐
-│ Agent       │ Character                      │ Style                            │
-├─────────────┼────────────────────────────────┼──────────────────────────────────┤
-│ sm          │ Stilgar                        │ Tribal leader, decisive          │
-│ tea         │ Thufir Hawat                   │ Mentat, analytical               │
-│ dev         │ Reverend Mother Mohiam         │ Precise, powerful                │
-│ reviewer    │ Leto II (God Emperor)          │ Long-view, uncompromising        │
-│ architect   │ Paul Atreides (Muad'Dib)       │ Visionary, strategic             │
-│ pm          │ Lady Jessica                   │ Diplomatic, influential          │
-│ devops      │ Planetologist Pardot Kynes     │ Ecological, systems thinker      │
-└─────────────┴────────────────────────────────┴──────────────────────────────────┘
-
-User title: "Cousin"
-
-Sample interaction:
-  Stilgar: "The water of your code flows strong today, Cousin. Let us see what
-           the sietch requires of us in this sprint."
-
-[S] Select this theme
-[P] Preview another theme
-[B] Browse all themes
-[D] Use default (no theme)
-```
-
-## CONFIGURATION
-
-### Update persona-config.yaml
-
-```yaml
-# .claude/persona-config.yaml
-# Selected theme: dune
-
-theme: dune
-
-# Optional overrides
-overrides:
-  # Use different character for specific agent
-  # dev: custom-character
-
-# Disable personas for specific agents
-# disabled:
-#   - tea
-```
-
-### Theme Activation
-
-After selection:
-
-```
-✓ Theme 'dune' selected
-
-Updated files:
-  - .claude/persona-config.yaml
-
-To see your new personas in action:
-  - Run any agent command (e.g., /sm, /dev)
-  - Agents will now use Dune character personas
-
-To change themes later:
-  - /theme list    - see available themes
-  - /theme set X   - switch to theme X
-  - /theme show    - see current theme details
-```
-
-## INTERACTIVE FLOW
-
-```
-🎭 Theme Configuration
-═══════════════════════
-
-Current theme: {current_theme or "default (none)"}
-
-Options:
-[1] Recommended themes (based on project)
-[2] Browse all themes by category
-[3] Search themes by keyword
-[4] Preview a specific theme
-[5] Keep current / use default
-[6] Create custom theme
-
-> 1
-
-Recommended for {project_type}:
-
-[a] dune - Infrastructure & systems thinking
-    "Plans changes across centuries"
-
-[b] star-trek - Exploration & problem-solving
-    "Boldly solving bugs no one has solved before"
-
-[c] firefly - Scrappy & pragmatic
-    "Keep flying, keep coding"
-
-[d] Show more recommendations
-
-> a
-
-{preview dune theme}
-
-[S] Select 'dune'
-[P] Preview another
-[B] Back to options
-```
-
-## SUCCESS CRITERIA
-
-✅ Theme selected (or explicitly chose default)
-✅ persona-config.yaml updated
-✅ User previewed theme and is satisfied
-✅ Theme ready for agent use
-
-## NEXT STEP
-
-After theme is configured, proceed to `step-08-theme-packs.md` to optionally install additional theme packs.

package/pennyfarthing-dist/workflows/project-setup/steps/step-08-theme-packs.md

@@ -1,142 +0,0 @@
-# Step 8: Install Additional Theme Packs (Optional)
-
-<purpose>
-Offer the user additional theme packs beyond the 26 base themes that ship with Pennyfarthing. Theme packs are optional npm packages that add themed personas with portraits.
-</purpose>
-
-<instructions>
-1. Explain the theme pack system
-2. Show available packs with descriptions
-3. Let user select which packs to install
-4. Install selected packs
-5. Verify themes are discovered
-</instructions>
-
-<output>
-- User informed about available theme packs
-- Selected packs installed (if any)
-- New themes discoverable via `/theme list`
-</output>
-
-## THEME PACK SYSTEM
-
-```
-🎭 Additional Theme Packs
-══════════════════════════
-
-Pennyfarthing ships with 26 base themes. Additional themes are available
-as optional packages - install the ones that interest you.
-
-Theme packs are discovered automatically once installed. No configuration
-needed beyond `npm install`.
-```
-
-## AVAILABLE PACKS
-
-Present the packs with descriptions and theme counts:
-
-```
-Available theme packs:
-
-[1] @pennyfarthing/themes-literary (15 themes)
-    Classic literature: Dickens, Shakespeare, Austen, Moby Dick,
-    Sherlock Holmes, Les Miserables, Great Gatsby, and more.
-    Pre-1950 books and author collections.
-
-[2] @pennyfarthing/themes-prestige-tv (17 themes)
-    Golden age television: Breaking Bad, The Sopranos, The Wire,
-    Mad Men, Deadwood, Succession, Twin Peaks, and more.
-
-[3] @pennyfarthing/themes-comedy (9 themes)
-    Comedy TV and film: The Office, Parks & Rec, Futurama,
-    The Simpsons, Monty Python, Ted Lasso, and more.
-
-[4] @pennyfarthing/themes-scifi (8 themes)
-    Sci-fi and cyberpunk deep cuts: Foundation, Babylon 5,
-    Neuromancer, Snow Crash, Star Trek TOS, and more.
-
-[5] @pennyfarthing/themes-realistic (14 themes)
-    Historical figures: Renaissance masters, jazz legends,
-    scientific revolutionaries, classical composers, and more.
-    Realistic portrait style.
-
-[6] @pennyfarthing/themes-superheroes (4 themes)
-    Superheroes and animated action: Marvel MCU, Legion of Doom,
-    Superfriends, Avatar: The Last Airbender.
-
-[7] @pennyfarthing/themes-mythology-fantasy (4 themes)
-    Mythology and fantasy: Greek mythology, Norse mythology,
-    His Dark Materials, The Witcher.
-
-[A] Install ALL packs (71 additional themes)
-[S] Skip - base themes are enough for now
-```
-
-## INSTALLATION
-
-Based on user selection, install the chosen packs:
-
-```bash
-# Install selected packs (example: literary + prestige-tv)
-npm install @pennyfarthing/themes-literary @pennyfarthing/themes-prestige-tv
-```
-
-### Install All
-
-```bash
-npm install \
-  @pennyfarthing/themes-literary \
-  @pennyfarthing/themes-prestige-tv \
-  @pennyfarthing/themes-comedy \
-  @pennyfarthing/themes-scifi \
-  @pennyfarthing/themes-realistic \
-  @pennyfarthing/themes-superheroes \
-  @pennyfarthing/themes-mythology-fantasy
-```
-
-## VERIFICATION
-
-After installation, verify themes are discovered:
-
-```bash
-# List all themes - should show base + installed packs
-pennyfarthing theme list
-```
-
-```
-✓ Theme packs installed
-
-Themes available:
-  Base themes:              26
-  {pack_name}:              {count}
-  ...
-  ─────────────────────────────
-  Total:                    {total}
-
-New themes are ready to use. Switch anytime with:
-  /theme set {theme-name}
-```
-
-## INSTALLING LATER
-
-```
-You can install theme packs anytime:
-
-  npm install @pennyfarthing/themes-literary
-  npm install @pennyfarthing/themes-prestige-tv
-  # etc.
-
-They're automatically discovered - no config changes needed.
-To see what's available: /theme list
-```
-
-## SUCCESS CRITERIA
-
-- User shown available theme packs
-- Selected packs installed (if any)
-- New themes verified as discoverable
-- User knows how to install more later
-
-## NEXT STEP
-
-After theme packs, proceed to `step-09-cyclist.md` to optionally install Cyclist visual terminal.