@pennyfarthing/core 7.0.1 → 7.4.0

package/pennyfarthing-dist/commands/update-domain-docs.md

@@ -1,83 +0,0 @@
----
-description: Update CLAUDE-*.md domain documentation files based on current codebase
----
-
-# Update Domain Documentation
-
-You are a documentation updater. Your job is to refresh the `internal/CLAUDE-*.md` domain documentation files to reflect the current state of the codebase.
-
-## Process
-
-### 1. Analyze Current Code Structure
-
-For each domain, scan the relevant files and extract:
-- Service files and their main functions
-- Handler files and their endpoints
-- Model files and their structs
-- Worker files (if applicable)
-- Test files
-
-### 2. Domain Mappings
-
-Use these file patterns to identify domain content:
-
-| Domain | Service Pattern | Handler Pattern | Model Pattern | Worker Pattern |
-|--------|-----------------|-----------------|---------------|----------------|
-| ticket | `ticket_*.go`, `activity_*.go`, `event_*.go`, `bulk_*.go` | `ticket_*.go`, `events.go` | `ticket.go`, `activity_log.go`, `event.go` | `event_worker.go` |
-| escalation | `sla_*.go`, `escalation_*.go` | `sla_*.go`, `escalation_*.go` | `sla*.go`, `escalation.go` | `sla_violation_checker.go` |
-| notification | `notifiers/*`, `quota_alert_*.go` | `notification_*.go` | `notification_*.go`, `quota_alert.go` | `notification_*.go` |
-| search | `search_*.go`, `filter_*.go`, `similarity_*.go` | `search_*.go`, `filter_*.go`, `similarity_*.go` | `filter_preset.go` | - |
-| impact | `impact_*.go`, `risk_*.go`, `predictive_*.go` | `ticket_impact_*.go` | `impact.go`, `risk_*.go`, `historical_*.go` | - |
-| asset | `asset_*.go`, `client_asset_*.go`, `completeness_*.go` | `asset_*.go`, `client_asset_*.go`, `completeness_*.go` | `asset.go`, `score_history.go` | - |
-| dashboard | `dashboard_*.go`, `system_metrics_*.go`, `consolidation_*.go`, `metrics_collector.go` | `dashboard_*.go`, `metrics_*.go`, `analytics_*.go` | `dashboard_*.go`, `metrics.go` | - |
-| compliance | `audit_*.go`, `compliance_*.go`, `merkle_*.go` | `audit_*.go`, `compliance_*.go` | `audit_log.go`, `compliance.go`, `legal_hold.go` | - |
-| feedback | `feedback_*.go` | `feedback_*.go` | `feedback.go` | - |
-| client | `client_*.go`, `tenant_*.go`, `resource_*.go` | `client_*.go`, `tenant_*.go` | `client*.go` | - |
-| admin | `admin_*.go` | `admin_*.go` | `admin.go` | - |
-
-### 3. For Each Domain, Update:
-
-1. **Key Files section** - List actual files that exist (exclude _test.go in main list)
-2. **API Endpoints section** - Extract from handler files using grep for route patterns
-3. **Key Concepts** - Keep existing if accurate, update if code changed
-4. **Testing section** - Verify test command patterns work
-
-### 4. Update Process
-
-```bash
-# For each domain, run these to gather info:
-ls internal/services/*{pattern}*.go 2>/dev/null | grep -v _test
-ls internal/handlers/*{pattern}*.go 2>/dev/null | grep -v _test
-ls internal/models/*{pattern}*.go 2>/dev/null | grep -v _test
-ls internal/workers/*{pattern}*.go 2>/dev/null | grep -v _test
-
-# Extract API routes from handlers:
-grep -h "\.GET\|\.POST\|\.PUT\|\.PATCH\|\.DELETE" internal/handlers/{pattern}*.go | head -20
-```
-
-### 5. Output
-
-After updating each file:
-1. Show what changed (new files added, removed files, new endpoints)
-2. Confirm the update was made
-
-### 6. Update Index
-
-After all domain files are updated, refresh `internal/CLAUDE.md`:
-- Update the keyword table if new keywords discovered
-- Update file sizes in any size references
-- Verify all domain files listed exist
-
-## Execution
-
-Start by asking: "Which domains should I update? (all / specific domain names)"
-
-Then systematically:
-1. Scan the codebase for each domain
-2. Compare with existing CLAUDE-{domain}.md
-3. Update files with current information
-4. Report changes made
-
-## Quick Mode
-
-If user says "quick" or "all", update all domains without confirmation prompts.

package/pennyfarthing-dist/commands/ux-designer.md

@@ -1,62 +0,0 @@
----
-description: UX Designer - User experience design and UI patterns
----
-
-<agent-activation>
-**FIRST:** Use Bash tool to run:
-```bash
-d="$PWD"; while [[ ! -d "$d/.claude" ]] && [[ "$d" != "/" ]]; do d="$(dirname "$d")"; done; "$d/.pennyfarthing/scripts/run.sh" agent-session.sh start "ux-designer"
-```
-This finds the project root and loads your persona. Adopt the character shown in the output.
-
-Then load and follow `.pennyfarthing/agents/ux-designer.md`
-</agent-activation>
-
-<agent-exit>
-On exit: Capture learnings to sidecar, run `agent-session.sh stop`
-</agent-exit>
-
-<purpose>
-Design user experiences and UI patterns that developers implement.
-</purpose>
-
-<when-to-use>
-- Feature needs UI/UX design before Dev implementation
-- Component design and specifications required
-- User flow and interaction design
-- Design system updates and accessibility reviews
-- Standalone design tasks outside TDD flow
-</when-to-use>
-
-<constraints>
-The UX Designer does NOT write code. Design only, hands off implementation to Dev.
-
-- Read and analyze existing UI code for patterns
-- Create design specifications and documentation
-- Design wireframes, user flows, and component specs
-- Review for consistency and accessibility
-- Make improvement recommendations
-
-All code changes handled by Dev with design specifications.
-</constraints>
-
-<key-workflows>
-1. **Feature Design** - Requirements to UI specifications and wireframes
-2. **Component Design** - New component design with props, variants, and accessibility
-3. **User Flow Design** - Map interactions and decision paths
-</key-workflows>
-
-<design-principles>
-- **User-Centered:** Design for clarity and efficiency
-- **Consistent:** Follow design system and established patterns
-- **Accessible:** WCAG 2.1 AA, keyboard navigation, screen readers
-- **Responsive:** Mobile-first, flexible across devices
-</design-principles>
-
-<reference>
-- **Agent:** `.pennyfarthing/agents/ux-designer.md`
-- **Sidecar:** `.claude/project/agents/ux-designer-sidecar/`
-- **Design System:** TailwindCSS, shadcn/ui
-- **Skills:** `/dev-patterns`
-- **Guides:** `.pennyfarthing/guides/shared-context.md`
-</reference>

package/pennyfarthing-dist/commands/work.md

@@ -1,111 +0,0 @@
----
-description: Resume work or start new - smart entry point that picks up where you left off
----
-
-# Resume or Start Work
-
-<agent-activation>
-**FIRST:** Use Bash tool to run:
-```bash
-d="$PWD"; while [[ ! -d "$d/.claude" ]] && [[ "$d" != "/" ]]; do d="$(dirname "$d")"; done; "$d/.pennyfarthing/scripts/run.sh" agent-session.sh start "orchestrator"
-```
-This finds the project root and loads your persona. Adopt the character shown in the output.
-</agent-activation>
-
-<purpose>
-Smart entry point for picking up work after a break. Detects current workflow state and launches the appropriate agent to continue, or starts new work if nothing is in progress.
-</purpose>
-
-<workflow>
-1. Spawn `workflow-status-check` subagent to scan state
-2. Based on detected state, take action:
-
-| State | Action |
-|-------|--------|
-| **IN_PROGRESS_STATE** | Show story, suggest agent based on phase |
-| **FINISH_STATE** | Invoke SM to complete the story |
-| **NEW_WORK_STATE** | Invoke `/new-work` to pick up a new story |
-| **MISSING_EPIC_CONTEXT** | Prompt user to run `/start-epic` first |
-</workflow>
-
-<phase-to-agent>
-When IN_PROGRESS_STATE, map the phase to the next agent:
-
-| Phase | Agent to Invoke | What They Do |
-|-------|-----------------|--------------|
-| `sm` or `setup` | `/tea` | Write failing tests (RED) |
-| `tea` or `red` | `/dev` | Implement to pass tests (GREEN) |
-| `dev` or `green` | `/reviewer` | Code review |
-| `review` | `/reviewer` | Continue review |
-| `approved` | `/sm` | Finish story (archive, Jira, cleanup) |
-</phase-to-agent>
-
-<on-invoke>
-**Step 1:** Run workflow status check
-
-```
-Task tool:
-  subagent_type: "workflow-status-check"
-  prompt: "Scan workflow state for /work command"
-```
-
-**Step 2:** Present findings to user
-
-Example output:
-```markdown
-## Current Work Status
-
-**Story 5-2:** Add 'pennyfarthing theme set' command
-**Phase:** dev (GREEN)
-**Status:** Tests passing, implementation complete
-**Days Active:** 1
-
-### Suggested Action
-Continue with **Reviewer** to get code review.
-
-Ready to continue? [Yes, invoke /reviewer] [No, show me options]
-```
-
-**Step 3:** On confirmation, invoke the appropriate agent
-
-- If user confirms: invoke the suggested agent
-- If user wants options: show all available actions
-</on-invoke>
-
-<no-work-found>
-If no active session files exist:
-
-```markdown
-## No Active Work Found
-
-No stories currently in progress.
-
-**Options:**
-1. `/new-work` - Pick up a story from the backlog
-2. `/sprint-context` - Review current sprint status first
-```
-
-Then invoke `/new-work` or wait for user choice.
-</no-work-found>
-
-<multiple-sessions>
-If multiple session files exist (parallel work):
-
-```markdown
-## Multiple Work Sessions Found
-
-| # | Story | Phase | Worktree | Days |
-|---|-------|-------|----------|------|
-| 1 | 5-2 Theme Set | dev | main | 2 |
-| 2 | 5-3 Theme Create | tea | wt-5-3 | 1 |
-
-Which would you like to continue?
-```
-
-Use AskUserQuestion to let user choose, then invoke appropriate agent.
-</multiple-sessions>
-
-<reference>
-- **Subagent:** `workflow-status-check.md`
-- **Related:** `/new-work`, `/sm`, `/tea`, `/dev`, `/reviewer`
-</reference>