Claude artifacts become deployed full-stack apps through two composable skill prompts — then move to durable infrastructure.
A fleet of supply-chain consoles was built as Claude React artifacts and deployed through a two-skill pipeline. abacus-mirror ports an artifact at high fidelity to a managed Next.js web app — it encodes the platform's deploy contract (component slot, managed providers, dependency age gate, design tokens) so the port survives contact with the platform. abacus-bridge then augments the deployed mirror server-side: database persistence with an admin/use split, per-dataset merge, upload history, and a secure-by-default auth gate whose secret never enters the source.
The key property: the Claude artifact stays canonical. Edit the source, re-derive the deployment — the orchestrator skill re-mirrors in place preserving the data layer, then re-bridges from the recorded augmentation spec.
The portability is the point. When one hosting platform stopped being available, nothing was locked in — proven tools port to a governed enterprise platform (managed Postgres behind an ORM layer that keeps the next hop portable too). Build fast on whatever's available; move to durable infrastructure when it matters.