Audit UX accessibility with WCAG. TRIGGERS - Use when user needs help with accessibility-audit-ux related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Audit UX accessibility with WCAG. TRIGGERS - Use when user needs help with accessibility-audit-ux related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design accessibility testing strategies. TRIGGERS - Use when user needs help with accessibility-testing related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a formatted PDF compliance audit document with findings, risk ratings, remediation recommendations, and sign-off sections.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
QA + bugfix cycle until it passes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full pipeline: evaluation -> spec -> implementation -> review -> QA
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 re-measure and standing report of the canonical data model's live DB conformance. Use when asked 'where are we at' on DB drift or conformance, to update the drift numbers, when a drift-audit brief is re-issued, or on /drift-audit. NOT the per-table fix recipe (use matrx-frontend's db-canonicalize-table).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A live demo or admin page shipped with every feature whose results the user would otherwise not see. Use when building or extending a server-side capability, service, registry, or pipeline, or adding a backend endpoint or feature with no UI, whose output only shows in logs, the DB, or an agent run, or when the user says there's no way to see it or asks 'how do I test this'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The interview primitive for putting open decisions to an owner. Use on 'grill me', 'stress-test this', or 'what do you need from me before you build this', and whenever a plan, scope, spec, vision, or question ledger needs owner rulings. NOT for steps only a human can perform (use a guided session).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Working playbook preloaded into the browser-tester helper; the coach updates its Lessons after each round. Use only when acting as browser-tester or coaching it. NOT for general UI work (use matrx-frontend's browser-testing doc).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Doctrine for adding a capability INTO a live, existing feature to a world-class bar. Use on 'add X to Y', 'extend Y to support X', a new option, button, setting, endpoint, or tool for Y, or a sub-feature spec to implement. NOT for whole-feature audits or overhauls (use feature-deep-dive).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Doctrine for auditing an ENTIRE feature and building it to its ideal state. Use on 'deep dive on X', 'audit the X feature', 'figure out everything X does', 'take over X and finish it', 'bring X up to best practices', or when a whole feature needs overhauling, unifying, or finishing, not patching. NOT for one small addition (use build-sub-feature).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.