Update project structure and documentation: Add new entries to .gitignore for standalone outputs and MCP config, delete obsolete design_skill.md file, and revise README and various skills to reflect updated workflow steps, including UI design and performance testing. Adjust paths in retrospective and metrics documentation to align with new directory structure.

2026-04-23 02:26:32 +00:00 · 2026-03-24 04:48:08 +02:00
parent e609586c7c
commit 749217bbb6
22 changed files with 286 additions and 165 deletions
@@ -11,10 +11,12 @@ Workflow for projects with an existing codebase. Starts with documentation, prod
 | 2c   | Decompose Tests         | decompose/SKILL.md (tests-only) | Step 1t + Step 3 + Step 4             |
 | 2d   | Implement Tests         | implement/SKILL.md              | (batch-driven, no fixed sub-steps)    |
 | 2e   | Refactor                | refactor/SKILL.md               | Phases 0–5 (6-phase method)           |
+| 2ea  | UI Design               | ui-design/SKILL.md              | Phase 0–8 (conditional — UI projects only) |
 | 2f   | New Task                | new-task/SKILL.md               | Steps 1–8 (loop)                      |
 | 2g   | Implement               | implement/SKILL.md              | (batch-driven, no fixed sub-steps)    |
 | 2h   | Run Tests               | (autopilot-managed)             | Unit tests → Blackbox tests |
 | 2hb  | Security Audit          | security/SKILL.md               | Phase 1–5 (optional)                  |
+| 2hc  | Performance Test        | (autopilot-managed)             | Load/stress tests (optional)          |
 | 2i   | Deploy                  | deploy/SKILL.md                 | Steps 1–7                             |

 After Step 2i, the existing-code workflow is complete.
@@ -91,8 +93,37 @@ If `_docs/04_refactor/` has phase reports, the refactor skill detects completed

 ---

+**Step 2ea — UI Design (conditional)**
+Condition: the autopilot state shows Step 2e (Refactor) is completed AND the autopilot state does NOT show Step 2ea (UI Design) as completed or skipped
+
+**UI Project Detection** — the project is a UI project if ANY of the following are true:
+- `package.json` exists in the workspace root or any subdirectory
+- `*.html`, `*.jsx`, `*.tsx` files exist in the workspace
+- `_docs/02_document/components/` contains a component whose `description.md` mentions UI, frontend, page, screen, dashboard, form, or view
+- `_docs/02_document/architecture.md` mentions frontend, UI layer, SPA, or client-side rendering
+
+If the project is NOT a UI project → mark Step 2ea as `skipped` in the state file and auto-chain to Step 2f.
+
+If the project IS a UI project → present using Choose format:
+
+```
+══════════════════════════════════════
+ DECISION REQUIRED: UI project detected — generate/update mockups?
+══════════════════════════════════════
+ A) Generate UI mockups before new task planning (recommended)
+ B) Skip — proceed directly to new task
+══════════════════════════════════════
+ Recommendation: A — mockups inform better frontend task specs
+══════════════════════════════════════
+```
+
+- If user picks A → Read and execute `.cursor/skills/ui-design/SKILL.md`. After completion, auto-chain to Step 2f (New Task).
+- If user picks B → Mark Step 2ea as `skipped` in the state file, auto-chain to Step 2f (New Task).
+
+---
+
 **Step 2f — New Task**
-Condition: `_docs/04_refactor/FINAL_refactor_report.md` exists AND the autopilot state shows Step 2e (Refactor) is completed AND the autopilot state does NOT show Step 2f (New Task) as completed
+Condition: (the autopilot state shows Step 2ea (UI Design) is completed or skipped) AND the autopilot state does NOT show Step 2f (New Task) as completed

 Action: Read and execute `.cursor/skills/new-task/SKILL.md`

@@ -159,8 +190,36 @@ Action: Present using Choose format:

 ---

+**Step 2hc — Performance Test (optional)**
+Condition: the autopilot state shows Step 2hb (Security Audit) is completed or skipped AND the autopilot state does NOT show Step 2hc (Performance Test) as completed or skipped AND (`_docs/04_deploy/` does not exist or is incomplete)
+
+Action: Present using Choose format:
+
+```
+══════════════════════════════════════
+ DECISION REQUIRED: Run performance/load tests before deploy?
+══════════════════════════════════════
+ A) Run performance tests (recommended for latency-sensitive or high-load systems)
+ B) Skip — proceed directly to deploy
+══════════════════════════════════════
+ Recommendation: [A or B — base on whether acceptance criteria
+ include latency, throughput, or load requirements]
+══════════════════════════════════════
+```
+
+- If user picks A → Run performance tests:
+  1. Check if `_docs/02_document/tests/performance-tests.md` exists for test scenarios
+  2. Detect appropriate load testing tool (k6, locust, artillery, wrk, or built-in benchmarks)
+  3. Execute performance test scenarios against the running system
+  4. Present results vs acceptance criteria thresholds
+  5. If thresholds fail → present Choose format: A) Fix and re-run, B) Proceed anyway, C) Abort
+  6. After completion, auto-chain to Step 2i (Deploy)
+- If user picks B → Mark Step 2hc as `skipped` in the state file, auto-chain to Step 2i (Deploy).
+
+---
+
 **Step 2i — Deploy**
-Condition: the autopilot state shows Step 2h (Run Tests) is completed AND (Step 2hb is completed or skipped) AND (`_docs/04_deploy/` does not exist or is incomplete)
+Condition: the autopilot state shows Step 2h (Run Tests) is completed AND (Step 2hb is completed or skipped) AND (Step 2hc is completed or skipped) AND (`_docs/04_deploy/` does not exist or is incomplete)

 Action: Read and execute `.cursor/skills/deploy/SKILL.md`

@@ -196,9 +255,11 @@ Action: The project completed a full cycle. Present status and loop back to New
 | Blackbox Test Spec (Step 2b) | Auto-chain → Decompose Tests (Step 2c) |
 | Decompose Tests (Step 2c) | **Session boundary** — suggest new conversation before Implement Tests |
 | Implement Tests (Step 2d) | Auto-chain → Refactor (Step 2e) |
-| Refactor (Step 2e) | Auto-chain → New Task (Step 2f) |
+| Refactor (Step 2e) | Auto-chain → UI Design detection (Step 2ea) |
+| UI Design (Step 2ea, done or skipped) | Auto-chain → New Task (Step 2f) |
 | New Task (Step 2f) | **Session boundary** — suggest new conversation before Implement |
 | Implement (Step 2g) | Auto-chain → Run Tests (Step 2h) |
 | Run Tests (Step 2h, all pass) | Auto-chain → Security Audit choice (Step 2hb) |
-| Security Audit (Step 2hb, done or skipped) | Auto-chain → Deploy (Step 2i) |
+| Security Audit (Step 2hb, done or skipped) | Auto-chain → Performance Test choice (Step 2hc) |
+| Performance Test (Step 2hc, done or skipped) | Auto-chain → Deploy (Step 2i) |
 | Deploy (Step 2i) | **Workflow complete** — existing-code flow done |
@@ -1,6 +1,6 @@
 # Greenfield Workflow

-Workflow for new projects built from scratch. Flows linearly: Problem → Research → Plan → Decompose → Implement → Run Tests → Security Audit (optional) → Deploy.
+Workflow for new projects built from scratch. Flows linearly: Problem → Research → Plan → UI Design (if applicable) → Decompose → Implement → Run Tests → Security Audit (optional) → Deploy.

 ## Step Reference Table

@@ -9,10 +9,12 @@ Workflow for new projects built from scratch. Flows linearly: Problem → Resear
 | 0    | Problem   | problem/SKILL.md       | Phase 1–4                             |
 | 1    | Research  | research/SKILL.md      | Mode A: Phase 1–4 · Mode B: Step 0–8 |
 | 2    | Plan      | plan/SKILL.md          | Step 1–6 + Final                      |
+| 2a   | UI Design | ui-design/SKILL.md     | Phase 0–8 (conditional — UI projects only) |
 | 3    | Decompose | decompose/SKILL.md     | Step 1–4                              |
 | 4    | Implement | implement/SKILL.md     | (batch-driven, no fixed sub-steps)    |
 | 5    | Run Tests | (autopilot-managed)    | Unit tests → Blackbox tests |
 | 5b   | Security Audit | security/SKILL.md | Phase 1–5 (optional)                  |
+| 5c   | Performance Test | (autopilot-managed) | Load/stress tests (optional)        |
 | 6    | Deploy    | deploy/SKILL.md        | Step 1–7                              |

 ## Detection Rules
@@ -76,6 +78,37 @@ If `_docs/02_document/` exists but is incomplete (has some artifacts but no `FIN

 ---

+**Step 2a — UI Design (conditional)**
+Condition: `_docs/02_document/architecture.md` exists AND the autopilot state does NOT show Step 2a (UI Design) as completed or skipped AND the project is a UI project
+
+**UI Project Detection** — the project is a UI project if ANY of the following are true:
+- `package.json` exists in the workspace root or any subdirectory
+- `*.html`, `*.jsx`, `*.tsx` files exist in the workspace
+- `_docs/02_document/components/` contains a component whose `description.md` mentions UI, frontend, page, screen, dashboard, form, or view
+- `_docs/02_document/architecture.md` mentions frontend, UI layer, SPA, or client-side rendering
+- `_docs/01_solution/solution.md` mentions frontend, web interface, or user-facing UI
+
+If the project is NOT a UI project → mark Step 2a as `skipped` in the state file and auto-chain to Step 3.
+
+If the project IS a UI project → present using Choose format:
+
+```
+══════════════════════════════════════
+ DECISION REQUIRED: UI project detected — generate mockups?
+══════════════════════════════════════
+ A) Generate UI mockups before decomposition (recommended)
+ B) Skip — proceed directly to decompose
+══════════════════════════════════════
+ Recommendation: A — mockups before decomposition
+ produce better task specs for frontend components
+══════════════════════════════════════
+```
+
+- If user picks A → Read and execute `.cursor/skills/ui-design/SKILL.md`. After completion, auto-chain to Step 3 (Decompose).
+- If user picks B → Mark Step 2a as `skipped` in the state file, auto-chain to Step 3 (Decompose).
+
+---
+
 **Step 3 — Decompose**
 Condition: `_docs/02_document/` contains `architecture.md` AND `_docs/02_document/components/` has at least one component AND `_docs/02_tasks/` does not exist or has no task files (excluding `_dependencies_table.md`)

@@ -142,8 +175,36 @@ Action: Present using Choose format:

 ---

+**Step 5c — Performance Test (optional)**
+Condition: the autopilot state shows Step 5b (Security Audit) is completed or skipped AND the autopilot state does NOT show Step 5c (Performance Test) as completed or skipped AND (`_docs/04_deploy/` does not exist or is incomplete)
+
+Action: Present using Choose format:
+
+```
+══════════════════════════════════════
+ DECISION REQUIRED: Run performance/load tests before deploy?
+══════════════════════════════════════
+ A) Run performance tests (recommended for latency-sensitive or high-load systems)
+ B) Skip — proceed directly to deploy
+══════════════════════════════════════
+ Recommendation: [A or B — base on whether acceptance criteria
+ include latency, throughput, or load requirements]
+══════════════════════════════════════
+```
+
+- If user picks A → Run performance tests:
+  1. Check if `_docs/02_document/tests/performance-tests.md` exists for test scenarios
+  2. Detect appropriate load testing tool (k6, locust, artillery, wrk, or built-in benchmarks)
+  3. Execute performance test scenarios against the running system
+  4. Present results vs acceptance criteria thresholds
+  5. If thresholds fail → present Choose format: A) Fix and re-run, B) Proceed anyway, C) Abort
+  6. After completion, auto-chain to Step 6 (Deploy)
+- If user picks B → Mark Step 5c as `skipped` in the state file, auto-chain to Step 6 (Deploy).
+
+---
+
 **Step 6 — Deploy**
-Condition: the autopilot state shows Step 5 (Run Tests) is completed AND (Step 5b is completed or skipped) AND (`_docs/04_deploy/` does not exist or is incomplete)
+Condition: the autopilot state shows Step 5 (Run Tests) is completed AND (Step 5b is completed or skipped) AND (Step 5c is completed or skipped) AND (`_docs/04_deploy/` does not exist or is incomplete)

 Action: Read and execute `.cursor/skills/deploy/SKILL.md`

@@ -161,9 +222,11 @@ Action: Report project completion with summary. If the user runs autopilot again
 | Problem Gathering | Auto-chain → Research (Mode A) |
 | Research (any round) | Auto-chain → Research Decision (ask user: another round or proceed?) |
 | Research Decision → proceed | Auto-chain → Plan |
-| Plan | Auto-chain → Decompose |
+| Plan | Auto-chain → UI Design detection (Step 2a) |
+| UI Design (done or skipped) | Auto-chain → Decompose |
 | Decompose | **Session boundary** — suggest new conversation before Implement |
 | Implement | Auto-chain → Run Tests (Step 5) |
 | Run Tests (all pass) | Auto-chain → Security Audit choice (Step 5b) |
-| Security Audit (done or skipped) | Auto-chain → Deploy (Step 6) |
+| Security Audit (done or skipped) | Auto-chain → Performance Test choice (Step 5c) |
+| Performance Test (done or skipped) | Auto-chain → Deploy (Step 6) |
 | Deploy | Report completion |