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

Step 6: Migrate Vertical Slice 1

Ship one complete user-facing capability through the new stack, end-to-end, behind a feature flag. The first slice is your proof point.

What you're doing in this step

Take the first slice (typically sign-in or a simple read-only screen) and build the entire vertical: Angular component → .NET API endpoint → DB query (or call to legacy via the coexistence layer). Ship behind a feature flag and canary it to production.

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 45 min

Authentication Setup (OAuth + JWT)

Implement production-grade authentication with OAuth providers, JWT sessions, role-based access, and secure refresh flows.

Use this when: Slice 1 is the auth flow itself

nodejstypescriptnextjs
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: You want to lock the API contract before implementation

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: Slice 1 is a form-heavy screen — adapt the React patterns to Angular reactive forms

reacttypescriptnextjstailwindshadcn-ui
View template
Template· Template 1 day

SQL Server to Modern Schema Translator

Translate SQL Server schemas to modernized SQL Server (Azure SQL) or Postgres, handling type differences, constraints, and stored procedure migration.

Use this when: Slice 1 needs data movement from SQL Server to a different engine

postgressql
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
View skill
Skill· Skill 5 min setup

Compatibility Layer Generator Skill

Claude Code skill that generates adapters, shims, and proxies for incremental coexistence between legacy and new systems.

claude-codedotnet
View skill
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
View skill
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
View config
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
View config
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
View config
MCP config· MCP config 10 min setup

Postgres MCP for Evoke

Pre-configured Postgres MCP server for Claude Code — schema inspection and read-only queries to make database work safer and faster.

claude-codemcppostgres
View config
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.

  • Slice 1 implemented end-to-end (Angular + .NET + DB)
  • Parity tests pass: new behavior matches legacy
  • Unit and integration tests cover the new code
  • Feature flag wires up routing
  • Internal team validates on staging for 1 week
  • Canary rollout: 1% → 5% → 25% → 50% → 100% with stop conditions
  • Monitoring shows no error-rate increase, latency within 50% of legacy
  • Rollback procedure tested in staging
Common pitfalls

What goes wrong at this step

  • Big-bang deploy — defeats the strangler fig purpose. Always canary
  • No stop conditions — the team keeps ramping the % even when errors increase
  • No rollback drill — the first time you flip the flag back is the worst time to discover it doesn't work
  • Hidden coupling to legacy — slice 1 ends up needing 10 legacy adapters; reconsider scope
← Previous step

Command Palette

Search for a command to run...