ai-setup-forge

Accessibility testing for web applications using Playwright (@playwright/test) with TypeScript and axe-core. Use when asked to write, run, or debug automated accessibility checks, keyboard navigation tests, focus management, ARIA/semantic validations, screen reader compatibility, or WCAG 2.1 Level AA compliance testing. Covers axe-core integration, POUR principles (perceivable, operable, understandable, robust), color contrast, form labels, landmarks, and accessible names.

To ensure the application is usable by people with disabilities, complying with WCAG standards and improving SEO/UX. Use when: During development of UI components; Before major releases.

Accessibility testing toolkit using Selenium WebDriver 4+ with Java 21+ and axe-core engine. Use when asked to validate WCAG 2.1/2.2 compliance, scan pages or components for a11y violations, test keyboard navigation, audit color contrast, check ARIA semantics, generate accessibility reports, filter axe rules, debug screen reader issues, or implement POUR principles (perceivable, operable, understandable, robust).

To allow incompatible interfaces to work together by wrapping an object in an adapter that translates its interface into one that a client expects. Use when: When integrating a third-party library whose interface doesn't match your application's internal requirements; When you want to standardize multiple different implementations of a service (e.g., different payment gateways); When you need to provide a stable interface while the underlying dependency is subject to change.

To implement a scalable permission system where users have roles, and roles have granular permissions. Use when: B2B SaaS applications (Admin, Editor, Viewer); Systems with complex access requirements.

Browser automation CLI for AI agents. Use for website interaction, form automation, screenshots, scraping, and web app verification. Prefer snapshot refs (@e1, @e2) for deterministic actions.

Visual UI annotation tool for AI agents. Drop the React toolbar into any app — humans click elements and leave feedback, agents receive structured CSS selectors, bounding boxes, and React component trees to find exact code. Supports MCP watch-loop, platform-specific hooks (Claude Code / Codex / Gemini CLI / OpenCode), webhook delivery, and autonomous self-driving critique with agent-browser.

To structure autonomous AI systems that can reason, plan, and execute tools to solve complex, multi-step problems using patterns like ReAct and Multi-Agent orchestration. Use when: When the task requires multiple distinct steps (e.g., "Find the price of BTC and email me the summary"); When the LLM needs to interact with the outside world (APIs, Databases, Web Search); When the workflow is non-linear and depends on intermediate results.

To systematically assess the performance, accuracy, and safety of LLM outputs using quantitative metrics and "LLM-as-a-Judge" patterns, ensuring production readiness. Use when: Before deploying any LLM application to production; When comparing different models (e.g., GPT-4o vs. Claude 3.5 Sonnet) or prompt versions; To detect regressions after updating prompts or RAG knowledge bases.

Automation skill for designing, verifying, and improving auth, cost, logging, and security compliance based on the internal AI tool mandatory implementation guide (P0/P1). Supports the full lifecycle of RBAC design, Gateway principles, Firestore policy, behavior logs, cost transparency, and the criteria verification system.

To automate server configuration. Use when: Tasks, handlers, and roles; When the specific requirement for Ansible Playbook Creation arises in the project.

To handle server state (fetching, caching, synchronizing, and updating) in React applications, replacing manual useEffect fetching logic. Use when: Fetching data from REST or GraphQL APIs; When you need caching, deduplication, background updates, or optimistic UI.

Design and document REST APIs following industry best practices: URL conventions, HTTP semantics, versioning, pagination, error formats, and OpenAPI/Swagger annotations. Use this skill whenever the user wants to design an API, define endpoints, create an API contract, add OpenAPI documentation, review API naming, or says things like "design the API for X", "what endpoints do I need for X", "how should I structure this REST API", "add Swagger docs", "define the API contract". Always use this skill for any REST API design or documentation task.

Guidance and best practices for api documentation best practices.

To design and implement a RESTful API endpoint that is consistent, scalable, and follows industry best practices for HTTP methods, status codes, and URL structure. Use when: When creating a new API resource or sub-resource; When refactoring existing endpoints to meet REST standards; When defining the contract between frontend and backend.

To manage changes in API contracts without breaking existing clients, ensuring backward compatibility. Use when: When introducing breaking changes (renaming fields, changing data types, removing endpoints); When supporting mobile apps that cannot be forced to update immediately.

To prepare, build, and submit React Native applications to the Apple App Store and Google Play Store using EAS Build (Expo Application Services). Use when: When the app is ready for beta testing (TestFlight/Internal Testing) or production release; When generating standalone binaries (.ipa, .aab).

Guidance and best practices for architectural decision records (adr).

Design and implement authentication and authorization systems. Use when setting up user login, JWT tokens, OAuth, session management, or role-based access control. Handles password security, token management, SSO integration.

Guidance and best practices for authentication strategy selection.

To ensure data is preserved and recoverable in case of corruption, accidental deletion, or catastrophic failure. Use when: Always. For every production database.

Autonomous ML experimentation framework by Andrej Karpathy. AI agent autonomously modifies train.py, runs 5-minute GPU experiments, evaluates with val_bpb, and commits only improvements via git ratcheting — so you wake up to 100+ experiments and a better model. Use when setting up autoresearch, writing program.md directives, interpreting results, configuring hardware, or running overnight autonomous ML experiments. Triggers on: autoresearch, autonomous ml experiments, overnight gpu experiments, karpathy autoresearch, train.py experiments, val_bpb, program.md research directives, ai runs experiments.

To build serverless functions. Use when: Triggers, layers, and concurrency; When the specific requirement for AWS Lambda Function Design arises in the project.

To retrieve secrets (database credentials, API keys) at runtime rather than storing them in environment variables or config files, enabling automatic rotation and better security. Use when: High-security environments; When key rotation is required by compliance.

To use serverless on Azure. Use when: Bindings and triggers; When the specific requirement for Azure Functions Basics arises in the project.

To offload time-consuming tasks (email sending, image processing, report generation) from the main HTTP request-response cycle using Redis-based queues. Use when: When an API request takes longer than a few seconds; To handle rate-limited 3rd party API calls; To retry failed operations automatically.

Guidance and best practices for bff pattern implementation (backend for frontend).

To release new software versions with zero downtime and instant rollback capability by maintaining two identical environments (Blue and Green). Use when: Mission-critical applications where downtime is unacceptable; Complex updates that might need immediate reversion.

AI-driven Game Development Studio using BMAD methodology. Routes game projects through Pre-production, Design, Architecture, Production, and Game Testing phases with 6 specialized agents. Supports Unity, Unreal Engine, Godot, and custom engines.

Creative Intelligence Suite for AI-driven ideation, design thinking, innovation strategy, problem-solving, and storytelling. 5 named specialist agents with distinct methodologies — no setup required, all workflows available immediately.

Orchestrates BMAD workflows for structured AI-driven development. Routes work across Analysis, Planning, Solutioning, and Implementation phases.

Guidance and best practices for branch protection rules.

To store data on the client-side efficiently, choosing the right mechanism (LocalStorage, SessionStorage, Cookies, IndexedDB). Use when: Cookies: Auth tokens (HTTPOnly), small preferences; LocalStorage: Non-sensitive persistent data (Dark mode preference); SessionStorage: Tab-specific data (Form inputs).

To improve response times and reduce database load by storing frequently accessed data in a fast, in-memory store. Use when: When fetching data that changes infrequently (e.g., product catalog, configuration); When computing expensive aggregations; When endpoints have high read-to-write ratios.

To render 2D (Canvas API) or 3D (Three.js/WebGL) graphics in the browser for games, visualizations, or creative effects. Use when: Canvas: Charts, simple games, image editing; Three.js: 3D models, immersive experiences, complex particle systems.

Guidance and best practices for changelog maintenance.

To test system resilience. Use when: Simulating failures; When the specific requirement for Chaos Engineering Basics arises in the project.

To automate the testing, building, and linting process whenever code is pushed, ensuring quality control and preventing regressions before merging. Use when: When setting up a new repository; When enforcing code quality standards (Lint, Prettier); When automating deployment (CD) or release management.

To decouple business logic from frameworks, databases, and external tools, making the application easier to test and maintain over time. Use when: When building complex enterprise applications; When you want to ensure the business logic can survive changes in the database (e.g., SQL to NoSQL) or framework (e.g., Express to NestJS); When you need high testability of core business rules.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", or "readable code". Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.