Route Makeover
Route Makeover orchestrates a complete app redesign by scanning your SvelteKit project's routes, organizing them into tiers and clusters, and materializing a structured task epic ready for execution. It pairs with the impeccable skill to handle per-route treatment and jat:tasktree to wire dependencies, letting you hand a design team a ready-to-run plan. Use it when you need the whole app redesigned—not just one screen.
Route Makeover scans your SvelteKit app's routes, clusters them by design need, and generates a dependency-wired task epic for a full-app redesign.
AI-generated summary based on this skill's SKILL.md
Install
joewinke/jat/route-makeover · repository language: Svelte
git clone https://github.com/joewinke/jat
cp -r jat/.agents/skills/route-makeover ~/.claude/skills/route-makeoverFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does Route Makeover do for a SvelteKit app design overhaul?
Route Makeover orchestrates a complete app redesign by scanning your SvelteKit project's routes, organizing them into tiers and clusters, and materializing a structured task epic ready for execution. It pairs with the impeccable skill to handle per-route treatment and jat:tasktree to wire dependencies, letting you hand a design team a ready-to-run plan.
How does Route Makeover redesign all routes at once?
Route Makeover scans your entire SvelteKit app, clusters routes by dependency and design scope, and generates a dependency-wired task epic that gates per-route treatment behind shared system fixes. This lets you plan and materialize design work across the whole app in structured tiers and foundation phases rather than tackling routes in isolation.
Can I add new routes to an existing Route Makeover epic?
Yes. Route Makeover supports adding new routes to an existing design-treatment epic without re-running the foundation phase. This means you can extend your design plan incrementally as your app grows, keeping the core system work intact while layering on new route treatments.
What is the relationship between Route Makeover and impeccable?
Route Makeover generates the high-level design PRD and task tree that organizes your redesign work; impeccable handles the per-route treatment and design critique. Route Makeover gates per-route work behind shared system fixes, so impeccable can focus on individual route polish once the foundation is solid.
How does Route Makeover handle design dependencies?
Route Makeover generates a design epic with jat:tasktree-compatible dependency wiring, so tasks that depend on shared system work are automatically gated. This automates design-firm-style task planning and dependency management, ensuring your design team works in the right order and foundation phases complete before per-route treatment begins.
When should I use Route Makeover instead of redesigning routes individually?
Use Route Makeover when you need the whole app redesigned—not just one screen. It's built for full-app UI overhauls where you want to identify shared design patterns, cluster related routes, and hand your team a ready-to-run plan that respects dependencies and foundation work.
SKILL.md
rendered from the published skill — quoted content, verbatim
Turn a whole SvelteKit app into a structured design makeover: scan every route → cluster + tier them → write a PRD → materialize an impeccable-treatment epic (epic + foundation tasks + one task per route cluster, fully dependency-wired).
This skill orchestrates two others: the impeccable
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 3 files
.agents/skills/route-makeover/SKILL.md
.agents/skills/route-makeover/reference/treatment.md
.agents/skills/route-makeover/scripts/scan-routes.mjs