Kastalien-Research.

assumptions

Manage the assumption registry — track, verify, and query assumptions about external dependencies and system behavior. Prevents costly rediscovery of known failures.

capture-learning

Capture significant learnings from the current work session. Structures insights for future sessions and updates agent memory.

claude-opus-4-6-prompting

>

claude-prompt

Write or improve prompts for Claude using Anthropic's official best practices. Creates system prompts, agent prompts, tool descriptions, and MCP resource templates. Pass an existing prompt to improve it, or describe what you need to create one from scratch.

coolify-compose

Convert Docker Compose files to Coolify templates. Use when creating Coolify services, converting docker-compose.yml for Coolify deployment, working with SERVICE_URL/SERVICE_PASSWORD magic variables, or troubleshooting Coolify compose errors.

crafting-effective-readmes

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

diagram

Generate architecture diagrams for a codebase subsystem or module. Explores source files and produces Mermaid diagrams in docs/.

diataxis

Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.

escalate

Format a structured escalation to the human decision-maker (Chief Agentic). Use when hitting an escalation threshold.

frontend-design-principles

Create polished, intentional frontend interfaces. Use this skill when building any UI — dashboards, admin panels, landing pages, marketing sites, or web applications. Routes to specialized guidance based on context.

hdd

DEPRECATED — use workflow Stage 2 (spec + frontmatter claims). Historical HDD docs are in docs/decisions/archive/.

hub-audit

Run an Agent-Native Architecture Audit using Thoughtbox Hub for multi-agent coordination. Spawns 3 auditor agents and 1 synthesizer that collaborate through structured channels, cross-reference findings, and build consensus on scores.

hub-collab

Orchestrate a multi-agent collaboration demo on the Thoughtbox Hub. Spawns MANAGER, ARCHITECT, and DEBUGGER agents that coordinate through shared workspaces, problems, proposals, and channels.

improving-prompts

Use when optimizing CLAUDE.md, AGENTS.md, custom commands, or skill files for Claude 4.5 models - applies documented Anthropic best practices systematically instead of inventing improvements

knowledge

Unified cross-store knowledge query. Searches MEMORY.md, Thoughtbox knowledge graph, git history, and assumption registry in parallel, returning results with provenance.

mcp-code-mode

>

nextjs-supabase-auth

Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.

peer-notebook-delivery-guard

>

reducing-entropy

Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.

research-task

Execute a research task using compositional workflow planning. Characterizes the task, selects an approach from a library of research strategies, executes it, and self-evaluates output quality.

researching-codebases

Use when answering complex questions about a codebase that require exploring multiple areas or understanding how components connect - coordinates parallel sub-agents to locate, analyze, and synthesize findings

session-review

Generate a structured session summary for cross-session continuity. Captures key decisions, hypotheses, partial work, and knowledge references. Output is written to .claude/session-handoff.json for the next session to load automatically.

source-command-hdd-decide

Phase 5 router for accept/reject ADR decision

source-command-hdd-hdd

[DEPRECATED] Thin HDD router — use /hdd skill instead

source-command-hdd-research

Phase 1 router for HDD research

source-command-hdd-stage-adr

Phase 2 router for staging ADR creation

source-command-hdd-validate

Phase 4 router for hypothesis validation

source-of-truth-preflight

>

synthesize

Fuse insights from multiple knowledge sources (code, docs, memory, research, web) into coherent understanding. Use when you have scattered information that needs integration.

test-suite

Run behavioral smoke tests against the live Thoughtbox Code Mode MCP server. Verifies the public `/mcp` surface (`thoughtbox_search`, `thoughtbox_execute`, `thoughtbox_peer_notebook`) plus the main execution paths behind it.

theseus-protocol

Thoughtbox-first Theseus workflow for behavior-preserving refactors. Use this when structure changes but behavior must stay fixed and scope drift needs hard boundaries.

thoughtbox-team

Spawn an Agent Team with a background Thoughtbox analyst teammate. The analyst monitors your reasoning sessions for evolution candidates, contradictions, and generates periodic digests. Use this at the start of any deep Thoughtbox reasoning session, when you're about to record many thoughts and want background analysis. Triggers on "start thoughtbox team", "I want a session analyst", "monitor my reasoning", or at the start of any session where you plan to use Thoughtbox extensively.

thoughtbox:debug

Trigger when debugging something unexpected — a test failure, surprising behavior, production incident, or any situation where initial attempts aren't working. Prevents the common agent failure mode of trying random things when stuck. Use when "the first fix didn't work", "this is behaving unexpectedly", "I'm stuck", "why is this happening", or after 2+ failed attempts to fix something.

thoughtbox:decision

>

thoughtbox:evolution

A-Mem thought evolution — check which prior thoughts should be updated when a significant new insight arrives. Spawns a lightweight subagent to classify prior thoughts as UPDATE or NO_UPDATE, then applies revisions. Use during long reasoning sessions when you reach a synthesis, make a decision, or discover something that changes earlier assumptions. Triggers on "this changes what I thought earlier", "update prior reasoning", "evolve thoughts", or automatically on conclusion/synthesis thoughts in sessions >10 thoughts.

thoughtbox:knowledge-query

Cross-session knowledge retrieval from the Thoughtbox knowledge graph. Searches entities, traverses relations, retrieves observations, and synthesizes findings from past sessions. Use when you need to recall prior decisions, check what's already known about a topic, find related insights, or build on past work. Triggers on "what do we know about", "have we seen this before", "recall", "prior decisions about", "knowledge graph", or when starting work that might have prior context.

thoughtbox:onboard

Gateway orientation for agents using Thoughtbox MCP for the first time. Use this skill when you connect to a Thoughtbox MCP server and need to understand what's available, how to structure reasoning sessions, or how to use the tb SDK. Also use when you're unsure which Thoughtbox operation to use for a task, or when you want to check what modules and patterns are available. Triggers on first Thoughtbox interaction, "how do I use Thoughtbox", "what can Thoughtbox do", or any confusion about Thoughtbox operations.

thoughtbox:refactor

Friction-gated refactoring using the Theseus protocol. Prevents scope creep and refactoring fugue state by enforcing file scope boundaries, visa-based expansion, checkpoint audits, and a brittleness counter. Use when refactoring code, restructuring modules, renaming across files, or any task where "structure changes but behavior must stay the same". Triggers on "refactor", "restructure", "rename across", "extract module", "move code", or when a change touches 3+ files without adding features.

thoughtbox:research

>

thoughtbox:session-review

Analyze completed Thoughtbox sessions to extract patterns, anti-patterns, and learnings for the knowledge graph. This is the learning loop that makes Thoughtbox improve over time. Use after completing a reasoning session, when reviewing past sessions for insights, or when you want to assess reasoning quality. Triggers on "review session", "what did I learn", "extract insights", "analyze reasoning", "session retrospective", or proactively after any significant session completes.

ulc-loop

Start a Unified Loop Controller session via Ralph Wiggum. Autonomously works through backlog, dispatches agents, and explores via QD when idle.

ulysses-protocol

Thoughtbox-first Ulysses workflow for surprise-gated debugging. Use this when debugging gets uncertain and you need explicit plan, outcome, and reflection discipline without relying on local shell state.

workflow-brainstorming

This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.

workflow-ideation

Evaluate whether an idea is worth implementing by asking structured questions about outcomes, alignment, and opportunity cost. Stage 1 of the development workflow.

workflow-reflection

Finalize the workflow by reflecting on the process, moving ADRs, closing issues, and preparing for merge. Stage 8 of the development workflow.

workflow-revision

Iterate on implementation fixes surfaced by review until all claims are verified. Stage 6 of the development workflow.

workflow-tournament

Execute an implementation by dispatching multiple sub-agents to parallel Git worktrees. Each builds the entire feature independently, and the best implementation is selected and merged.

workflows-compound

Capture learnings from the workflow into reusable documentation. Stage 7 of the development workflow.

workflows-plan

Transform spec (with frontmatter claims) into an implementation plan with task decomposition and sub-agent assignment. Stage 3 of the development workflow.

workflows-review

Verify implementation claims by dispatching review agents. Stage 5 of the development workflow.

workflows-work

Execute the implementation plan by dispatching sub-agents for each task. Stage 4 of the development workflow.

writing-cli-skills

Guide for writing skills that wrap CLI tools. Use when creating a new CLI skill. For review, run through the Checklist section.