source-command-implement-batch
Implement a bounded batch of Lorcana cards with isolated ownership, focused tests, and shared-engine backpressure. Use when the user supplies a card list or asks to process missing implementations.
source-command-implement-card
Compatibility router for the migrated Lorcana implement-card source command. Use only when an older prompt explicitly invokes source-command-implement-card.
source-command-improve-parser
Compatibility entrypoint for the former improve-parser command. Use for Lorcana parser validation and card-generation gaps.
source-command-review-pr-comments
Compatibility router for the migrated review-pr-comments source command. Use only when an older prompt explicitly invokes source-command-review-pr-comments.
source-command-review-pull-request
Compatibility router for the migrated review-pull-request source command. Use only when an older prompt explicitly invokes source-command-review-pull-request.
source-command-triage-player-report
Compatibility router for the migrated Lorcana triage-player-report source command. Use only when an older prompt explicitly invokes source-command-triage-player-report.
replay-debugging
Download and inspect a single turn of a real Lorcana game from production using the `tcg-replay` CLI. Use whenever you need to understand what actually happened in a player-reported bug — gives you the cards involved (with file paths), the pre-turn match state, and a step-by-step trace of moves, engine logs, and JSON patches for that turn.
improve-card-generator
Diagnose and repair Lorcana card parser or generation gaps in packages/lorcana/lorcana-cards. Use when generation marks cards missingImplementation, parser validation fails, or generated card output is incorrect.
gundam-test-generation
Author and review Gundam TCG card-behavior tests with the canonical GundamTestEngine pattern. Use whenever creating or modifying a card test under packages/cards/src/cards, including tests scaffolded during card implementation.
gundam-tcg-rules
Official Gundam Card Game comprehensive rules, glossary, and implementation constraints for this repository. Use when answering Gundam rules questions or changing gameplay logic, turn flow, combat, shields, damage, deckbuilding, resources, card behavior, effect resolution, keywords, pairing/linking, simulator prompts, tests, AI behavior, or player-facing rules copy.
gundam-cards
Implement, debug, or review one Gundam Card Game card in packages/cards, including any focused engine or types support required by its printed behavior.
gundam-bot-bench
Run reproducible Gundam bot self-play, diagnose strategy or engine failures, and compare heuristic candidates with tools/bot-bench. Use for bot fuzzing, strategy changes, deadlocks, illegal moves, or win-rate evaluation.
doc-gardening
Audit Gundam AGENTS, skills, and living documentation against current code after package moves or architectural changes. Use for semantic drift that deterministic link checks cannot prove.
typeset
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
self-improve-bot
Train and verify Cyberpunk greedy-strategy weights with the ai-runner hill climber. Use when changing greedy automation, trainer behavior, bot heuristics, or evaluating a candidate weight set.
quieter
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
polish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
cyberpunk-tcg-rules
Official Cyberpunk TCG gameplay rules, glossary, and rule-resolution guidance for this repository. Use whenever work touches gameplay logic, turn flow, combat, Gig theft, Street Cred, deckbuilding, RAM limits, card behavior, AI behavior, balance, rules text, UI copy, tests, or design docs and the output must stay aligned with the published gameplay guide.
critique
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
swu-rules
Official Star Wars Unlimited comprehensive rules, glossary, keyword, and implementation guidance for this repository. Use whenever work touches SWU gameplay logic, card behavior, keywords, turn flow, combat, targeting, deckbuilding, parser/import work, rules text, UI copy, tests, or design docs and the output must stay aligned with the published Comprehensive Rules.
op-rules
One Piece Card Game comprehensive rules, glossary, and implementation constraints for this repository. Use when answering One Piece rules questions or changing One Piece gameplay logic, card behavior, turn flow, battle, DON!! handling, Life, triggers, counters, deck validation, simulator prompts, tests, AI behavior, or player-facing rules copy.
nx-workspace
Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.
nx-run-tasks
Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.
nx-plugins
Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.
nx-import
Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.
nx-generate
Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.
monitor-ci
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.
link-workspace-packages
Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org/*) like "cannot find module", "failed to resolve import", "TS2307", or "cannot resolve". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager''s workspace commands to fix actual linking.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
parser-improvement
Compatibility entrypoint for Lorcana parser and card-generation work. Routes missingImplementation and generator failures to improve-card-generator.
memory-bank
Manage Memory Bank development logs in .ai_memory/. Use when starting a new feature, updating progress on current work, adding implementation log entries, or checking log status. Triggers on: (1) Starting new features/tasks, (2) "update memory bank" or "log progress", (3) Adding dated entries to implementation logs, (4) Checking Memory Bank status. Always prepends entries with YYYY-MM-DD dates, newest first.
lorcana-test-generation
Generate focused Lorcana card-behavior tests with the current multiplayer harness, or a minimal engine repro when a card exposes a runtime gap. Use when creating, repairing, or reviewing Lorcana card and engine tests.
lorcana-rules
Explain and cite Disney Lorcana rules using indexed references, and produce implementation-ready behavior constraints for card development. Use when answering mechanic questions, resolving card interactions, or deriving test/implementation constraints from official rules.
example-data-processor
Process CSV data files by cleaning, transforming, and analyzing them. Use this when users need to work with CSV files, clean data, or perform basic data analysis tasks.
ontological-documentation
Create comprehensive ontological documentation for Grey Haven systems - extract domain concepts from TanStack Start and FastAPI codebases, model semantic relationships, generate visual representations of system architecture, and document business domains. Use when onboarding, documenting architecture, or analyzing legacy systems.
tanstack-patterns
Apply Grey Haven's TanStack ecosystem patterns - Router file-based routing, Query data fetching with staleTime, and Start server functions. Use when building React applications with TanStack Start. Triggers: 'TanStack', 'TanStack Start', 'TanStack Query', 'TanStack Router', 'React Query', 'file-based routing', 'server functions'.
project-structure
Organize Grey Haven projects following standard structures for TanStack Start (frontend) and FastAPI (backend). Use when creating new projects, organizing files, or refactoring project layout.
pr-template
Generate pull request descriptions following Grey Haven Studio standards with clear summary, motivation, implementation details, testing strategy, and comprehensive checklist. Use when creating or reviewing pull requests.
testing-strategy
Grey Haven's comprehensive testing strategy - Vitest unit/integration/e2e for TypeScript, pytest markers for Python, >80% coverage requirement, fixture patterns, and Doppler for test environments. Use when writing tests, setting up test infrastructure, running tests, debugging test failures, improving coverage, configuring CI/CD, or when user mentions 'test', 'testing', 'pytest', 'vitest', 'coverage', 'TDD', 'test-driven development', 'unit test', 'integration test', 'e2e', 'end-to-end', 'test fixtures', 'mocking', 'test setup', 'CI testing'.
react-tanstack-testing
Specialized testing for React applications using TanStack ecosystem (Query, Router, Table, Form) with Vite and Vitest. Use when testing React + TanStack apps, mocking server state, testing router, or validating query behavior. Triggers: 'TanStack testing', 'React Query testing', 'test TanStack', 'mock query', 'router test'.
suite-audit
Meta-level plugin suite auditor that uses subagents to analyze any plugin for usability improvements, missing agents, duplication, and workflow optimizations. Generates comprehensive reports with user-approved todo conversion. Triggers: 'audit suite', 'analyze plugin usability', 'find duplicate agents', 'suggest new agents', 'optimize plugin workflow', 'plugin gap analysis'.
smart-debugging
AI-powered intelligent debugging with stack trace analysis, error pattern recognition, and automated fix suggestions. Use when debugging complex errors, analyzing stack traces, or performing root cause analysis. Triggers: 'debug', 'error analysis', 'stack trace', 'root cause', 'troubleshooting'.
onboarding-coordination
Automate developer onboarding with personalized plans, Linear integration, knowledge base setup, and milestone tracking. Use when onboarding new developers, planning team expansion, or managing role transitions.
plugin-audit
Comprehensive Claude Code plugin auditing skill for validating structure, detecting deprecated patterns, and recommending best practices based on the latest changelog. Use when auditing plugins, checking for deprecations, validating plugin structure, preparing plugins for release, or ensuring compatibility with recent Claude Code versions. Triggers: 'audit plugin', 'check plugin health', 'validate skill', 'plugin deprecation', 'changelog compatibility', 'plugin best practices'.
test-generation
Comprehensive test suite generation with unit tests, integration tests, edge cases, and error handling. Use when generating tests for existing code, improving coverage, or creating systematic test suites. Triggers: 'generate tests', 'add tests', 'test coverage', 'write tests for', 'create test suite'.
incident-response
Handle production incidents with SRE best practices including detection, investigation, mitigation, recovery, and postmortems. Use when dealing with production outages, SEV1/SEV2 incidents, creating postmortems, or updating runbooks.
evaluation
Evaluate LLM outputs with multi-dimensional rubrics, handle non-determinism, and implement LLM-as-judge patterns. Essential for production LLM systems. Use when testing prompts, validating outputs, comparing models, or when user mentions 'evaluation', 'testing LLM', 'rubric', 'LLM-as-judge', 'output quality', 'prompt testing', or 'model comparison'.
code-quality-analysis
Multi-mode code quality analysis covering security reviews (OWASP Top 10), clarity refactoring (readability rules), synthesis analysis (cross-file issues), and DDD/DRY lenses (flags mechanical naming, primitive obsession, domain rules leaking into infrastructure, and premature abstractions via the three-occurrences-same-concept rule). Supports team-mode parallel analysis when invoked from quality-pipeline. Use when reviewing code for security vulnerabilities, improving code readability, conducting quality audits, pre-deployment checks, or when user mentions 'code quality', 'code review', 'security review', 'refactoring', 'code smell', 'OWASP', 'code clarity', 'primitive obsession', 'value object', 'ubiquitous language', 'DRY', 'premature abstraction', or 'quality audit'.
tdd-typescript
TypeScript/JavaScript Test-Driven Development with Vitest, strict red-green-refactor methodology, domain-first modeling (DDD) via branded types, principled DRY discipline, React component testing, and comprehensive coverage patterns. Use when implementing TypeScript features with TDD, writing Vitest tests, testing React components, developing with test-first approach, modeling domain concepts, refactoring duplication, or when user mentions 'TypeScript TDD', 'Vitest', 'React testing', 'JavaScript TDD', 'red-green-refactor', 'TypeScript unit tests', 'branded types', 'value object', 'ubiquitous language', 'DRY', or 'test-driven TypeScript'.
Page 825 of 1671 · 83513 results
