spences10
- 55 skills
- 0 followers
- 37 repo stars
- last month last updated
- ▌ Tdd 2 · spences10 bundleTest-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.
- ▌ Deslop 2 · spences10 bundleClean AI-generated code noise. Use when reviewing diffs, removing unnecessary comments, tightening verbose code, or desloping recent changes.
- ▌ Nopeek 2 · spences10Secret-safe agent sessions via nopeek CLI. Use when user asks about secrets, .env loading, credential safety, or keeping API keys out of conversation context.
- ▌ Asshole 2 · spences10Stop dismissing pre-existing test/build failures. Use when reporting test results, build output, or any command output containing errors or failures.
- ▌ Reflect 2 · spences10 bundleCapture reusable session learnings. Use when updating agent instructions, adding lessons learned, preserving project conventions, or fixing repeated mistakes.
- ▌ Research 2 · spences10 bundleVerify sources before presenting findings. Use when asked to research links or documentation.
- ▌ Plugin Dev 2 · spences10 bundleValidate Claude Code plugin projects. Use only for .claude-plugin manifests, plugin marketplaces, or claude plugin validation.
- ▌ Svelte Runes 2 · spences10 bundleImplement Svelte 5 runes correctly. Use for reactive state, props, effects, $state.raw, $derived.by, $props, and $bindable.
- ▌ Orchestration 2 · spences10 bundleCoordinate parallel agent work. Use when decomposing complex tasks, running review/implementation in parallel, managing task lists, or choosing shared vs isolated workspaces.
- ▌ Skill Creator 2 · spences10 bundleDesign and create Agent Skills using progressive disclosure principles. Use when building new skills, planning skill architecture, or writing skill content.
- ▌ Structured Rpi 2 · spences10 bundlePlan risky or ambiguous work before implementing. Use when refactoring, designing unclear features, comparing approaches, or needing user checkpoints.
- ▌ Svelte Styling 2 · spences10 bundleSvelte CSS styling patterns. Use for scoped styles, CSS custom properties, style: directive, :global, or styling child components.
- ▌ Ecosystem Guide 2 · spences10Navigating LLM tooling workflows. Use when choosing recall, search, SQLite, MCP, secret-safety, or skill validation tools.
- ▌ Techdebt Finder 2 · spences10 bundleFind technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
- ▌ CI Debug Workflow 2 · spences10 bundleDebug failing CI pipelines, containers, and reproduce bugs locally. Use when CI is red, containers won't start, or need to reproduce bugs.
- ▌ Svelte Components 2 · spences10 bundleBuild Svelte components. Use for Svelte custom elements, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
- ▌ Svelte Deployment 2 · spences10 bundleSvelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.
- ▌ Svelte Layerchart 2 · spences10 bundleBuild Svelte LayerChart components. Use for tooltip snippets, Chart context access, gradients, highlights, axes, and Svelte 5 snippet patterns.
- ▌ Sveltekit Data Flow 2 · spences10 bundleSvelteKit data flow guidance. Use when working with load functions, form actions, server/client boundaries, serialization, or invalidation.
- ▌ Sveltekit Structure 2 · spences10 bundleSvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
- ▌ Svelte Template Directives 2 · spences10 bundleSvelte template directive guidance. Use when working with snippets, attachments, dynamic HTML, declaration tags, debugging tags, or global DOM events.
- ▌ Sveltekit Remote Functions 2 · spences10 bundleImplement SvelteKit remote functions. Use for query(), query.live(), form(), command(), and prerender() patterns in .remote.ts files.
- ▌ Improve Codebase Architecture 2 · spences10 bundleFind AI-readiness architecture issues and module-deepening refactors. Use when improving codebase architecture, testability, agent navigation, seams, or refactor tickets.
- ▌ Svelte Code Writer · spences10Svelte code writing and validation workflow. Use when creating, editing, reviewing, or debugging .svelte, .svelte.ts, or .svelte.js files.
- ▌ Svelte Core Bestpractices · spences10Svelte 5 core best practices. Use when creating, editing, or reviewing .svelte, .svelte.ts, or .svelte.js files. Routes to deeper Svelte skills.
- ▌ Operating Tailscale Agent Hosts · spences10 bundlePrivate remote coding-agent hosts over Tailscale. Use when configuring unattended Linux workers, persistent remote agents, or private access to development services.
- ▌ Analytics · spences10 bundleQuery Claude Code session analytics from ccrecall database. Use when user asks about token usage, session history, or wants to analyze their Claude Code usage patterns.
- ▌ MCP Setup · spences10 bundleSetup guide for essential MCP servers. Use when configuring MCP servers or when user asks about search, SQLite, or MCP management.
- ▌ Nopeek · spences10Secret-safe Claude Code sessions via nopeek CLI. Use when user asks about secrets, .env loading, credential safety, or keeping API keys out of conversation context.
- ▌ Tdd · spences10 bundleTest-Driven Development workflow with red-green-refactor cycle. Use only when explicitly asked for TDD, not for general test writing.
- ▌ Deslop · spences10 bundleIdentify and remove AI-generated code patterns (slop). Use when asked to clean up AI-generated code, remove unnecessary comments, or deslop.
- ▌ Asshole · spences10Stop dismissing pre-existing test/build failures. Use when reporting test results, build output, or any command output containing errors or failures.
- ▌ Reflect · spences10 bundleAnalyze session history for learnings and persist to skills. Solves "memory zero" - correct once, never again.
- ▌ Research · spences10 bundleVerify sources before presenting findings. Use when asked to research links or documentation.
- ▌ Plugin Dev · spences10 bundleValidate, test, and distribute Claude Code plugins and marketplaces. Use when developing plugins, debugging validation errors, or preparing for distribution.
- ▌ Skill Creator · spences10 bundleDesign and create Claude Skills using progressive disclosure principles. Use when building new skills, planning skill architecture, or writing skill content.
- ▌ Orchestration · spences10 bundleMulti-agent orchestration patterns for Claude Code team mode. Use when coordinating teammates, decomposing complex tasks, or managing shared task lists.
- ▌ Techdebt Finder · spences10 bundleFind technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
- ▌ Structured Rpi · spences10 bundleEnhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints.
- ▌ CI Debug Workflow · spences10 bundleDebug failing CI pipelines, containers, and reproduce bugs locally. Use when CI is red, containers won't start, or need to reproduce bugs.
- ▌ Worktree Mastery · spences10 bundleGit worktree patterns for parallel Claude sessions. Run multiple Claude instances on same repo without conflicts.
- ▌ Advanced Prompting · spences10 bundleHigh-leverage prompts that challenge Claude's defaults. Use for "grill me", "prove it works", "scrap this", "what would 10x engineer do", "find ways this fails".
- ▌ Claude Md Maintenance · spences10 bundleMaintain CLAUDE.md files effectively. Use when adding lessons learned, updating conventions, or restructuring project instructions.
- ▌ Terminal Optimization · spences10 bundleTerminal setup for Claude Code. Use for Ghostty config, statusline customization, voice dictation, tmux worktrees.
- ▌ Improve Codebase Architecture · spences10 bundleExplore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
- ▌ Svelte Runes · spences10 bundleSvelte runes guidance. Use for reactive state, props, effects, or migration. Covers $state, $derived, $effect, $props, $bindable. Prevents reactivity mistakes.
- ▌ Svelte Styling · spences10 bundleSvelte CSS styling patterns. Use for scoped styles, CSS custom properties, style: directive, :global, or styling child components.
- ▌ Ecosystem Guide · spences10Guide to spences10's Claude Code ecosystem tools. Use when user asks which tool to use, how tools relate, or needs help choosing between MCP servers, skills, or CLIs.
- ▌ Svelte Components · spences10 bundleSvelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
- ▌ Svelte Deployment · spences10 bundleSvelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.
- ▌ Svelte Layerchart · spences10 bundleSvelte LayerChart patterns. Use for chart components with tooltip snippets, Chart context access, and all Svelte 5 snippet patterns for tooltips, gradients, highlights, and axes.
- ▌ Sveltekit Data Flow · spences10 bundleSvelteKit data flow guidance. Use for load functions, form actions, server/client data, and invalidation. Covers +page.server.ts vs +page.ts, serialization, fail(), redirect(), error(), invalidateAll().
- ▌ Sveltekit Structure · spences10 bundleSvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
- ▌ Svelte Template Directives · spences10 bundleSvelte template directives ({@attach}, {@html}, {@render}, {@const}, {@debug}). Use for DOM manipulation, third-party libs, tooltips, canvas, dynamic HTML. @attach replaces use: actions.
- ▌ Sveltekit Remote Functions · spences10 bundleSvelteKit remote functions guidance. Use for query(), form(), command(), and prerender() patterns in .remote.ts files.