Playbook
0 / 10 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
  9. 09
  10. 10
Step 07 of 10 2-4 quarters· advanced

Step 7: Continue Migrating Slices

Migrate the remaining capabilities, refining patterns as you go. Edge cases (file uploads, printing, real-time data) emerge mid-way through this phase.

What you're doing in this step

Ship slice after slice. Most follow the same pattern as slice 1: page + API + DB query. Edge cases (complex grids → server-side pagination, file uploads → presigned URLs, printing → PDF generation, real-time → polling/WS) need decisions as they appear.

Recommended prompts

Use one of these to do the work in your IDE

Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.

Primary recommendation 0.5 day

Feature Flag Rollout Strategy for Migrations

Use feature flags to safely route traffic between legacy and new systems during migration with controlled rollout and instant rollback.

View template
Template· Template 20 min

React Form Builder (react-hook-form + Zod)

Build a fully accessible, type-safe form with react-hook-form, Zod validation, and shadcn/ui components.

Use this when: More forms to migrate

reacttypescriptnextjstailwindshadcn-ui
View template
Template· Template 10 min

shadcn/ui Component Builder

Generate a custom React component composed of shadcn/ui primitives with proper accessibility and types.

Use this when: Building reusable UI components for the SPA

reacttypescripttailwindshadcn-ui
View template
Template· Template 25 min

OpenAPI 3.1 Spec Generator

Generate a complete OpenAPI 3.1 specification from user stories or a feature description, ready for API-first development.

Use this when: Adding endpoints to the API contract

View template
Recommended skills

Drop these into Claude Code for this phase

Skills auto-trigger on the right kind of request. Install once; they apply to every prompt that fits.

Skill· Skill 5 min setup

Spec-Driven Builder Skill

Tool-neutral skill that walks developers through PRD → stories → schema → API → tests for any new feature, producing real artifacts at each step. The methodology is identical on every supported tool.

claude-codecopilotcursor
Skill· Skill 5 min setup

Migration Planner Skill

Flagship migration skill that walks Claude Code through audit → strategy → slicing → cutover for any legacy system migration.

claude-code
Skill· Skill 5 min setup

Test Generator Skill

Claude Code skill that picks the right test type (unit/integration/E2E) based on context and applies Evoke's testing patterns automatically.

claude-code
Skill· Skill 5 min setup

Code Reviewer Skill

Claude Code skill that performs comprehensive code review on PRs and diffs, prioritized by severity with concrete fixes.

claude-code
Recommended MCP configs

Wire these tools into Claude Code first

MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.

MCP config· MCP config 10 min setup

Azure DevOps MCP for Evoke

Pre-configured Azure DevOps MCP server for Claude Code — work items, repos, PRs, and pipelines from chat.

claude-codemcp
MCP config· MCP config 10 min setup

GitHub MCP for Evoke

Pre-configured GitHub MCP server for Claude Code — issues, PRs, code search, and Actions from chat.

claude-codemcp
MCP config· MCP config 5 min setup

Filesystem MCP for Evoke

Pre-configured filesystem MCP server for Claude Code — safe, scoped read/write access to project files.

claude-codemcp
When you're done

Verify these in your own work before moving on

This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.

  • All forms have a web equivalent
  • All workflows can be completed without WinForms
  • Performance acceptable across all flows
  • User testing passed for each major slice
Common pitfalls

What goes wrong at this step

  • Long tail of forms nobody uses — audit usage; some forms can be deprecated, not migrated
  • Power-user feature gaps — keyboard shortcuts, bulk operations, exports — desktop users have these; ensure web has equivalents
  • Reporting and exports — easy to defer; users will scream when they realize their reports don't work yet
← Previous step

Command Palette

Search for a command to run...