Audit workplace accessibility for compliance. TRIGGERS - Use when user needs help with accessibility-audit related tasks.
The English summary is being prepared. Showing the original description.
Test design, vulnerability assessment, and quality assurance (13K skills)
Audit workplace accessibility for compliance. TRIGGERS - Use when user needs help with accessibility-audit related tasks.
The English summary is being prepared. Showing the original description.
Audit UX accessibility with WCAG. TRIGGERS - Use when user needs help with accessibility-audit-ux related tasks.
The English summary is being prepared. Showing the original description.
Implement A/B tests with code and analytics. TRIGGERS - Use when user needs help with ab-test-implementation related tasks.
The English summary is being prepared. Showing the original description.
Plan accessibility testing. TRIGGERS - Use when user needs help with accessibility-testing-plan related tasks.
The English summary is being prepared. Showing the original description.
Build A/B testing frameworks for features. TRIGGERS - Use when user needs help with a-b-testing-framework related tasks.
The English summary is being prepared. Showing the original description.
Design A/B tests with hypotheses, variants, sample sizes, and analysis plans. TRIGGERS - Use when user wants to run A/B tests, split tests, or experiment with variations.
The English summary is being prepared. Showing the original description.
Analyze A/B test results with statistics. TRIGGERS - Use when user needs help with ab-test-analysis related tasks.
The English summary is being prepared. Showing the original description.
Generate a formatted PDF compliance audit document with findings, risk ratings, remediation recommendations, and sign-off sections.
The English summary is being prepared. Showing the original description.
Cooks and packages a shippable CARLA server from a UE 5.8 ue58-dev checkout via the CMake `package` targets (shipping/development/debug/test), scoping the cook with CARLA_MAPS_TO_COOK, and inspects an existing package for the failures a green build hides — stale pak/ucas mismatch, missing staged OpenDrive/TM road data, missing post-process profiles, and Town15's uncookable content. Use when the user asks to "package CARLA UE5", "cook a map", "build a shipping server", "make a distributable CARLA", or a package builds but renders black / has no maps.
The English summary is being prepared. Showing the original description.
Adds a new ROS 2 message type to CARLA's native ROS 2 interface — the hand-written POD struct under LibCarla/source/carla/ros2/types/msg, its Fast-CDR serialize/deserialize pair, the RIHS01 type hash computed in Docker, the CdrTopicInfo registration and the type-hash test. Use when the user asks to "add a ROS message type", "support sensor_msgs/X in CARLA", "add a carla_msgs type", "why is my type hash warning appearing", or needs a message CARLA does not publish yet. There is no IDL codegen — every step is manual.
The English summary is being prepared. Showing the original description.
Runs Scenic probabilistic scenarios against a running CARLA server with the `scenic FILE --simulate --2d` CLI — the carlaChallenge1-10 traffic scenarios shipped by ScenarioRunner (`model srunner.scenic.models.model`) and by Scenic itself (`model scenic.simulators.carla.model`) — bounding the run, sampling scenes headlessly first to tell a map problem from a syntax problem, and restoring the world afterwards. Use when the user asks to "run a Scenic scenario", "run carlaChallenge", "test a .scenic file", "scenic --simulate", or reports a Scenic scenario that rejects every sample or cannot find blueprints.
The English summary is being prepared. Showing the original description.
Runs a single ScenarioRunner Python scenario (or a whole group) against a running CARLA server — FollowLeadingVehicle, ControlLoss, DynamicObjectCrossing, SignalizedJunctionLeftTurn and the rest of srunner/examples — in sync or async mode, with result output, recording and manual/agent control of the ego. Lists what is runnable on the checked-out branch and on the loaded map. Use when the user asks to "run a scenario", "test FollowLeadingVehicle", "list scenarios", "run a CARLA traffic scenario", or reports a scenario that is "not supported".
The English summary is being prepared. Showing the original description.
Diagnoses and fixes CI failures and re-runs GitHub Actions jobs. Use when CI is failing, tests break in CI, lint errors block merging, a build fails, or jobs need re-running.
The English summary is being prepared. Showing the original description.
Full pipeline: evaluation -> spec -> implementation -> review -> QA
The English summary is being prepared. Showing the original description.
QA + bugfix cycle until it passes
The English summary is being prepared. Showing the original description.
Trial protocol for teaching AI Matrx an expert's knowledge until the platform breaks, fixing it. Use when asked to run an expertise trial, distil a person/creator/recent video into a Masterwork, or test the capture product. NOT for a known-missing feature (use build-sub-feature).
The English summary is being prepared. Showing the original description.
Splits one big Claude task or automation into a set of focused AI Matrx agents that work on the person's own AI Matrx tables, then builds and test-runs each one. Use when the person says "split my task into agents", "turn my automation into AI Matrx agents", "make agents for my work", or after their data has moved into AI Matrx.
The English summary is being prepared. Showing the original description.
Super-Admin-only lock-down pattern. Use before touching admin.admins, admin.admin_audit_log, is_super_admin() / requireSuperAdmin() / selectIsSuperAdmin, app/api/admin/admins/**, app/(admin)/administration/users/admins/**, the admin RPCs (admin_promote, admin_update, admin_revoke, admin_list, admin_list_audit, admin_find_user_by_email), createAdminClient(), a new RLS policy, SECURITY DEFINER RPC, or admin-gated route, or when locking a sensitive table to Super Admin.
The English summary is being prepared. Showing the original description.
Audit-and-fix method for one user setting area across every repo. Use when a setting seems ignored, duplicated or confusing, on 'audit the X settings' or 'why doesn't my X setting apply', or as a lane of the settings sweep. NOT for adding a new setting (use build-sub-feature).
The English summary is being prepared. Showing the original description.
Run the full on-track check on a conversation, project, or keyword the owner names: find the sessions, extract exactly what he typed, dispatch independent judges who go to the live product as him and report what was missed, plan the remedy, and return one page — what he will see, what is missing, the plan. Use when told to check whether work is on track, to audit a project that has drifted, on 'run the on-track check on X', or when a long campaign is about to freeze, hand off, or claim done.
The English summary is being prepared. Showing the original description.
Next.js route metadata, per-route favicons, OpenGraph, and Twitter cards. Use when adding a route or layout, adding a favicon or social share image, auditing missing metadata, naming tab titles, or touching createRouteMetadata, createDynamicRouteMetadata, generateFaviconMetadata, or titlePrefix.
The English summary is being prepared. Showing the original description.
Live real tests proving an AI Matrx agent really works. Use when you built or changed an agent, mandate, prompt, tool, model setting, binding or a workflow step that runs agents; when told to use safety-net; or to check an area works. NOT for one automated test (use forcing-function-tests).
The English summary is being prepared. Showing the original description.
The agent.review_queue register for work Arman must see or test in the UI. Use at the end of any task that produced something reviewable, at the start of a task to check prior feedback, and when reviewing, claiming, routing, or repairing a queue row.
The English summary is being prepared. Showing the original description.
The bar every automated test or guard must clear: green only when the real system works. Use when writing, fixing, or reviewing a test, mock, stub, fixture, snapshot, or self-test; adding a regression test for a bug; or about to call work done because tests pass.
The English summary is being prepared. Showing the original description.