Strangler fig visualization pattern
Skill kjuhwa/skills-hub/skills/design/strangler-fig-visualization-pattern
Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.
npx -y skills add kjuhwa/skills-hub --skill strangler-fig-visualization-patternAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Side-by-side legacy/new system visualization with traffic routing overlay for strangler-fig migration apps
SKILL.md
1.7 KB, 309 tokens by cl100k_base, as published. Nobody here has run it
strangler-fig-visualization-pattern
Strangler-fig visualizations share a three-zone layout: a legacy monolith panel (left, typically rendered in muted/grey tones to signal deprecation), a new service panel (right, in vibrant/green tones to signal growth), and a routing facade layer (top or center) that shows which endpoints/routes are currently proxied to which side. Each endpoint or feature is rendered as a node with a migration-state badge: legacy-only, shadowed, canary, migrated, retired. Color transitions (grey → amber → green) communicate progress without requiring a legend.
The routing facade should animate request flows as particles or arrows traveling from the client through the facade to either the legacy or new backend. Percentage splits (e.g., 10% canary → new, 90% → legacy) are shown as weighted edge thickness or as a split-flow animation where particle counts match the routing ratio. Hovering a node reveals its migration metadata (dependencies, call volume, last-migrated date, rollback window).
A vine/ivy metaphor overlay (literal in vine-grower, abstracted in migration-simulator/route-router) works well: new-service growth visually "wraps" the legacy node until the legacy node shrinks and disappears on retirement. Timeline scrubbers let users replay migration history; a "kill legacy" control simulates the final cutover to verify no traffic still routes to the retired path.