Delegate a long-tail investigation (log dig, audit, transcript analysis) to a peer agent and take back only a summary. Use when the raw output would crowd out 1000+ tokens of the primary session that do not need to live there.
Spawn N peer agents on genuinely independent subtasks, wait for every result, then merge. Use when subtasks do not read each other's outputs and the wall-clock saving is worth N× the token cost.
Delegate a verification check to a peer agent and consume a structured pass/fail/needs-info verdict instead of free-form text. Use when you want a second agent to check work against explicit criteria without rewriting it.
Expert patterns for 2D animation in Godot using AnimatedSprite2D and skeletal cutout rigs. Use when implementing sprite frame animations, procedural animation (squash/stretch), cutout bone hierarchies, or frame-perfect timing systems. Trigger keywords: AnimatedSprite2D, SpriteFrames, animationfinished…
Expert patterns for Godot 3D lighting including DirectionalLight3D shadow cascades, OmniLight3D attenuation, SpotLight3D projectors, VoxelGI vs SDFGI, and LightmapGI baking. Use when implementing realistic 3D lighting, shadow optimization, global illumination, or light probes. Trigger keywords: DirectionalLight3D…
Manage and explain a repository's .agent-kb/ knowledge base (KB) for coding agents. Use when the user works with the KB — asks how the KB or its commands behave, sets up project memory, records durable knowledge, refreshes the KB runtime protocol, validates routes/links, compiles inbox notes into topics, trims stale…
Project Context System — structured project memory for any project via layered docs and codebase index. Use for: documenting projects, writing PRD/roadmap, generating codebase repo-wiki, capturing requirements/decisions, writing dev notes, building doc navigation index, compacting bloated docs, auto-detecting stale…
Use this skill when delegating coding work to Factory Droid's droid CLI for code analysis, edits, specification-first implementation, worktree isolation, or multi-agent missions. Do not use it for small direct edits or when Factory Droid is unavailable.
Validates that all specification files in the Cognitive OS repo pass markdownlint, are properly formatted, contain required sections, and maintain consistency between master spec and harness adapters.
A step-by-step debugging guide based on reproducing a failure, testing one explanation at a time, making the smallest relevant change, and checking the result. It includes a stopping rule for repeated unsuccessful fixes.
A workflow for turning corrections into written rules that can be reused in later coding sessions. It records the situation, the mistake, the correct action, and a clear if-then test.
Create an implementation plan — discovery in the real codebase first, then a plan document with verified code anchors, spec impact, and dependencies, filed under Active in the plans hub. Use when the user says "plan ", "write a plan for ...", or asks to turn a backlog task or accepted feature into work.
Brownfield-first workspace onboarding — scan the codebase and draft data/product.md plus starting architecture and spec docs from what the code shows, interview the developer only for what the code can't answer, mark the onboarding tasks done, and delete the example documents. Use when the user says "run the setup"…
Verify that implementation matches the graph — check a plan's tasks, spec requirements, and scenarios against the actual code before shipping, or sweep the whole workspace for doc↔code drift. Use when the user says "verify ", "is this ready to ship", "audit the docs", or "check for drift".
Use when implementing any feature or bugfix, before writing implementation code. Triggered by keywords: TDD, BDD, test-first, test-driven, write-test-first.
Use in a dedicated subagent when completing tasks, implementing major features, or doing post-TDD code review before merge to verify work meets requirements.
Use in a dedicated subagent for post-TDD blind unit-test review against requirements and public contracts to find missing cases, wrong assertions, and brittle tests.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright…
★not rated 5 4mo agoA62 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: