clay-migration-deep-dive
Execute Clay major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Clay, performing major version upgrades, or re-platforming existing integrations to Clay. Trigger with phrases like "migrate clay", "clay migration", "switch to clay", "clay replatform", "clay upgrade major".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- clay-migration-deep-dive
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Execute Clay major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Clay, performing major version upgrades, or re-platforming existing integrations to Clay. Trigger with phrases like "migrate clay", "clay migration", "switch to clay", "clay replatform", "clay upgrade major".
- allowed-tools
- Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(kubectl:*)
- compatible-with
- claude-code, codex, openclaw
02 资源文件 1
- 参考文档references/implementation-guide.md3.3 KB
03 SKILL.md 正文
Clay Migration Deep Dive
Overview
Comprehensive guide for migrating to or from Clay, or major version upgrades using the strangler fig pattern.
Prerequisites
- Current system documentation
- Clay SDK installed
- Feature flag infrastructure
- Rollback strategy tested
Migration Types
| Type | Complexity | Duration | Risk |
|---|---|---|---|
| Fresh install | Low | Days | Low |
| From competitor | Medium | Weeks | Medium |
| Major version | Medium | Weeks | Medium |
| Full replatform | High | Months | High |
Instructions
Assess current configuration (Week 1-2)
Inventory all files referencing Clay, count integration points, and document dependencies. Build a MigrationInventory with data types, record counts, and customizations.
Step 2: Build Adapter Layer (Week 3-4)
Create a ServiceAdapter interface with CRUD operations. Implement ClayAdapter with data transformation from old format to Clay format. This enables gradual migration.
Step 3: Migrate Data (Week 5-6)
Run batch data migration (100 records per batch) with error collection. Track progress and log failed batches for retry.
Step 4: Shift Traffic (Week 7-8)
Use feature flags to gradually route traffic: start at 0%, increase to 10%, 50%, then 100%. Use getServiceAdapter() to select Clay vs legacy based on flag percentage.
Step 5: Validate and Cut Over
Run validation checks: data count match, API functionality, performance baseline, and error rates. All must pass before completing the migration.
Rollback Plan
Disable Clay via environment variable and restart pods. For data rollback, restore from backup. Verify via health endpoint.
For complete TypeScript implementations, assessment scripts, and validation code, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
Output
- Migration assessment complete
- Adapter layer implemented
- Data migrated successfully
- Traffic fully shifted to Clay
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Data mismatch | Transform errors | Validate transform logic |
| Performance drop | No caching | Add caching layer |
| Rollback triggered | Errors spiked | Reduce traffic percentage |
| Validation failed | Missing data | Check batch processing |
Resources
Next Steps
For advanced troubleshooting, see clay-advanced-troubleshooting.
Examples
Basic usage: Apply clay migration deep dive to a standard project setup with default configuration options.
Advanced scenario: Customize clay migration deep dive for production environments with multiple constraints and team-specific requirements.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.