mcp-tui: Skill for Claude Code

Implement Vertical Slice (TDD)

Implement a feature as a complete vertical slice using strict RED/GREEN/REFACTOR discipline. Each slice delivers working functionality through all layers — not a horizontal layer across features.

Pre-Flight Checks

Before writing any code:

1. Confirm the feature scope and acceptance criteria with the user
2. Read .claude/rules/architecture.md for active patterns and constraints
3. Read .claude/rules/tdd.md for TDD discipline rules
4. Identify which layers this slice touches (validation, logic, data, API, UI)
5. Verify the feature is small enough for one vertical slice (if not, split first)

Step 1 -- Write the Smoke Test (RED)

Write one end-to-end smoke test for the core user journey at HIGHEST fidelity.

Smoke Test Rules

• Full e2e — real UI (if applicable), real backend, real database
• NO mocks, stubs, or simulations
• Test the complete user journey from entry to exit
• Run it — it MUST FAIL (RED) because the feature doesn't exist yet

# Example: "User can create a post"
test("user creates a post and sees it in the list"):
  navigate to /posts/new
  fill in title and body
  click submit
  assert redirected to /posts
  assert new post appears in list

Run with: go test (CLI subprocess + live MCP servers: npx server-everything, test-servers/*.js)

Commit: RED: Smoke test for [feature]

Step 2 -- Identify the Thinnest Slice

Break the feature into the smallest possible behavior increments. Each increment is ONE RED/GREEN/REFACTOR cycle.

Slice Planning

List the behaviors in implementation order (dependencies first):

Example for "User can create a post":
  1. Post validation rejects empty title (pure logic)
  2. Post can be persisted to database (data layer)
  3. API endpoint accepts POST /posts (API layer)
  4. UI form submits to API (presentation layer)
  5. Success redirects to post list (navigation)

Each behavior becomes one TDD cycle. Order matters — build from the inside out, but always as a vertical slice (not all validation first, then all data, then all API).