Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

repo-svelte-change-workflow

Estrellas17

Forks0

Actualizado11 de abril de 2026 a las 03:03

Changes Svelte 5 and SvelteKit files in this repo using the required Svelte MCP flow and local UI conventions. Use when editing `.svelte`, `.svelte.ts`, route components, shared blocks, editor panels, or homepage UI behavior.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

emzinnia

emzinnia/emzinnia.dev

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores webOcupaciones informáticas y matemáticas·SOC 15-1254

SKILL.md

readonly

name	repo-svelte-change-workflow
description	Changes Svelte 5 and SvelteKit files in this repo using the required Svelte MCP flow and local UI conventions. Use when editing `.svelte`, `.svelte.ts`, route components, shared blocks, editor panels, or homepage UI behavior.

Repo Svelte Change Workflow

Use this skill when

Touching src/**/*.svelte or src/**/*.svelte.ts
Changing route UI such as src/routes/+layout.svelte or src/routes/**/+page.svelte
Updating shared blocks, hero components, editor sections, or UI primitives

Required workflow

Read AGENTS.md.
Use the Svelte MCP in this order: list-sections, then get-documentation for every relevant section.
Make the change with the Svelte 5 patterns already used here: $props, $state, $effect, and shared state in .svelte.ts modules.
Run the Svelte autofixer and keep iterating until it returns no issues or suggestions.
Run targeted verification such as npm run check, the nearest Vitest file, or the relevant Playwright spec.

Repo conventions

Prefer Tailwind utilities over custom CSS.
Keep components focused; extract helpers before adding new abstractions.
Put shared mutable state in src/lib/stores/*.svelte.ts.
Keep markup semantic and accessible so tests can use role-based queries.

Common paths

src/lib/components/blocks/
src/lib/components/editor/
src/lib/components/hero/
src/lib/components/ui/

Más de este repositorio

mismo repositorio

repo-content-markdown-workflow

emzinnia/emzinnia.dev

Maintains article, project, and markdown-backed content flows in this SvelteKit portfolio. Use when editing `src/articles/**`, blog/project routes, `src/lib/articles.ts`, `src/lib/markdown.ts`, content reader panels, or the dev content editor.

2026-04-2717

repo-design-system-catalog

emzinnia/emzinnia.dev

Maintains this repo's UI component library, design page, component documentation registry, and design-system docs. Use when editing `src/lib/components/ui/**`, `src/lib/components/design/**`, `src/lib/registry/designComponents.ts`, `src/routes/design/**`, or `docs/components/**`.

2026-04-2717

repo-homepage-grid-registry

emzinnia/emzinnia.dev

Maintains homepage registry data, grid item types, shuffled layout behavior, reader panels, and homepage block wiring. Use when editing `src/lib/registry/homepage.ts`, `src/lib/types/homepage.ts`, grid components, homepage blocks, or `src/routes/+page.svelte`.

2026-04-2717

repo-performance-analytics-workflow

emzinnia/emzinnia.dev

Maintains the dev performance analytics pipeline across browser instrumentation, persisted analytics API, Prisma storage, and editor analytics UI. Use when editing `performanceAnalytics`, `/api/performance-analytics`, analytics Prisma models, or editor analytics sections.

2026-04-2717

repo-api-route-patterns

emzinnia/emzinnia.dev

Implements SvelteKit API routes in this repo using the existing server, env, and response conventions. Use when editing `src/routes/api/**/+server.ts`, adding new endpoints, or connecting server routes to Prisma or GitHub-backed data.

2026-04-1117

repo-editor-dev-surface

emzinnia/emzinnia.dev

Maintains the dev-only editor route and its shared homepage customization state. Use when changing `/editor`, grid layout behavior, local user settings, debug toggles, or editor section components.

2026-04-1117

name	repo-svelte-change-workflow
description	Changes Svelte 5 and SvelteKit files in this repo using the required Svelte MCP flow and local UI conventions. Use when editing `.svelte`, `.svelte.ts`, route components, shared blocks, editor panels, or homepage UI behavior.

Repo Svelte Change Workflow

Use this skill when

Touching src/**/*.svelte or src/**/*.svelte.ts
Changing route UI such as src/routes/+layout.svelte or src/routes/**/+page.svelte
Updating shared blocks, hero components, editor sections, or UI primitives

Required workflow

Read AGENTS.md.
Use the Svelte MCP in this order: list-sections, then get-documentation for every relevant section.
Make the change with the Svelte 5 patterns already used here: $props, $state, $effect, and shared state in .svelte.ts modules.
Run the Svelte autofixer and keep iterating until it returns no issues or suggestions.
Run targeted verification such as npm run check, the nearest Vitest file, or the relevant Playwright spec.

Repo conventions

Prefer Tailwind utilities over custom CSS.
Keep components focused; extract helpers before adding new abstractions.
Put shared mutable state in src/lib/stores/*.svelte.ts.
Keep markup semantic and accessible so tests can use role-based queries.

Common paths

src/lib/components/blocks/
src/lib/components/editor/
src/lib/components/hero/
src/lib/components/ui/