All authors

Claude Skills by Kastalien-Research
github.com/Kastalien-Research112 skills1 installs191 views
- Next Best PracticesNext.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundlingVotes: 0GitHub stars: 64
- Nextjs Supabase AuthExpert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.Votes: 0GitHub stars: 64
- Vercel React Best PracticesReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.Votes: 0GitHub stars: 64
- Coolify ComposeConvert 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.Votes: 0GitHub stars: 64
- Crafting Effective ReadmesUse when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.Votes: 0GitHub stars: 64
- DiataxisStructure, 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.Votes: 0GitHub stars: 64
- Frontend Design PrinciplesCreate 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.Votes: 0GitHub stars: 64
- Improving PromptsUse 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 improvementsVotes: 0GitHub stars: 64
- Reducing EntropyUse when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.Votes: 0GitHub stars: 64
- Researching CodebasesUse 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 findingsVotes: 0GitHub stars: 64
- Writing Clearly And ConciselyUse when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.Votes: 0GitHub stars: 64
- Writing Cli SkillsGuide for writing skills that wrap CLI tools. Use when creating a new CLI skill. For review, run through the Checklist section.Votes: 0GitHub stars: 64
- AssumptionsManage the assumption registry — track, verify, and query assumptions about external dependencies and system behavior. Prevents costly rediscovery of known failures.Votes: 0GitHub stars: 64
- Capture LearningCapture significant learnings from the current work session. Structures insights for future sessions and updates agent memory.Votes: 0GitHub stars: 64
- Claude PromptWrite or improve prompts for Codex 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.Votes: 0GitHub stars: 64
- Code ModeGuide for designing, implementing, and advising on MCP servers that use Code Mode — the pattern where an LLM writes and executes code to orchestrate API calls instead of calling individual tools one at a time. Use this skill whenever the user mentions Code Mode, MCP tool proliferation, context window bloat from MCP tools, programmatic tool calling, LLM code execution in MCP, building a Code Mode server, or wants to compress a large API into a small MCP surface. Also use when the user asks how...Votes: 0GitHub stars: 64
- Deploy Team HubDeploy a multi-agent team that coordinates through Thoughtbox Hub.Votes: 0GitHub stars: 64
- DiagramGenerate architecture diagrams for a codebase subsystem or module. Explores source files and produces Mermaid diagrams in docs/.Votes: 0GitHub stars: 64
- DistillExtract reusable principles and decision frameworks from accumulated experience. Use after significant work sessions, project milestones, or when you notice recurring patterns worth codifying.Votes: 0GitHub stars: 64
- Effect TsEffect-TS expert — write, debug, refactor, and explain code using the Effect ecosystem (effect, @effect/platform, @effect/rpc, @effect/cli, @effect/schema, @effect/cluster). Use this skill whenever the user works with Effect-TS code, mentions Effect services/layers/fibers/streams/schedules, asks about Effect error handling or dependency injection, wants to migrate code to Effect, or asks questions like 'how do I do X in Effect'. Also trigger when you see Effect imports in code being discussed...Votes: 0GitHub stars: 64
- EvalView and manage the evaluation harness — session metrics, baselines, trend analysis, and regression detection. The feedback loop that tells the system whether improvements actually improved things.Votes: 0GitHub stars: 64
- ExperimentRun parallel experiments across git worktrees. Define competing approaches to the same problem, dispatch sub-agents to implement each in isolation, then compare results. Use when you have 2-5 alternatives and want to test all of them before committing to one.Votes: 0GitHub stars: 64
- HddDEPRECATED — use workflow Stage 2 (spec + frontmatter claims). Historical HDD docs are in docs/decisions/archive/.Votes: 0GitHub stars: 64
- Hub AuditRun 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.Votes: 0GitHub stars: 64
- Hub CollabOrchestrate a multi-agent collaboration demo on the Thoughtbox Hub. Spawns MANAGER, ARCHITECT, and DEBUGGER agents that coordinate through shared workspaces, problems, proposals, and channels.Votes: 0GitHub stars: 64
- ImplementImplement a specification using a TDD-oriented workflow. Extracts requirements, generates tests first, then implements to pass the tests. Includes spiral detection and acceptance gates.Votes: 0GitHub stars: 64
- KnowledgeUnified cross-store knowledge query. Searches MEMORY.md, Thoughtbox knowledge graph, git history, and assumption registry in parallel, returning results with provenance.Votes: 0GitHub stars: 64
- Peer Notebook Delivery GuardGovern ADR-022 MCP peer notebook implementation units. Use before or during durable control-plane, manifest lifecycle, web app inspection, runtime provider, or isolation/policy hardening work to prevent mock substitution, scope drift, and incomplete acceptance evidence.Votes: 0GitHub stars: 64
- Research TaskExecute 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.Votes: 0GitHub stars: 64
- Session ReviewGenerate a structured session summary for cross-session continuity. Captures key decisions, hypotheses, partial work, and knowledge references. Output is written to .Codex/session-handoff.json for the next session to load automatically.Votes: 0GitHub stars: 64
- Source Command Hdd DecidePhase 5 router for accept/reject ADR decisionVotes: 0GitHub stars: 64
- Source Command Hdd ResearchPhase 1 router for HDD researchVotes: 0GitHub stars: 64
- Source Command Hdd Stage AdrPhase 2 router for staging ADR creationVotes: 0GitHub stars: 64
- Source Command Hdd ValidatePhase 4 router for hypothesis validationVotes: 0GitHub stars: 64
- StatusGenerate a status report across all workstreams using git history and GitHub issues. Shows active work, recent changes, and open PRs.Votes: 0GitHub stars: 64
- SupabaseManage Supabase local and hosted infrastructure. Migrations, schema diff, status, reset, push, and inspection. Wraps the Supabase CLI with project-specific context and gotcha avoidance.Votes: 0GitHub stars: 64
- SynthesizeFuse insights from multiple knowledge sources (code, docs, memory, research, web) into coherent understanding. Use when you have scattered information that needs integration.Votes: 0GitHub stars: 64
- TasteRun a taste evaluation on a research proposal or technical direction. Determines whether to proceed, simplify, defer, or kill before committing research effort.Votes: 0GitHub stars: 64
- TeamOrchestrate an Agent Teams session with Thoughtbox as the reasoning substrateVotes: 0GitHub stars: 64
- Test SuiteRun 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.Votes: 0GitHub stars: 64
- Theseus ProtocolThoughtbox-first Theseus workflow for behavior-preserving refactors. Use this when structure changes but behavior must stay fixed and scope drift needs hard boundaries.Votes: 0GitHub stars: 64
- Thoughtbox DebugTrigger 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.Votes: 0GitHub stars: 64
- Thoughtbox DecisionStructure decisions with parallel hypothesis exploration and knowledge graph persistence. Triggers on: "decide", "choose between", "which approach", "compare options", "evaluate alternatives", "tradeoff analysis".Votes: 0GitHub stars: 64
- Thoughtbox EvolutionA-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...Votes: 0GitHub stars: 64
- Thoughtbox Knowledge QueryCross-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.Votes: 0GitHub stars: 64
- Thoughtbox OnboardGateway 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 Tho...Votes: 0GitHub stars: 64
- Thoughtbox RefactorFriction-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.Votes: 0GitHub stars: 64
- Thoughtbox ResearchStructured research using Thoughtbox IRCoT (Interleaved Retrieval and Chain-of-Thought). Triggers on: "research", "investigate", "explore", "literature review", "what do we know about".Votes: 0GitHub stars: 64
- Thoughtbox Session ReviewAnalyze 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.Votes: 0GitHub stars: 64
- Thoughtbox TeamSpawn 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.Votes: 0GitHub stars: 64