skills

Coordinate parallel agent work. Use when decomposing complex tasks, running review/implementation in parallel, managing task lists, or choosing shared vs isolated workspaces.

Svelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.

SvelteKit data flow guidance. Use when working with load functions, form actions, server/client boundaries, serialization, or invalidation.

Implement SvelteKit remote functions. Use for query(), query.live(), form(), command(), and prerender() patterns in .remote.ts files.

SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.

Svelte 5 core best practices. Use when creating, editing, or reviewing .svelte, .svelte.ts, or .svelte.js files. Routes to deeper Svelte skills.

Build Svelte LayerChart components. Use for tooltip snippets, Chart context access, gradients, highlights, axes, and Svelte 5 snippet patterns.

Svelte template directive guidance. Use when working with snippets, attachments, dynamic HTML, declaration tags, debugging tags, or global DOM events.

Build Svelte components. Use for Svelte custom elements, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.

Implement Svelte 5 runes correctly. Use for reactive state, props, effects, $state.raw, $derived.by, $props, and $bindable.

Navigating LLM tooling workflows. Use when choosing recall, search, SQLite, MCP, secret-safety, or skill validation tools.

Validate Claude Code plugin projects. Use only for .claude-plugin manifests, plugin marketplaces, or claude plugin validation.

Secret-safe agent sessions via nopeek CLI. Use when user asks about secrets, .env loading, credential safety, or keeping API keys out of conversation context.

Verify sources before presenting findings. Use when asked to research links or documentation.

Design and create Agent Skills using progressive disclosure principles. Use when building new skills, planning skill architecture, or writing skill content.

Clean AI-generated code noise. Use when reviewing diffs, removing unnecessary comments, tightening verbose code, or desloping recent changes.

Capture reusable session learnings. Use when updating agent instructions, adding lessons learned, preserving project conventions, or fixing repeated mistakes.

Plan risky or ambiguous work before implementing. Use when refactoring, designing unclear features, comparing approaches, or needing user checkpoints.

Stop dismissing pre-existing test/build failures. Use when reporting test results, build output, or any command output containing errors or failures.

Debug failing CI pipelines, containers, and reproduce bugs locally. Use when CI is red, containers won't start, or need to reproduce bugs.

Find AI-readiness architecture issues and module-deepening refactors. Use when improving codebase architecture, testability, agent navigation, seams, or refactor tickets.

Test-driven development with a red-green-refactor loop. Use when explicitly asked for TDD, red-green-refactor, test-first development, or integration-test-led feature work.

Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.

Svelte code writing and validation workflow. Use when creating, editing, reviewing, or debugging .svelte, .svelte.ts, or .svelte.js files.

Svelte CSS styling patterns. Use for scoped styles, CSS custom properties, style: directive, :global, or styling child components.