adapt
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.
animate
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
arrange
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
audit
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
bolder
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
clarify
Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.
colorize
Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.
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.
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.
delight
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.
distill
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
extract
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context.
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
implement-card
Step-by-step playbook for implementing any Cyberpunk TCG card (Legend, Unit, Program, Gear) in the engine. Covers loading rules context, understanding the card definition, verifying engine support, writing tests, running them, and opening a PR. Always loaded when implementing or testing any card. Self-updates after each PR via the retrospective step.
normalize
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
onboard
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.
optimize
Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.
overdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.
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.
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.
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.
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.
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.
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.
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.
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-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-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.
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.
lorcana-cards
Single owner for everything related to a specific Disney Lorcana card in `packages/lorcana/lorcana-cards` \u2014 authoring, debugging, triaging, generating, and any bounded engine or types extension required to make the printed text work. Use whenever the unit of work is \"this card\".
lorcana-find-card
Locate Lorcana cards in `packages/lorcana/lorcana-cards` and return deterministic, ranked similar-card references for implementation work. Use when a user asks to find a card by name/slug/set-number, needs definition/test file paths, or needs similar implementation examples.
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.
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.
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.
parser-improvement
Compatibility entrypoint for Lorcana parser and card-generation work. Routes missingImplementation and generator failures to improve-card-generator.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
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.
skill-creator
Guide for creating effective skills. This skill should be used 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.
source-command-fix-ci
Compatibility router for the migrated fix-ci source command. Use only when an older prompt explicitly invokes source-command-fix-ci.
source-command-fix-typescript
Diagnose and fix TypeScript errors within a specified Lorcana package using that package's current scripts and ownership boundary.
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-regenerate-cards
Regenerate Lorcana card sources with the current package scripts after parser, source-data, or generator changes.
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.
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.
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.
Page 1 of 2 · 57 results