JasonWarrenUK/claude-code-config Skills

This skill should be used when the user mentions "API design", "TypeScript API", "type-safe API", "endpoint design", "API validation", "Zod", discusses creating APIs, type safety, error handling, or API architecture. Addresses designing clean, type-safe APIs with validation, error handling, and documentation.

This skill should be used when the user mentions "Neo4j", "Cypher", "graph database", "graph query", discusses graph relationships, traversals, path finding, or needs help with Cypher syntax. Addresses Neo4j fundamentals, query patterns, performance optimization, and integration with relational databases.

This skill should be used when the user mentions "database design", "schema design", "graph database", "document database", "polyglot persistence", "data modeling", "Neo4j", "Supabase", "PostgreSQL", "MongoDB", discusses database architecture, choosing databases, or integrating multiple databases. Addresses when to use relational vs graph vs document databases and integration patterns.

# Debugging Skill ## Purpose Provide systematic debugging methodology for all types of bugs: runtime errors, test failures, logic bugs, performance issues, and production incidents. ## Core Methodology ### Five-Step Universal Framework 1. **REPRODUCE** - Make the bug happen reliably 2. **ISOLATE*

This skill should be used when the user mentions "domain model", "entity relationships", "data model", "system model", "map the domain", "what are the entities", "how does this connect", discusses designing a new feature or system, plans architecture, or needs to understand the shape of a problem before coding. Addresses model-first thinking — understanding the domain before writing solutions.

This skill should be used when the user mentions "dark patterns", "accessibility", "a11y", "privacy", "tracking", "analytics", "notifications", "user data", "GDPR", "consent", "manipulation", "sustainability", "performance budget", or when building user-facing features that collect data, send notifications, display urgency, or gate access. Addresses ethical constraints in software design — manipulation, accessibility, privacy, and sustainability.

This skill should be used when the user mentions "layout issues", "styling problems", "CSS fixes", "style consistency", "unify styles", "visual bugs", discusses frontend styling, works on UI components, or asks about component styling approaches. Applies to Svelte/SvelteKit projects primarily, with general frontend principles.

This skill should be used when the user mentions "git", "branch", "commit", "merge", "pull request", "PR", "version control", discusses branching strategy, commit conventions, collaboration workflows, or needs help with git operations. Addresses git best practices, branch management, commit messages, and LazyGit integration.

# OpenTUI Operative > Comprehensive reference for building terminal UIs with OpenTUI (@opentui/core). > Source: https://opentui.com/docs/ — all 29 documentation pages. --- ## Trigger Use when: user mentions "OpenTUI", "TUI", "terminal UI", "@opentui/core", renderables, or works on files importin

This skill should be used when the user says "remember", "note this", "add to CLAUDE.md", "don't forget", "keep in mind", or asks to store a preference, convention, or project-specific instruction. Stores memories in the project's CLAUDE.md file.

This skill should be used when the user mentions "scope", "MVP", "minimum viable", "too much", "overwhelmed", "where do I start", "feature creep", "simplify", "cut scope", "what's essential", or when a conversation reveals expanding complexity, multiple possible approaches, or analysis paralysis. Counterbalances the tendency to over-analyse and over-build.

This skill should be used when the user mentions "Svelte", "SvelteKit", "runes", "$state", "$derived", "$effect", "$props", discusses component patterns, reactive state, routing, load functions, form actions, or needs help with Svelte/SvelteKit code. Addresses Svelte 5 patterns using runes, SvelteKit conventions, and best practices.

This skill should be used when the user mentions "debugging", "troubleshooting", "bug", "error", "issue", "not working", "broken", discusses investigating problems, asks about debugging techniques, DevTools usage, or mentions they need to fix something. Addresses methodical problem-solving approach for software issues.

This skill should be used when the user mentions "write tests", "test coverage", "testing strategy", "unit tests", "integration tests", "e2e tests", "vitest", "jest", discusses testing approaches, asks about test patterns, or works on test files. Addresses testing fundamentals with emphasis on Vitest and Svelte component testing using pragmatic, risk-based approaches.

This skill should be used when the user mentions "user experience", "UX", "how would someone use this", "user flow", "onboarding", "confusing", "intuitive", "user needs", "persona", "user story", or when designing features that end-users interact with directly. Addresses understanding users through empathy and inference rather than formal research.