decision-records
Where a decision goes and how it is written down so the next reader finds it: architecture decision records (ADRs, amended by addendum and never by silent edit), protocol-change proposals for frozen interfaces, design notes with a status lifecycle, adversarial review waves with a triage roll-up, and corrections filed on the issue rather than only in a commit. Use when a decision was just made and needs a home, when an existing ruling needs revisiting, when a review wave is being filed, or with `init` to scaffold the whole decision layout in a repo that has none. Pairs with `handoff` (the next.md rewrite) and `doc-graph` (per-package docs).
explainer-video
>
doc-graph
Set up and maintain a per-package documentation graph in any repo: one CLAUDE.md per package (Purpose, Key Types, Relationships, Traffic, Invariants, Deep Docs) with a byte-identical AGENTS.md mirror, a no-toolchain gate script that checks coverage, mirror equality, git-time staleness and file:line citation drift in docs/, and a repo-customized doc-gardening skill that regenerates stale docs from source. Use `init` in a repo that has none of this (it detects the language and layout, asks what the repo's traffic vocabulary is, installs scripts/doc_check.sh, a make target, a CI job, and .claude/skills/doc-gardening/), or `check` and `garden` in a repo that already has it. Pairs with `decision-records` and `handoff`.
doc-gardening
>
litbucket
Publish, search, and inspect internal Litbucket static artifacts. Use when asked to publish a site, dashboard, notebook, report, or other static bundle to an internal address, to find one that already exists, or to share a generated artifact with the team. Triggers include "publish this to litbucket", "put this on lightning.wiki", "find the <name> dashboard", "give me a link to this report".
technical-writing
Clear-writing guide distilled from Steven Pinker's \"The Sense of Style,\" with mechanical checks from Google's developer documentation style guide. Use when writing or revising prose that must be clear to a reader — documentation, design docs, specs, explanations, essays, emails, reports, RFCs, release notes — or when asked to make writing clearer, tighter, less academic, or less jargon-laden. Activate for \"make this clearer\", \"tighten this\", \"why is this hard to read\", \"edit this for clarity\", or any prose-quality pass. Also activate when prose is dense, overwritten, or hard to parse on the first read: sentences packing three ideas, invented metaphors and analogies the reader must decode, anthropomorphized systems, or phrasing that shows off instead of informing.
handoff
Rewrite the repo's session handoff document (docs/next.md) at the end of a body of work: re-baseline every claim against the tree and CI rather than carrying it forward, name where the previous edition was wrong, record the rulings nobody should re-litigate and the gaps deliberately left open, and order what to do next with exit criteria. Also `init` to create the handoff and a starter docs/execution.md (how waves are planned, sub-agents briefed, and gates verified) in a repo that has neither. Use when finishing a milestone, a wave, or a PR series; when a fresh session cannot tell where the tree is; or when next.md and the code disagree. Pairs with `decision-records`.
hunk
Line-level git staging and non-interactive rebase for agents that know exactly which lines they changed. Use when you need atomic commits carved out of a larger diff, or when you need to squash/drop/reorder/reword commits without interactive prompts.
incremental-commit
Create incremental, atomic commits that tell a story with detailed commit messages. Use when the user asks to commit changes, split a diff into logical commits, or wants a clean commit history instead of one large commit. Triggers include "commit this", "make atomic commits", "break this into commits", "/incremental-commit".
test-refine
Refines an existing Go test suite — removes trivial/duplicate tests, strengthens weak assertions, reshapes tests around invariants, and closes branch-coverage gaps. Uses code-guided coverage and (when available) gremlins mutation-testing survivor data rather than relying on line coverage alone. Use when test quality is uneven, after a test-generation pass, before opening a PR, or as a quality gate on critical paths (consensus, channel state, payment flows). Triggers: "refine these tests", "tests are bloated", "tighten assertions", "remove trivial tests", "audit test quality", "/test-refine".
reactive-polling
Poll for changes to any value and trigger React re-renders when it changes.
ui-useframe
Sync UI elements outside the Canvas with the render loop using R3F v10's external useFrame.
verekia-architecture
Day-to-day coding style and patterns for R3F game development with Miniplex ECS.
low-health
Display a pulsing red vignette overlay when the player's health is low.
miniplex
Use Miniplex for minimalistic Entity Component System with TypeScript support.
pushback
Make enemies flash white and rock back and forth when receiving damage.
verekia-setup
Verekia's preferred project setup with Next.js Pages Router, Tailwind 4, oxfmt, oxlint, and TypeScript.
health-bars
Display health bars above characters using CSS styling.
weapon-trail
Create a ribbon trail effect that follows a weapon's movement.
zustand-entities
Use Zustand as a simple state store for entity management (not a true ECS).
r3f-setup
Set up a React Three Fiber project with WebGPU support.
damage-numbers
Display floating damage numbers that animate upward and fade out, with support for critical hits.
bone-attachment
Attach meshes to bones of a skinned mesh, such as attaching a sword to a character's hand.
koota
Use Koota for data-oriented Entity Component System architecture with React bindings.
camera-shake
Shake the camera when the player takes damage or on impacts for visual feedback.
smooth-interpolation
Animate values smoothly using exponential decay instead of linear interpolation.
netbox-integration-best-practices
Best practices for building integrations with NetBox REST and GraphQL APIs. Use when building NetBox API integrations, reviewing integration code, troubleshooting NetBox performance issues, planning automation architecture, writing scripts that interact with NetBox, using pynetbox, configuring Diode for data ingestion, or implementing NetBox webhooks.
laravel-api
Build production-grade Laravel REST APIs using opinionated architecture patterns with Laravel best practices. Use when building, scaffoling, or reviewing Laravel APIs with specifications for stateless design, versioned endpoints, invokable controllers, Form Request DTOs, Action classes, JWT authentication, and PSR-12 code quality standards. Triggers on "build a Laravel API", "create Laravel endpoints", "add API authentication", "review Laravel API code", "refactor Laravel API", or "improve Laravel code quality".
agent-tower-plugin
Multi-agent deliberation for Claude Code - orchestrate AI coding assistants (Claude, Codex, Gemini) for council, debate, and consensus workflows
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent to review implementation against plan or requirements before proceeding
openapi-specification
OpenAPI 3.x specification design, schema patterns, and validation for REST API contracts. Use when creating or maintaining API specifications, generating documentation, or validating API contracts.
skill-creator
Guide for creating effective skills. Use when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
sharing-skills
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
session-management
Use when loading, saving, or reflecting on session context - provides structured workflows for session lifecycle management and reflection outputs.
security-testing-patterns
Security testing patterns including SAST, DAST, penetration testing, and vulnerability assessment techniques. Use when implementing security testing pipelines, conducting security audits, or validating application security controls.
feature-implementation
Use when implementing a feature or multi-file code change - provides structured implementation flow with persona selection, validation, and testing guidance.
python-performance-optimization
Python performance optimization patterns using profiling, algorithmic improvements, and acceleration techniques. Use when optimizing slow Python code, reducing memory usage, or improving application throughput and latency.
super-saiyan
Maximum visual excellence for any UI platform. Use when building user interfaces, styling components, or polishing visual elements.
implementation-workflow
Use when turning PRDs or feature specs into actionable implementation workflows - provides structured task decomposition, dependency mapping, and validation gates.
internal-comms
A set of resources to help write all kinds of internal communications, using company-specific formats. Use when asked to write internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
evaluator-optimizer
Iterative refinement workflow for polishing code, documentation, or designs through systematic evaluation and improvement cycles. Use when refining drafts into production-grade quality.
interaction-design
User flow design, micro-interactions, and interface behavior patterns with state management for all interaction conditions. Use when designing natural interactions, feedback systems, or handling error states.
helm-chart-patterns
Helm chart development patterns for packaging and deploying Kubernetes applications. Use when creating reusable Helm charts, managing multi-environment deployments, or building application catalogs for Kubernetes.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
multi-llm-consult
Consult external LLMs (Gemini, OpenAI/Codex, Qwen) for second opinions, alternative plans, independent reviews, or delegated tasks. Use when a user asks for another model's perspective, wants to compare answers, or requests delegating a subtask to Gemini/Codex/Qwen.
multi-perspective-analysis
Adopt multiple expert personas sequentially for complex problem analysis from diverse perspectives. Single-agent only — do NOT spawn sub-agents.
socratic-questioning
Guide discovery through questioning techniques and pattern recognition for Clean Code, GoF design patterns, and architectural decisions. Use when coaching developers, facilitating design discussions, or helping teams discover solutions.
Page 808 of 1671 · 83523 results
