Skill Claude CodeCodex
General guide for using the sqlite3 CLI to build composable knowledge databases. Use this skill when creating SQLite databases, designing schemas, querying data, managing relationships, or building new sqlite-based domain skills. Provides the foundational patterns that all specialized sqlite skills build upon.
Skill Claude CodeCodex
Personal note-taking, thinking trails, and knowledge management using plain SQLite. Supports capture-heavy workflows with clear provenance tracking, AI-generated thinking snapshots (breadcrumbs), and synthesis into permanent knowledge. Uses the sqlite3 CLI directly with SQL schemas for notes, resources, clippings…
Skill Claude CodeCodex
Use when writing, revising, or judging a skill. A skill is a packet of wisdom that changes how a situation is seen, not a procedure to follow — dense, composable, and worth loading. Trigger on creating a new skill, editing an existing one, deciding whether something should be a skill at all, or reviewing a set of…
Skill Claude CodeCodex
Use when reviewing written code — your own or someone else's. Concerns finding what the code will cost later rather than what it violates now, and saying it in a way that can be acted on. Trigger on requests to review, critique, or give feedback on an implementation, and before handing off work you wrote. Do NOT use…
Skill Claude CodeCodex
Use when work is about to be split across multiple agents, or when deciding whether it should be. Concurrency is a property of the change, not a scheduling decision — what can proceed at once is determined by what the pieces have to agree on. Trigger on any request to parallelise, fan out, delegate to subagents, or…
Skill Claude CodeCodex
Use when planning any multi-step change, or when a plan already exists and is about to be executed. A plan is a sequence of ambiguity collapses, not a list of tasks — each step must end at a state that can be checked, and the checks must be capable of failing. Trigger on requests to plan, sequence, break down, stage…
Skill Claude CodeCodex
Use when deciding where the boundaries in a system go — what becomes a module, a service, a process, a package; what gets extracted, merged, or left duplicated. Concerns which cut isolates change rather than which cut looks tidy. Trigger on refactors, restructuring, "this file is too big", extracting shared code, and…
Skill Claude CodeCodex
Use when deciding what the concepts in a system are and what they are called — the types, the boundaries between contexts, the vocabulary. Concerns whether the model tells the truth about the problem and reads as a story a human can follow. Trigger on designing or changing types, naming things, modelling a business…
Skill Claude CodeCodex
Use when an idea needs to become something buildable, or needs to die honestly before anything is built. Concerns the alternation between opening a possibility up and closing it down, and finding the fastest thing that would settle whether it is worth doing. Trigger when someone arrives with a concept rather than a…
Skill Claude CodeCodex
Use when thinking needs to open rather than close — generating possibilities, breaking out of a stuck frame, reading the state of a creative process, or noticing that a session has gone flat, cynical, or circular. A deck of moves for the infinite game of ideation, where good thinking is playing the right card at the…
Skill Claude CodeCodex
Use when carrying out a change that is already decided — building the thing rather than choosing it. Concerns staying oriented while the code is in motion — knowing how far from the last checkpoint, noticing when the plan has stopped matching what is being found, and stopping rather than compensating. Trigger on…
Skill Claude CodeCodex
Use when something is wrong and the cause is not yet known — failures, regressions, flaky behaviour, performance problems, incidents, or a user report that does not match what the code appears to do. Concerns holding the difference between what is observed and what is believed, and spending each action on the question…
Skill Claude CodeCodex
Explore a problem space before committing to a direction. Use this whenever the user is circling an idea rather than executing one — thinking out loud, asking "what's interesting here", "I've been wondering about X", "is this worth doing", "how should I think about this", or describing an itch without a plan. Also use…
Skill Claude CodeCodex
Use when arriving in an unfamiliar codebase, or returning to one after long enough that its shape has been forgotten. Concerns building a working model of what the system is and where its decisions live, before touching anything. Trigger at the start of work in a new repository, or when a change is about to be made…
Skill Claude CodeCodex
Entry point for planning work — routes to the skills that own the substance. Use when the user asks to plan, sequence, or scope something and it is not yet clear which kind of planning is needed.
Skill Claude CodeCodex
Use when a specific question must be answered before work can sensibly proceed — how something currently works, whether an approach is viable, what already exists, what a change would touch. Concerns answering the question that was actually asked, at a confidence level stated honestly. Trigger on investigation…
Skill Claude CodeCodex
Use at a checkpoint after real friction — a task where something was repeatedly confusing, a skill misfired or failed to fire, or a workaround was invented that should not have been needed. Concerns turning friction into a change to the skills themselves, and knowing when the right change is to cut rather than add.…
Skill Claude CodeCodex
Create, update, and manage Claude Code skills. Use when working with SKILL.md files, slash commands, or extending Claude's capabilities.
Skill Claude CodeCodex
Use during any implementation, design, refactor, or debugging task, in any language or codebase. Before changing anything that touches an existing domain concept, rule, type, or invariant, find what the change collides with and name the routes through it — instead of letting the first workable route settle the…
Skill Claude CodeCodex
Use when writing or restructuring code in any language. Concerns the shape of the code itself — what is data and what is function, where effects live, what the names say, when a module has stopped having one subject. Trigger on any implementation task, and on review of code that works but reads badly. Do NOT use for…
Skill Claude CodeCodex
This skill should be used when working on Bevy game engine projects. It provides specialized knowledge for Bevy's Entity Component System (ECS) architecture, component-driven design patterns, system ordering, UI development, build strategies, and common pitfalls. Use this skill when implementing game features…
Skill Claude CodeCodex
Reference for building and distributing Claude Code plugins — plugin.json and marketplace.json structure, bundling commands, agents, skills and hooks, versioning, and publishing a marketplace. Use when creating or packaging a plugin, setting up a marketplace, or debugging why a plugin's components are not loading.
Skill Claude CodeCodex
This skill should be used whenever domain modeling is taking place. It provides specialized guidance for type-driven and data-driven design based on Rich Hickey and Scott Wlaschin's principles. The skill helps contextualize current modeling within the existing domain model, identifies inconsistencies, builds…
Skill Claude CodeCodex
Interact with a running Godot game via MCP — launch, screenshot, click, inspect scene tree, get/set properties, call methods, run dev-console commands. Powered by godot-mcp + the GodotMCPBridge autoload (protocol v4.0).