rsc-security-audit
React Server Components (RSC) の利用方針とセキュリティ基準に基づき、データの安全性と疎結合性を監査します。
Discover Development skills, compare source repositories and read the instructions for each workflow.
React Server Components (RSC) の利用方針とセキュリティ基準に基づき、データの安全性と疎結合性を監査します。
Luau scripting for Roblox: variables, functions, tables, modules, events, coroutines. Use when writing or debugging Roblox Lua code.
Roblox animation: TweenService, AnimationController, keyframes, easing. Use when animating objects or characters.
Roblox UI/GUI development: ScreenGui, Frame, TextLabel, TextButton, UIListLayout, tweening UI. Use when creating or modifying user interfaces.
Roblox data persistence: DataStoreService, MemoryStoreService, saving player data. Use when saving or loading persistent data.
Roblox audio: Sound, SoundService, audio effects, 3D sound. Use when working with sounds and music.
Roblox Engine API reference: classes, properties, methods, events. Use when looking up how to use Roblox classes or their members.
Roblox physics and parts: BasePart, Model, constraints, welds, motors, collision. Use when working with 3D objects and physics.
Roblox characters and avatars: Humanoid, R6/R15, character customization. Use when working with player characters.
Update AGENTS.md in CloudRadar with a fully automated GitHub flow. Use when the user asks to change AGENTS.md, mentions the meta issue
This skill should be used when the user asks about Hotwire, Turbo Drive, Turbo Frames, Turbo Streams, Stimulus controllers, frontend interactivity, server-rendered HTML updates, websocket updates, progressive e...
This skill should be used when the user asks about Rails philosophy, DHH's principles, the Rails way, "convention over configuration", "majestic monolith", "omakase", "sharp knives", NO BUILD, integrated system...
This skill should be used when the user asks about Active Record models, database migrations, queries, associations (belongs_to, has_many, has_one, has_and_belongs_to_many), validations, callbacks, scopes, data...
This skill should be used when the user asks about testing Rails applications, Minitest, test-driven development (TDD), unit tests, integration tests, system tests, fixtures, factories, mocking, stubbing, test...
This skill should be used when the user asks about Rails routing, URL patterns, RESTful routes, route helpers, controller actions, strong parameters, before_action callbacks, rendering, redirecting, the params...
This skill should be used when the user asks about Rails performance optimization, slow queries, caching strategies, database indexing, N+1 query prevention, memory optimization, asset optimization, profiling,...
This skill should be used when the user asks about Action Cable, WebSockets, real-time features, channels, broadcasting, subscriptions, chat applications, live notifications, presence indicators, collaborative...
This skill should be used when the user asks about deploying Rails applications, Kamal deployment, Docker containers, production configuration, environment variables, secrets management, CI/CD pipelines, server...
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Convert PRDs to prd.json format for the SDK Bridge autonomous agent system. Use when you have an existing PRD and need to convert it to SDK Bridge's JSON format. Triggers on: convert this prd, turn this into sd...
Create a pull request after code changes are complete and reviewed. Use proactively after self-review passes and documentation is updated.
Self-review after code changes. Use proactively after completing any code modifications, before creating a pull request. Runs tests, checks code quality, and validates changes.
Update documentation after code changes. Use when API endpoints, database schema, backend/frontend structure, or block definitions have been modified.
Add test cases to the codebase. Use when writing new tests, improving test coverage, or when the user asks to add tests for specific functionality.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.