claude-plugins-registry

Condenses harness .md prompts (.claude/agents, commands, rules, skills) using caveman full + Opus, without losing information. Compresses verbose prose and tables, preserves code blocks/URLs/inline-code/headings via a deterministic gate. Overwrites in place (git is the review safety net). Use when asked to "condense/compress/shorten the agents/commands/rules/skills in .claude".

Audit .claude/agents/*.md frontmatter descriptions against the routing-description standard (condition-shaped, "Use proactively", 40-600 chars) and sync them with the project's CLAUDE.md `## Workflow & Agents` table or free-text mentions. Fixes descriptions in place, fixes stale/missing table rows, flags orphaned agents. Works on any existing project — not just one scaffolded by aia-harness. Use standalone, or after adding/editing agents by hand.

Generate or refresh rich intermediate CLAUDE.md files for strategic subdirectories of the target project. Reads .claude/rules/ (recursive), analyzes actual source files, maps rules to domains, and generates domain-specific CLAUDE.md with Key patterns, Applied rules, and Local conventions sections. Two-phase: map → approve → generate with diffs. Use after /aia-harness:init (step 5.6), or standalone to refresh existing files.

Seeds unit tests in a project that has none — installs the recommended framework for the stack, writes a real test in an existing module, wires the `test` script, and runs until green. Use when the project has no tests, when asked to "configure tests", "setup tests", "add tests", or "create test suite".

Use when setting up, scaffolding, bootstrapping, or improving a Claude Code "harness" for a project — hooks, skills, agents, rules, settings.json, .mcp.json, settings.local.json, worktree config, or per-domain CLAUDE.md. Triggers on "set up Claude Code", "harness engineering", "scaffold hooks/rules", "configure this project for Claude", "bootstrap .claude".

Review and upgrade the routing descriptions of candidate agents under templates/ (ECC, ag-kit, first-party) so each follows the best-practice standard — condition-shaped, with "Use proactively" and explicit trigger conditions. Writes the canonical description into the matching *_AGENT_WHEN_TO_USE map, propagates it into every agent file, and verifies the integrity gate. Use after editing any candidate agent, or standalone to sweep all of them.

Guards the Drizzle-kit generate → review → migrate flow for NestJS + Drizzle ORM projects. Use when changing the database schema or applying a migration.

Guides writing Jest unit tests for NestJS services and controllers using @nestjs/testing and mocked Drizzle DB. Use when adding or expanding unit tests.

Local pre-PR gate for NestJS projects. Runs lint, typecheck, tests, and build, then triggers the appropriate reviewer agent. Use before opening a pull request.

This skill should be used when the user mentions tickets, issues, backlog, PR, pull request, worktree, sprint, or any development project management activity. Also activate when the user says "create issue", "work on #N", "close ticket", "open PR", "merge PR", "view backlog", "create branch for issue", or when code was modified without a linked issue.

Use when asked to generate, build, prepare, optimize or assemble a /goal command for autonomous or overnight execution — triggers: "assemble goal", "generate autonomous goal", "prepare overnight task", "goal for autonomous session", "optimize goal", "goal builder".

This skill should be used to scaffold a complete new CRUD module in a PHP Adianti Framework project — Active Record model (TRecord) + list controller + form controller + menu.xml entry — by mirroring an existing module already in the codebase. Use when the user asks "create new module", "new Adianti module", "scaffold a module", "create CRUD", "new entity/registration", "create model + list + form", "add a new domain/entity", or names a new entity to register (e.g. "create a Fornecedores module"). Mirror the project's own conventions first; fall back to the adianti-framework skill references only when no existing module exists.

This skill should be used when the user asks about "worktree", "worktrees", "parallel sessions with worktree", "--worktree flag", "EnterWorktree", "ExitWorktree", ".worktreeinclude", "WorktreeCreate hook", "WorktreeRemove hook", "worktree.baseRef", "isolate subagents", "isolation worktree", "isolated sessions in Claude Code", "run Claude in parallel with worktrees", or any question about running parallel Claude Code sessions in isolated git worktrees.

Use when writing, wiring, reviewing, or debugging Claude Code hooks — especially JavaScript hooks. Covers exit codes, the node-resolver wrapper, fail-open vs blocking behavior, matchers, timeouts, and security. Triggers on "write a hook", "PreToolUse/PostToolUse/Stop hook", "hook not blocking", "format on save hook".

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents. When creating a new full-stack application from scratch, selecting tech stack, or scaffolding project structure. Use with /create workflow.

Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 13 templates for various tech stacks.

Token-efficient code review using Tree-sitter AST graphs and MCP. Cuts AI token usage on large codebases by computing the blast radius of changes instead of reading entire codebases. Uses a SQLite graph database for structural analysis. When reviewing code in large codebases (500+ files), when token costs are high, when making multi-file changes with cross-module dependencies, or when working with monorepos. Also for dead code detection, architecture visualization, and refactoring previews. NOT for small projects under 200 files with isolated single-file changes.

2D game development principles. Sprites, tilemaps, physics, camera.

3D game development principles. Rendering, shaders, physics, cameras.

Game art principles. Visual style selection, asset pipeline, animation workflow.

Game audio principles. Sound design, music integration, adaptive audio systems.

Game design principles. GDD structure, balancing, player psychology, progression.

Mobile game development principles. Touch input, battery, performance, app stores.

Multiplayer game development principles. Architecture, networking, synchronization.

PC and console game development principles. Engine selection, platform features, optimization strategies.

Game development orchestrator. Routes to platform-specific skills based on project needs. When building games with Unity, Godot, Unreal, Phaser, or any game engine. Routes to platform-specific sub-skills.

VR/AR development principles. Comfort, interaction, performance requirements.

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support. When internationalizing an app, managing translations, detecting hardcoded strings, or adding RTL support.

Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps. When designing mobile app interfaces for iOS/Android, React Native, or Flutter. Touch interaction and platform conventions. NOT for web apps.

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture. When using Tailwind CSS v4, implementing design tokens, container queries, or modern CSS patterns with Tailwind.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". When auditing web UI for best practices, checking accessibility, or reviewing design against Web Interface Guidelines.

Use when choosing, recommending, or wiring MCP servers for a project's .mcp.json. Curated list of strategic MCP servers with safe configuration (env placeholders, scoping). Triggers on "add an MCP", "which MCP servers", "configure .mcp.json", "strategic MCPs".

C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.