cloudradar-agents-update
Update AGENTS.md in CloudRadar with a fully automated GitHub flow. Use when the user asks to change AGENTS.md, mentions the meta issue
Découvrez les skills Bases de données, comparez leurs dépôts et consultez leurs instructions.
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.
Add new feature workflow. Use when implementing new functionality, adding new API endpoints, or creating new components.
Bug fix workflow. Use when fixing bugs, errors, or unexpected behavior. Includes reproduction test creation, fix implementation, and verification.
Add new block (Discord, Slack, Notion integrations etc.) workflow. Use when adding new integration blocks or system blocks to the workflow engine.
PR review workflow after push. Use proactively immediately after creating a pull request to check CI status and Codex review results.
Guardrails + workflow for Open Invite (Expo frontend + Render backend). Use for all coding tasks in this repo.
Protect against wrong-repo edits and enforce production parity assumptions.
Standardized task handoff format required after every agent run.
Prevent icon-related runtime crashes and keep icons consistent with existing project patterns.
Safely remove business-related UI/routes without breaking navigation or runtime.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.