@pennyfarthing/core 10.4.0 → 11.0.0

package/pennyfarthing-dist/skills/pf-workflow/examples.md

@@ -0,0 +1,101 @@
+# Workflow — Examples
+
+## Listing & Viewing
+
+```bash
+# List all available workflows
+.pennyfarthing/scripts/workflow/list-workflows.sh
+
+# Show TDD workflow details
+.pennyfarthing/scripts/workflow/show-workflow.sh tdd
+
+# Show current session's workflow
+.pennyfarthing/scripts/workflow/show-workflow.sh
+
+# Show trivial workflow
+.pennyfarthing/scripts/workflow/show-workflow.sh trivial
+```
+
+## Checking State (Python CLI)
+
+```bash
+# Check current workflow state
+pf workflow check
+pf workflow check --json
+
+# Who owns the "review" phase in TDD?
+pf workflow phase-check tdd review
+# Returns: reviewer
+
+# Who owns the "implement" phase in trivial?
+pf workflow phase-check trivial implement
+# Returns: dev
+
+# Emit handoff marker for Cyclist
+pf workflow handoff reviewer
+```
+
+## Stepped Workflows (BikeLane)
+
+```bash
+# Start architecture workflow in create mode (default)
+.pennyfarthing/scripts/workflow/start-workflow.sh architecture
+
+# Start in validate mode
+.pennyfarthing/scripts/workflow/start-workflow.sh architecture --mode validate
+
+# Check progress
+.pennyfarthing/scripts/workflow/workflow-status.sh
+
+# Resume after interruption
+.pennyfarthing/scripts/workflow/resume-workflow.sh
+.pennyfarthing/scripts/workflow/resume-workflow.sh architecture
+```
+
+## Phase Repair
+
+```bash
+# Preview phase fix
+.pennyfarthing/scripts/workflow/fix-session-phase.sh 56-1 review --dry-run
+
+# Fix phase to review (after Dev completed)
+.pennyfarthing/scripts/workflow/fix-session-phase.sh 56-1 review
+
+# Fix phase to approved (after Reviewer approved)
+.pennyfarthing/scripts/workflow/fix-session-phase.sh 56-1 approved
+
+# Using Jira key
+.pennyfarthing/scripts/workflow/fix-session-phase.sh MSSCI-12190 approved
+```
+
+## Switching Workflow Mid-Session
+
+1. Verify the target workflow exists:
+   ```bash
+   .pennyfarthing/scripts/workflow/show-workflow.sh trivial
+   ```
+
+2. Edit the session file:
+   - Open `.session/{story-id}-session.md`
+   - Change `**Workflow:**` line to new workflow name
+
+3. Continue with the new workflow's agent sequence.
+
+## Common Scenarios
+
+### Story upgraded from trivial to TDD
+```bash
+# Check current state
+pf workflow check --json
+# Edit session to change workflow from trivial to tdd
+# Fix phase to match where you are
+.pennyfarthing/scripts/workflow/fix-session-phase.sh 56-1 red
+```
+
+### Agent activated on wrong phase
+```bash
+# Check who owns the current phase
+pf workflow phase-check tdd review
+# Returns: reviewer — hand off if you're not the reviewer
+pf workflow handoff reviewer
+```

package/pennyfarthing-dist/skills/pf-workflow/skill.md

@@ -0,0 +1,49 @@
+---
+name: workflow
+description: |
+  List available workflows, show current workflow details, and switch workflows mid-session. Use when checking available workflow types (TDD, trivial, agent-docs), viewing current workflow phase, switching to a different workflow pattern, or managing BikeLane stepped workflows.
+args: "[list|show [name]|set <name>|start <name> [--mode <mode>]|resume [name]|status|check|fix-phase]"
+---
+
+# /pf-workflow - Workflow Management
+
+Pennyfarthing uses YAML-defined workflows to control agent sequences. The default TDD workflow (SM > TEA > Dev > Reviewer) can be customized or replaced.
+
+## Quick Reference
+
+### Shell Script Commands
+
+| Command | Script | Purpose |
+|---------|--------|---------|
+| `/pf-workflow` or `/pf-workflow list` | `.pennyfarthing/scripts/workflow/list-workflows.sh` | List all workflows |
+| `/pf-workflow show [name]` | `.pennyfarthing/scripts/workflow/show-workflow.sh [name]` | Show workflow details |
+| `/pf-workflow set <name>` | Edit session file `**Workflow:**` line | Switch workflow mid-session |
+| `/pf-workflow start <name>` | `.pennyfarthing/scripts/workflow/start-workflow.sh <name> [--mode M]` | Start stepped workflow |
+| `/pf-workflow resume [name]` | `.pennyfarthing/scripts/workflow/resume-workflow.sh [name]` | Resume interrupted workflow |
+| `/pf-workflow status` | `.pennyfarthing/scripts/workflow/workflow-status.sh` | Show stepped workflow progress |
+| `/pf-workflow fix-phase <id> <phase>` | `.pennyfarthing/scripts/workflow/fix-session-phase.sh <id> <phase> [--dry-run]` | Repair session phase |
+
+### Python CLI Commands
+
+| Command | CLI | Purpose |
+|---------|-----|---------|
+| Check workflow state | `pf workflow check [--json]` | Current story, phase, state |
+| Check phase owner | `pf workflow phase-check <workflow> <phase>` | Which agent owns a phase |
+| Emit handoff marker | `pf workflow handoff <next-agent>` | CYCLIST handoff marker |
+
+### Built-in Workflows
+
+| Workflow | Flow | Triggers |
+|----------|------|----------|
+| `tdd` (default) | SM > TEA > Dev > Reviewer > SM | features, 3+ points |
+| `tdd-tandem` | SM > TEA(+Arch) > Dev(+TEA) > Rev(+PM) > SM | `tandem` tag, 3+ points |
+| `trivial` | SM > Dev > Reviewer > SM | chores/fixes, 1-2 points |
+| `bdd` | SM > UX > TEA > Dev > Reviewer > SM | UI/UX features |
+| `bdd-tandem` | SM > UX(+Arch) > TEA > Dev(+UX) > Rev(+PM) > SM | `bdd-tandem` tag |
+| `agent-docs` | SM > Orchestrator > Tech Writer > SM | docs, agent-file label |
+| `architecture` | 7 stepped phases with gates | architecture/design/ADR |
+
+---
+
+**Detailed options and behavior:** [usage.md](usage.md)
+**Practical examples:** [examples.md](examples.md)

package/pennyfarthing-dist/skills/pf-workflow/usage.md

@@ -0,0 +1,145 @@
+# Workflow — Detailed Usage
+
+## Shell Script Commands
+
+### List Workflows
+
+```bash
+.pennyfarthing/scripts/workflow/list-workflows.sh
+```
+
+No arguments. Returns table of workflows with type, phases/steps count, modes, default flag, description.
+
+### Show Workflow
+
+```bash
+.pennyfarthing/scripts/workflow/show-workflow.sh [NAME]
+```
+
+| Arg | Required | Description |
+|-----|----------|-------------|
+| `NAME` | No | Workflow name (`tdd`, `trivial`, etc.). Omit for current session's workflow. |
+
+Returns workflow description, phase flow diagram, phases table, trigger conditions.
+
+### Switch Workflow
+
+Manual edit of `.session/{story-id}-session.md` — change the `**Workflow:**` line.
+
+Warning: Only do this when story requirements have fundamentally changed. Switching resets phase tracking.
+
+### Start Stepped Workflow
+
+```bash
+.pennyfarthing/scripts/workflow/start-workflow.sh <NAME> [--mode <MODE>]
+```
+
+| Arg/Option | Required | Description |
+|------------|----------|-------------|
+| `NAME` | Yes | Workflow name (e.g., `architecture`) |
+| `--mode` | No | `create` (default), `validate`, or `edit` |
+
+Creates a new session and begins at step 1.
+
+### Resume Stepped Workflow
+
+```bash
+.pennyfarthing/scripts/workflow/resume-workflow.sh [NAME]
+```
+
+| Arg | Required | Description |
+|-----|----------|-------------|
+| `NAME` | No | Workflow to resume. Detects from active session if omitted. |
+
+### Workflow Status
+
+```bash
+.pennyfarthing/scripts/workflow/workflow-status.sh
+```
+
+No arguments. Shows current step, progress percentage, mode.
+
+### Fix Session Phase
+
+```bash
+.pennyfarthing/scripts/workflow/fix-session-phase.sh <STORY_ID> <TARGET_PHASE> [--dry-run]
+```
+
+| Arg/Option | Required | Description |
+|------------|----------|-------------|
+| `STORY_ID` | Yes | Story ID (e.g., `56-1` or `MSSCI-12190`) |
+| `TARGET_PHASE` | Yes | Target phase to set |
+| `--dry-run` | No | Preview without making changes |
+
+Valid phases by workflow:
+
+| Workflow | Phases |
+|----------|--------|
+| `tdd` | setup, red, green, review, approved, finish |
+| `trivial` | setup, implement, review, approved, finish |
+
+Updates `**Phase:**` field, `**Phase Started:**` timestamp, and handoff history table.
+
+---
+
+## Python CLI Commands
+
+### Check Workflow State
+
+```bash
+pf workflow check [--json]
+```
+
+| Option | Description |
+|--------|-------------|
+| `--json` | Output as JSON |
+
+Returns current story ID, phase, workflow, and state.
+
+### Check Phase Owner
+
+```bash
+pf workflow phase-check <WORKFLOW_NAME> <PHASE>
+```
+
+| Arg | Required | Description |
+|-----|----------|-------------|
+| `WORKFLOW_NAME` | Yes | Workflow type (`tdd`, `trivial`, etc.) |
+| `PHASE` | Yes | Phase to check (`red`, `implement`, `review`, etc.) |
+
+Returns the agent name that owns the phase.
+
+### Emit Handoff Marker
+
+```bash
+pf workflow handoff <NEXT_AGENT>
+```
+
+| Arg | Required | Description |
+|-----|----------|-------------|
+| `NEXT_AGENT` | Yes | Agent to hand off to (`tea`, `dev`, `reviewer`, etc.) |
+
+Outputs CYCLIST-formatted YAML marker.
+
+---
+
+## Workflow Routing Priority
+
+When multiple workflows match a story:
+
+1. **Explicit tag:** `workflow: docs` on story overrides everything
+2. **Trigger tags:** Story tags match workflow's `triggers.tags`
+3. **Type match:** Story type matches workflow's `triggers.types`
+4. **Points match:** Story points within `triggers.points` range
+5. **Default:** Workflow with `default: true` (tdd)
+
+## File Locations
+
+| Location | Purpose |
+|----------|---------|
+| `pennyfarthing-dist/workflows/` | Built-in workflow YAML definitions |
+| `.session/{story-id}-session.md` | Current story's workflow assignment |
+
+## Creating Custom Workflows
+
+See `pennyfarthing-dist/guides/workflow-schema.md` for the full YAML schema and `pennyfarthing-dist/guides/bikelane.md` for BikeLane stepped workflows.

package/pennyfarthing-dist/skills/skill-registry.yaml

@@ -5,8 +5,8 @@
 version: "1.0.0"
 
 skills:
-  agentic-patterns:
-    name: agentic-patterns
+  pf-agentic-patterns:
+    name: pf-agentic-patterns
     description: Core reasoning patterns for building effective LLM agents
     category: ai-llm
     tags: [reasoning, patterns, agents, llm]
@@ -19,12 +19,12 @@ skills:
         invocation: /agentic-patterns troubleshooting
     anti_patterns:
       - Don't apply patterns mechanically without understanding context
-    related_skills: [context-engineering]
+    related_skills: [pf-context-engineering]
     keywords: [react, reflection, planning, tool-use, chain-of-thought]
     allowed_tools: [Read, Glob, Grep, Task]  # Reference material - read-only
 
-  changelog:
-    name: changelog
+  pf-changelog:
+    name: pf-changelog
     description: Maintain changelogs following Keep a Changelog format with conventional commits
     category: documentation
     tags: [changelog, releases, versioning]
@@ -40,8 +40,8 @@ skills:
     related_skills: []
     keywords: [keepachangelog, conventional-commits, semver, release-notes]
 
-  code-review:
-    name: code-review
+  pf-code-review:
+    name: pf-code-review
     description: Code review checklists and patterns for quality assurance
     category: development
     tags: [review, quality, checklist]
@@ -55,11 +55,11 @@ skills:
     anti_patterns:
       - Don't skip security considerations in review
       - Don't approve without running tests
-    related_skills: [testing, dev-patterns]
+    related_skills: [pf-testing]
     keywords: [pr, pull-request, quality, linting, security]
 
-  context-engineering:
-    name: context-engineering
+  pf-context-engineering:
+    name: pf-context-engineering
     description: Strategies for managing context windows in long-running agent sessions
     category: ai-llm
     tags: [context, optimization, agents]
@@ -73,12 +73,12 @@ skills:
     anti_patterns:
       - Don't load unnecessary context upfront
       - Don't repeat large code blocks in prompts
-    related_skills: [agentic-patterns]
+    related_skills: [pf-agentic-patterns]
     keywords: [context-window, tokens, summarization, lazy-loading]
     allowed_tools: [Read, Glob, Grep, Task]  # Reference material - read-only
 
-  cyclist:
-    name: cyclist
+  pf-cyclist:
+    name: pf-cyclist
     description: Launch Cyclist visual terminal for Claude Code monitoring
     category: tools
     tags: [visual, monitoring, terminal]
@@ -94,41 +94,23 @@ skills:
     related_skills: []
     keywords: [tui, terminal, visualization, dashboard]
 
-  dev-patterns:
-    name: dev-patterns
-    description: Common development patterns, fixes, and gotchas
-    category: development
-    tags: [patterns, debugging, implementation]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Implementing features
-        invocation: /dev-patterns
-      - context: Avoiding known pitfalls
-        invocation: /dev-patterns gotchas
-    anti_patterns:
-      - Don't apply patterns from other frameworks blindly
-    related_skills: [code-review, testing]
-    keywords: [implementation, debugging, fixes, best-practices]
-    allowed_tools: [Read, Glob, Grep, Task]  # Reference material - read-only
-
-  finalize-run:
-    name: finalize-run
+  pf-finalize-run:
+    name: pf-finalize-run
     description: Validate and save benchmark run results - single exit point for all runs
     category: benchmarking
     tags: [benchmark, validation, results]
     version: "1.0.0"
-    prerequisites: [judge]
+    prerequisites: [pf-judge]
     examples:
       - context: Completing a benchmark run
         invocation: /finalize-run
     anti_patterns:
       - Never save results without passing through this skill
-    related_skills: [judge, persona-benchmark]
+    related_skills: [pf-judge, pf-persona-benchmark]
     keywords: [benchmark, save, validate, guardrail]
 
-  jira:
-    name: jira
+  pf-jira:
+    name: pf-jira
     description: Jira CLI commands for sprint management
     category: project-management
     tags: [jira, issues, sprint]
@@ -141,11 +123,11 @@ skills:
         invocation: /jira assign ISSUE-123
     anti_patterns:
       - Don't bypass Jira for sprint tracking
-    related_skills: [sprint]
+    related_skills: [pf-sprint]
     keywords: [atlassian, issues, tickets, backlog]
 
-  judge:
-    name: judge
+  pf-judge:
+    name: pf-judge
     description: Evaluate agent responses using standardized rubrics
     category: benchmarking
     tags: [evaluation, rubrics, scoring]
@@ -158,11 +140,11 @@ skills:
         invocation: /judge compare
     anti_patterns:
       - Don't modify rubrics during a benchmark run
-    related_skills: [finalize-run, persona-benchmark]
+    related_skills: [pf-finalize-run, pf-persona-benchmark]
     keywords: [evaluation, scoring, metrics, grading]
 
-  just:
-    name: just
+  pf-just:
+    name: pf-just
     description: Run just recipes for project tasks like dev servers, tests, and databases
     category: tools
     tags: [tasks, runner, automation]
@@ -175,11 +157,11 @@ skills:
         invocation: /just db-reset
     anti_patterns:
       - Don't create complex recipes - keep them simple and composable
-    related_skills: [testing]
+    related_skills: [pf-testing]
     keywords: [justfile, make, tasks, automation, command-runner]
 
-  mermaid:
-    name: mermaid
+  pf-mermaid:
+    name: pf-mermaid
     description: Generate diagrams using Mermaid syntax for documentation
     category: tools
     tags: [diagrams, visualization, documentation]
@@ -192,11 +174,11 @@ skills:
         invocation: /mermaid sequence
     anti_patterns:
       - Don't create overly complex diagrams - split into multiple if needed
-    related_skills: [changelog]
+    related_skills: [pf-changelog]
     keywords: [flowchart, sequence, er-diagram, gantt, class-diagram]
 
-  otel:
-    name: otel
+  pf-otel:
+    name: pf-otel
     description: Claude Code OTEL telemetry format documentation for span interception and enrichment
     category: tools
     tags: [telemetry, monitoring, otel]
@@ -209,11 +191,11 @@ skills:
         invocation: /otel enrichment
     anti_patterns:
       - Don't assume fields exist - verify against this documentation
-    related_skills: [cyclist]
+    related_skills: [pf-cyclist]
     keywords: [opentelemetry, spans, traces, enrichment, correlation]
 
-  permissions:
-    name: permissions
+  pf-permissions:
+    name: pf-permissions
     description: Manage runtime permission grants - list, grant, and revoke tool access
     category: project-management
     tags: [permissions, security, tools]
@@ -232,13 +214,13 @@ skills:
     related_skills: []
     keywords: [grants, scopes, tools, runtime, security]
 
-  persona-benchmark:
-    name: persona-benchmark
+  pf-persona-benchmark:
+    name: pf-persona-benchmark
     description: Run benchmarks to compare persona effectiveness
     category: benchmarking
     tags: [benchmark, personas, comparison]
     version: "1.0.0"
-    prerequisites: [judge]
+    prerequisites: [pf-judge]
     examples:
       - context: Testing persona on code review
         invocation: /persona-benchmark cr-001 discworld
@@ -246,11 +228,11 @@ skills:
         invocation: /persona-benchmark tw-001 literary-classics
     anti_patterns:
       - Don't compare results across different rubric versions
-    related_skills: [judge, finalize-run, theme]
+    related_skills: [pf-judge, pf-finalize-run, pf-theme]
     keywords: [benchmark, comparison, personas, testing]
 
-  sprint:
-    name: sprint
+  pf-sprint:
+    name: pf-sprint
     description: Sprint status, backlog, story, and epic management for Pennyfarthing
     category: project-management
     tags: [sprint, status, backlog, stories, epics]
@@ -269,12 +251,12 @@ skills:
         invocation: /sprint epic add epic-85 "New epic"
     anti_patterns:
       - Don't manually edit sprint YAML - use scripts
-    related_skills: [jira]
+    related_skills: [pf-jira]
     keywords: [sprint, backlog, velocity, kanban, stories, epics, sizing, templates]
     allowed_tools: [Read, Glob, Grep, Bash, Task]
 
-  systematic-debugging:
-    name: systematic-debugging
+  pf-systematic-debugging:
+    name: pf-systematic-debugging
     description: Systematic debugging approach for isolating and fixing issues
     category: development
     tags: [debugging, troubleshooting, root-cause]
@@ -288,17 +270,17 @@ skills:
     anti_patterns:
       - Don't jump to solutions without reproducing the issue first
       - Don't fix symptoms instead of root causes
-    related_skills: [testing, dev-patterns, agentic-patterns]
+    related_skills: [pf-testing, pf-agentic-patterns]
     keywords: [debugging, bisect, reproduce, isolate, root-cause, regression]
 
-  story:
-    name: story
+  pf-story:
+    name: pf-story
     description: "DEPRECATED: Use /sprint story instead. Story commands consolidated under /sprint."
     category: project-management
     tags: [stories, sizing, workflow, deprecated]
     version: "2.0.0"
     deprecated: true
-    redirect: sprint
+    redirect: pf-sprint
     prerequisites: []
     examples:
       - context: Creating new stories
@@ -308,11 +290,11 @@ skills:
     anti_patterns:
       - Don't create stories without acceptance criteria
       - Don't use /story directly - use /sprint story instead
-    related_skills: [sprint, jira]
+    related_skills: [pf-sprint, pf-jira]
     keywords: [user-stories, estimation, points, acceptance-criteria]
 
-  testing:
-    name: testing
+  pf-testing:
+    name: pf-testing
     description: Test commands and TDD workflow patterns
     category: development
     tags: [tdd, testing, quality]
@@ -326,11 +308,11 @@ skills:
     anti_patterns:
       - Don't run tests directly - use testing-runner subagent
       - Don't skip RED phase in TDD workflow
-    related_skills: [dev-patterns, code-review]
+    related_skills: [pf-code-review]
     keywords: [jest, vitest, pytest, unit-test, integration, tdd, red-green]
 
-  theme:
-    name: theme
+  pf-theme:
+    name: pf-theme
     description: Manage persona themes - list, show, set, create, and interactive maker wizard
     category: theming
     tags: [personas, themes, customization, creation]
@@ -353,24 +335,24 @@ skills:
     related_skills: []
     keywords: [personas, characters, discworld, literary-classics, custom, generation, wizard]
 
-  theme-creation:
-    name: theme-creation
+  pf-theme-creation:
+    name: pf-theme-creation
     description: "DEPRECATED: Use /theme maker instead"
     category: theming
     tags: [personas, themes, creation]
     version: "2.0.0"
     deprecated: true
-    redirect: theme
+    redirect: pf-theme
     prerequisites: []
     examples:
       - context: Interactive theme wizard
         invocation: /theme maker
     anti_patterns: []
-    related_skills: [theme]
+    related_skills: [pf-theme]
     keywords: [personas, custom, generation, wizard]
 
-  workflow:
-    name: workflow
+  pf-workflow:
+    name: pf-workflow
     description: Manage workflows - list, show, set, start, resume, and check status
     category: project-management
     tags: [workflow, phases, tdd]
@@ -385,11 +367,11 @@ skills:
         invocation: /workflow start architecture
     anti_patterns:
       - Don't switch workflows mid-story unless requirements fundamentally changed
-    related_skills: [sprint]
+    related_skills: [pf-sprint]
     keywords: [tdd, tdd-tandem, trivial, agent-docs, bdd, bdd-tandem, architecture, bikelane, stepped, phased]
 
-  yq:
-    name: yq
+  pf-yq:
+    name: pf-yq
     description: YAML processor for reading, modifying, and querying YAML files
     category: tools
     tags: [yaml, processing, cli]
@@ -402,5 +384,5 @@ skills:
         invocation: /yq modify
     anti_patterns:
       - Don't use complex expressions without testing first
-    related_skills: [just]
+    related_skills: [pf-just]
     keywords: [yaml, jq, parsing, query, mikefarah]

package/pennyfarthing-dist/workflows/architecture/data/domain-complexity.csv

@@ -0,0 +1,13 @@
+domain,signals,complexity_level,suggested_workflow,web_searches
+e_commerce,"shopping,cart,checkout,payment,products,store",medium,standard,"ecommerce architecture patterns, payment processing, inventory management"
+fintech,"banking,payment,trading,finance,money,investment",high,enhanced,"financial security, PCI compliance, trading algorithms, fraud detection"
+healthcare,"medical,diagnostic,clinical,patient,hospital,health",high,enhanced,"HIPAA compliance, medical data security, FDA regulations, health tech"
+social,"social network,community,users,friends,posts,sharing",high,advanced,"social graph algorithms, feed ranking, notification systems, privacy"
+education,"learning,course,student,teacher,training,academic",medium,standard,"LMS architecture, progress tracking, assessment systems, video streaming"
+productivity,"productivity,workflow,tasks,management,business,tools",medium,standard,"collaboration patterns, real-time editing, notification systems, integration"
+media,"content,media,video,audio,streaming,broadcast",high,advanced,"CDN architecture, video encoding, streaming protocols, content delivery"
+iot,"IoT,sensors,devices,embedded,smart,connected",high,advanced,"device communication, real-time data processing, edge computing, security"
+government,"government,civic,public,admin,policy,regulation",high,enhanced,"accessibility standards, security clearance, data privacy, audit trails"
+process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,control system,cyberphysical,MES,instrumentation,I&C,P&ID",high,advanced,"industrial process control architecture, SCADA system design, OT cybersecurity architecture, real-time control systems"
+building_automation,"building automation,BAS,BMS,HVAC,smart building,fire alarm,fire protection,fire suppression,life safety,elevator,DDC,access control,sequence of operations,commissioning",high,advanced,"building automation architecture, BACnet integration patterns, smart building design, building management system security"
+gaming,"game,gaming,multiplayer,real-time,interactive,entertainment",high,advanced,"real-time multiplayer, game engine architecture, matchmaking, leaderboards"

package/pennyfarthing-dist/workflows/architecture/data/project-types.csv

@@ -0,0 +1,7 @@
+project_type,detection_signals,description,typical_starters
+web_app,"website,web application,browser,frontend,UI,interface",Web-based applications running in browsers,Next.js, Vite, Remix
+mobile_app,"mobile,iOS,Android,app,smartphone,tablet",Native mobile applications,React Native, Expo, Flutter
+api_backend,"API,REST,GraphQL,backend,service,microservice",Backend services and APIs,NestJS, Express, Fastify
+full_stack,"full-stack,complete,web+mobile,frontend+backend",Applications with both frontend and backend,T3 App, RedwoodJS, Blitz
+cli_tool,"CLI,command line,terminal,console,tool",Command-line interface tools,oclif, Commander, Caporal
+desktop_app,"desktop,Electron,Tauri,native app,macOS,Windows",Desktop applications,Electron, Tauri, Flutter Desktop