roblox-code-review
Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when reviewing Roblox or Luau code for security, performance, monetization, data persistence, or architecture risks.
Load BEFORE any Roblox task, including direct build requests: sets initiative level, when to warn vs act, and which decisions need the user.
Use for growth diagnosis, discovery, retention, onboarding, experiments, LiveOps, and packaging.
Use when building Roblox menus, HUDs, shops, notifications, dialogs, or responsive cross-platform UI.
Use when handling Roblox keyboard, mouse, gamepad, touch, motion input, or cross-platform action binding.
Use for Roblox lighting, atmosphere, day/night, or post-processing effects.
Use when implementing Roblox multi-language support, translation tables, auto-translation, locale-specific content, or region detection.
Use for Luau language semantics, tables, control flow, string patterns, scope, closures, and cross-language translation errors.
Use for Luau annotations, generics, unions, narrowing, strictness, sealed tables, module type exports, or typed metatables.
Use when implementing Roblox GamePasses, Developer Products, subscriptions, private servers, Creator Rewards, or purchase policy checks.
Review UX design intent and available implementation evidence for accessibility barriers, inclusive interaction, WCAG or Section 508 requirements, keyboard and focus behavior, semantics, dynamic announcements, content, motion, zoom/reflow, and recovery. Use when a designer asks f
Find important users, contexts, constraints, dependencies, consequences, and conditions that a design discussion has not considered at all. Use when a designer asks "what am I missing?", wants edge perspectives beyond UI states, or needs a pre-review scan for overlooked experienc
Interrogate a UX idea, requirement, flow, feature, or design direction before execution. Use when a designer asks to be challenged, wants assumptions exposed, wants a red-team review of the premise, or needs hard questions that test whether the proposed work should exist at all.
Rewrite UX, product, research, handoff, ticket, or engineering-facing content so it reads like a capable human practitioner wrote it. Use when generated or existing content is bloated, robotic, unclear, over-structured, audience-blind, or sounds like AI while preserving meaning,
Review and improve product UX content including labels, instructions, errors, empty states, confirmations, terminology, and content timing. Use when a designer asks whether UI copy is clear, consistent, accessible, actionable, appropriately human, or aligned with the product's es
Review and compare UX designs, flows, prototypes, specifications, or implementations against user goals, evidence, interaction behavior, accessibility, design-system fit, content, and engineering intent. Use when a designer asks for critique, comparison, tough feedback, review be
Catalog captured:2026-11-21