AnimalAL-v1

Starts the AnimalKernel.Web site via run-dev script, uses Context7 for React best practices and Cursor's built-in browser (cursor-ide-browser) for browser-driven development and testing. Use when building or testing the clientapp UI, when the user invokes animal-kernel-web-dev with a follow-up task, or when developing the AnimalKernel.Web frontend with expert UX and browser verification.

Plugin Scaffolding Generator - Creates complete plugin implementations following project patterns. Use when user says "add a plugin for [feature]", "create [Name]Plugin", or "scaffold a new plugin".

Analyzes IntegrationTesterApp test-result JSON (test-results_*.json, multi-model-results_*.json) and produces in-depth analysis of flow (prompt → tools called → response → assertions) and responses, plus actionable fix recommendations. Resolves "latest" or no path to the newest file in src/IntegrationTesterApp/test-results/. Use when the user says /analyze-test-json, "analyze test json", "analyze test results", "analyze latest test results", or @-mentions a test-results or multi-model-results JSON file and asks for analysis or recommendations.

Audits passed tests only: checks that each model response is logically consistent with the user's question (topic, entities, numbers, intent). Does not re-check assertions; adds a semantic-sanity layer so tests that pass on keywords/tools but give off-topic or contradictory answers are surfaced. Resolves JSON like analyze-test-json (test-results_*.json, multi-model-results_*.json in src/IntegrationTesterApp/test-results/). Use when the user says /check-test-logical-resp, "check logical responses", "check test responses make sense", "audit passed tests for logic", or @-mentions a test-result JSON and asks whether responses were logical.

Generates the provider pattern (interface plus fake/real implementations) for plugin data sources. Use when the user says "create a provider for [data source]", "add provider interface for [feature]", or "implement provider pattern for [plugin]".

Picks one workplan from .claude/workplans/Pending/ (skipping plans for issues tagged AIIGNORE or FUTUREWORK), moves it to .claude/workplans/Inprogress/, executes each step via the referenced skills, runs tests and logical-response check. On full success moves to .claude/Done/ and sets the GitHub issue as complete. On partial success (significant progress made, tests pass, but work remains), creates a continuation GitHub issue and progress report. Use when the user says "execute pending workplan", "work from pending", "pick and do a workplan", or "run the next pending plan".

Guides adding a new MCP server integration to AnimalAL-v1: create a nested kernel plugin wrapping the MCP server, add a system message in KernelConstants, register the plugin in StandardKernel, and add integration tests. Use when the user says "add MCP server", "integrate MCP server", "wire MCP tools", or asks how to add or connect a new MCP server to the project.

Discovers open GitHub issues via GitHub MCP (list_issues on user-github) or gh CLI, excludes issues with labels AIIGNORE or FUTUREWORK, prioritizes maint over feat, picks one, analyzes the repo and issue, writes a detailed implementation plan to .claude/workplans/Pending/, commits that plan on the current branch, then sets the issue to "not planned" (closed, state_reason not_planned). Prefer GitHub MCP over gh CLI. Use when the user says "pick an issue and plan", "pick issue and plan", "plan next issue", "choose issue and create plan", or "pick from GitHub issues and plan".

Automated code review for plugin implementations against AnimalAL project standards. Analyzes nested plugins for pattern compliance (NestedStockPlugin structure), IDisposable, IInternalCallTracker, ChatHistory parameter, logger usage, error handling, description attributes, thread-safe call tracking, lazy initialization, StandardKernel registration, and test coverage. Use when the user says /review-plugin, "review plugin", "review NestedXPlugin", or asks to audit or check plugin code against project standards.

Runs IntegrationTesterApp tests with context-aware tag filtering. Detects modified files via git status, maps plugin/kernel paths to test tags, invokes run-tests.ps1 accordingly, and highlights failures. Use when the user requests to run tests, invokes the smart test runner, or when verifying changes under src/Plugins or src/AnimalKernel per CLAUDE.md workflow.

Keeps CLAUDE.md in sync with available skills, agents, and MCP servers. Discovers skills from .claude/skills/, agents from .claude/agents/, and MCP servers via `claude mcp list`; rebuilds the Skills & Agents and MCP Servers sections. Use when adding or removing skills, agents, or MCP servers, when the user says "sync dev guide", "update CLAUDE.md", "keep rules in sync with skills", or "refresh dev guide".

Ensures Real and Fake provider implementations stay in sync with their interfaces. Scans provider interfaces, detects missing or mismatched methods in Fake/Real implementations, validates fake data consistency, suggests realistic fake data from Real provider patterns, and can auto-generate stub implementations. Use when the user says /sync-providers, "sync providers", "check provider sync", "providers out of sync", or asks to verify or fix Real/Fake provider implementations.

Picks one workplan from .cursor/workplans/Pending/ (skipping plans for issues tagged AIIGNORE or FUTUREWORK), moves it to .cursor/workplans/Inprogress/, executes each step via the referenced skills, runs tests and logical-response check. On full success moves to .cursor/workplans/Done/ and sets the GitHub issue as complete. On partial success (significant progress made, tests pass, but work remains), creates a continuation GitHub issue and progress report. Use when the user says "execute pending workplan", "work from pending", "pick and do a workplan", or "run the next pending plan".

Discovers open GitHub issues via GitHub MCP (list_issues on user-github) or gh CLI, excludes issues with labels AIIGNORE or FUTUREWORK, prioritizes maint over feat, picks one, analyzes the repo and issue, writes a detailed implementation plan to .cursor/workplans/Pending/, commits that plan on the current branch, then sets the issue to "not planned" (closed, state_reason not_planned). Prefer GitHub MCP over gh CLI. Use when the user says "pick an issue and plan", "pick issue and plan", "plan next issue", "choose issue and create plan", or "pick from GitHub issues and plan".

Runs IntegrationTesterApp tests with context-aware tag filtering. Detects modified files via git status, maps plugin/kernel paths to test tags, invokes run-tests.ps1 accordingly, and highlights failures. Use when the user requests to run tests, invokes the smart test runner, or when verifying changes under src/Plugins or src/AnimalKernel per CLAUDE.md workflow.

Guides adding a new MCP server integration to AnimalAL-v1: create a nested kernel plugin wrapping the MCP server, add a system message in KernelConstants, register the plugin in StandardKernel, and add integration tests. Use when the user says "add MCP server", "integrate MCP server", "wire MCP tools", or asks how to add or connect a new MCP server to the project.

Keeps .cursor/rules/GeneralDevGuide.mdc in sync with available skills and MCP servers. Discovers skills from .cursor/skills/, agents from .cursor/agents/, and MCP servers from mcps/; rebuilds the Skills & Agents tables and the MCP Servers table. Use when adding or removing skills or MCP servers, when the user says "sync dev guide", "update GeneralDevGuide", "keep rules in sync with skills", or "refresh dev guide from skills and MCP".

Automated code review for plugin implementations against AnimalAL project standards. Analyzes nested plugins for pattern compliance (NestedStockPlugin structure), IDisposable, IInternalCallTracker, ChatHistory parameter, logger usage, error handling, description attributes, thread-safe call tracking, lazy initialization, StandardKernel registration, and test coverage. Use when the user says /review-plugin, "review plugin", "review NestedXPlugin", or asks to audit or check plugin code against project standards.

Plugin Scaffolding Generator - Creates complete plugin implementations following project patterns. Use when user says "add a plugin for [feature]", "create [Name]Plugin", or "scaffold a new plugin".

Analyzes IntegrationTesterApp test-result JSON (test-results_*.json, multi-model-results_*.json) and produces in-depth analysis of flow (prompt → tools called → response → assertions) and responses, plus actionable fix recommendations. Resolves "latest" or no path to the newest file in src/IntegrationTesterApp/test-results/. Use when the user says /analyze-test-json, "analyze test json", "analyze test results", "analyze latest test results", or @-mentions a test-results or multi-model-results JSON file and asks for analysis or recommendations.

Audits passed tests only: checks that each model response is logically consistent with the user's question (topic, entities, numbers, intent). Does not re-check assertions; adds a semantic-sanity layer so tests that pass on keywords/tools but give off-topic or contradictory answers are surfaced. Resolves JSON like analyze-test-json (test-results_*.json, multi-model-results_*.json in src/IntegrationTesterApp/test-results/). Use when the user says /check-test-logical-resp, "check logical responses", "check test responses make sense", "audit passed tests for logic", or @-mentions a test-result JSON and asks whether responses were logical.

Ensures Real and Fake provider implementations stay in sync with their interfaces. Scans provider interfaces, detects missing or mismatched methods in Fake/Real implementations, validates fake data consistency, suggests realistic fake data from Real provider patterns, and can auto-generate stub implementations. Use when the user says /sync-providers, "sync providers", "check provider sync", "providers out of sync", or asks to verify or fix Real/Fake provider implementations.

Generates the provider pattern (interface plus fake/real implementations) for plugin data sources. Use when the user says "create a provider for [data source]", "add provider interface for [feature]", or "implement provider pattern for [plugin]".