ui-route — community ui-route, traceway, community, ide skills

v1.0.0

About this Skill

Perfect for Frontend Agents needing streamlined SvelteKit route creation and management. Traceway: observability for LLM's

andrewn6 andrewn6
[1]
[0]
Updated: 3/13/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
45
Canonical Locale
en
Detected Body Locale
en

Perfect for Frontend Agents needing streamlined SvelteKit route creation and management. Traceway: observability for LLM's

Core Value

Empowers agents to generate structured UI routes with file-based routing, utilizing SvelteKit's +page.svelte, +page.ts, and +layout.svelte components, and supports Server-Side Rendering (SSR) data loading.

Ideal Agent Persona

Perfect for Frontend Agents needing streamlined SvelteKit route creation and management.

Capabilities Granted for ui-route

Creating new pages with custom layouts
Generating routes with optional load functions for SSR data
Organizing UI components within SvelteKit projects

! Prerequisites & Limits

  • Requires SvelteKit project setup
  • Filesystem access needed for route creation
  • Svelte 5 compatibility required

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is ui-route?

Perfect for Frontend Agents needing streamlined SvelteKit route creation and management. Traceway: observability for LLM's

How do I install ui-route?

Run the command: npx killer-skills add andrewn6/traceway/ui-route. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for ui-route?

Key use cases include: Creating new pages with custom layouts, Generating routes with optional load functions for SSR data, Organizing UI components within SvelteKit projects.

Which IDEs are compatible with ui-route?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for ui-route?

Requires SvelteKit project setup. Filesystem access needed for route creation. Svelte 5 compatibility required.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add andrewn6/traceway/ui-route. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use ui-route immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

ui-route

Install ui-route, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Create UI Route or Component

Use this skill when the user asks to add a new page, route, or component to the SvelteKit frontend.

Creating a new route

Routes live in ui/src/routes/. SvelteKit uses file-based routing.

Route file structure

ui/src/routes/<route-name>/
├── +page.svelte      # Page component
├── +page.ts          # Load function (optional, for SSR data)
└── +layout.svelte    # Layout wrapper (optional, inherits parent)

Page template (Svelte 5 runes)

svelte
1<script lang="ts"> 2 import { onMount } from 'svelte'; 3 import { API_BASE, type MyType } from '$lib/api'; 4 5 // State — use $state(), never Svelte 4 stores 6 let items: MyType[] = $state([]); 7 let loading = $state(true); 8 let error = $state(''); 9 10 // Derived values — use $derived() 11 let itemCount = $derived(items.length); 12 let hasItems = $derived(items.length > 0); 13 14 // Complex derived — use $derived.by() 15 let summary = $derived.by(() => { 16 return items.reduce((acc, item) => acc + item.value, 0); 17 }); 18 19 // Side effects — use $effect() 20 $effect(() => { 21 console.log(`Items changed: ${items.length}`); 22 }); 23 24 onMount(async () => { 25 try { 26 const res = await fetch(`${API_BASE}/internal/my-endpoint?org_id=...&project_id=...`); 27 items = await res.json(); 28 } catch (e: any) { 29 error = e?.message || 'Failed to load'; 30 } 31 loading = false; 32 }); 33</script> 34 35<div class="app-shell-wide"> 36 {#if loading} 37 <p class="text-zinc-500 text-sm">Loading...</p> 38 {:else if error} 39 <div class="alert-danger">{error}</div> 40 {:else} 41 <div class="table-float"> 42 <!-- Content here --> 43 </div> 44 {/if} 45</div>

Creating a component

Components live in ui/src/lib/components/.

svelte
1<script lang="ts"> 2 // Props — use $props(), never export let 3 let { 4 items = [], 5 selected = null, 6 onSelect = undefined, 7 }: { 8 items: Item[]; 9 selected?: string | null; 10 onSelect?: (id: string) => void; 11 } = $props(); 12 13 // Internal state 14 let expanded = $state(false); 15</script> 16 17<div class="surface-panel"> 18 {#each items as item (item.id)} 19 <button 20 class="btn-ghost" 21 class:active={selected === item.id} 22 onclick={() => onSelect?.(item.id)} 23 > 24 {item.name} 25 </button> 26 {/each} 27</div>

Adding API fetch helpers

Add new fetch functions to ui/src/lib/api.ts:

typescript
1export async function getMyEntities(): Promise<MyEntity[]> { 2 const res = await fetch(`${API_BASE}/internal/my-entities?org_id=${getOrgId()}&project_id=${getProjectId()}`); 3 if (!res.ok) throw new Error(`Failed to fetch: ${res.statusText}`); 4 const data = await res.json(); 5 return data.items; 6}

If the type comes from the OpenAPI spec, re-export it from api-types.ts:

typescript
1export type MyEntity = Schemas['MyEntity'];

Design system primitives

Always check DESIGN_SYSTEM.md and reuse existing classes before adding new styles:

  • Surfaces: surface-panel, surface-command, surface-quiet, table-float
  • Shells: app-shell-wide, app-toolbar-shell, app-page-shell
  • Controls: control-input, control-select, control-textarea
  • Buttons: btn-primary, btn-secondary, btn-ghost
  • Chips: query-chip, query-chip-active
  • Labels: label-micro, table-head-compact
  • Alerts: alert-danger, alert-success, alert-warning

Key conventions

  • Svelte 5 only: $state, $derived, $effect, $props — never use Svelte 4 writable/derived stores
  • Tailwind CSS v4: Classes in markup, no CSS modules
  • Dark theme first: Maintain dark/light parity on major surfaces
  • Dense controls: 11px micro labels, 13px body, 14-16px headings
  • Floating panels: Use right floating panel for detail/edit flows
  • a11y: Use for/id on label/select pairs, proper button elements
  • Page params: page.params.id can be undefined in Svelte 5 — always default with ?? ''
  • Type casting: Cast filters for query strings: (filter ?? {}) as Record<string, string | undefined>

After creating the route

  1. Run svelte-check: cd ui && npm run check
  2. Verify in browser at http://localhost:5173/<route-name>

Related Skills

Looking for an alternative to ui-route or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer