Store Migration Workflow

Migrates monolithic Zustand stores to domain-driven stores using GOAP planning and AgentDB memory.

Updated Sep 21, 2025
One-click install
npx skills add https://github.com/bjpl/california_puzzle_game --skill store-migration-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Store Migration Workflow
Source: https://github.com/bjpl/california_puzzle_game/tree/main/.claude/skills/store-migration-workflow
Command: npx skills add https://github.com/bjpl/california_puzzle_game --skill store-migration-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the migration from monolithic Zustand stores to domain-driven stores using:

  • GOAP Planning for optimal action sequencing
  • Hive-Mind Coordination for complex refactoring
  • Neural Pattern Learning to generalize successful migrations
  • AgentDB Memory to persist migration state across sessions

Core Features & Use Cases

  • GOAP Planning: Generate optimal migration steps as a plan.
  • Hive-Mind Coordination: Leverage collective intelligence for large refactors.
  • Neural Pattern Learning: Train on successful migrations to improve future efforts.
  • AgentDB Memory: Persist world and plan state for cross-session continuity.
  • Use Case: Refactor a monolithic game store to domain stores without breaking app behavior.

Quick Start

Initialize hive-mind, set current world state and goal state, generate a GOAP plan, and spawn specialized agents for analysis, coding, migration, testing, and review.

Frequently Asked Questions about Store Migration Workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a monolithic Zustand store to domain-specific stores?

Migrate monolithic Zustand stores by decomposing god objects into domain-driven stores, updating imports across your codebase, and coordinating cross-store state transitions. This Skill automates the migration using GOAP planning to sequence steps optimally and hive-mind coordination to manage complex refactors without breaking application behavior.

What's the best way to refactor a large store architecture without breaking existing functionality?

Store migration using domain-driven decomposition maintains behavior by generating an optimal action plan with GOAP, spawning specialized agents for analysis, coding, migration, and testing, and persisting state across sessions via AgentDB memory. The Skill tracks world state and goal state to ensure all transitions remain consistent.

Can I use neural pattern learning to improve store migration over multiple refactors?

Yes. This Skill trains on successful migrations to generalize patterns and improve future efforts. Combined with AgentDB session persistence, neural pattern learning captures what worked across refactors and applies those insights to optimize subsequent migrations.

Do I need specialized coordination for migrating stores in a large codebase?

For large refactors involving multiple domain stores and cross-store coordination, hive-mind coordination orchestrates collective intelligence across specialized agents. GOAP planning generates the optimal migration sequence, reducing manual choreography and the risk of breaking state transitions.

How do I persist migration state and context across multiple work sessions?

AgentDB memory persists both world state and plan state across sessions, allowing you to pause and resume migrations without losing context. This enables long-running refactors to be completed incrementally while maintaining consistency.

What happens when a monolithic store has tightly coupled state across multiple domains?

The Skill handles complex state transitions through hive-mind coordination and GOAP planning, which sequences actions to respect dependencies and safely decompose coupled state into independent domain stores while maintaining referential integrity.