blade

Add React Native support (.native.tsx files) to Blade components that currently only have web implementations. Use when user says "add native support to {Component}", "migrate {Component} to native", or "/migrate-to-rn".

Resolve PR review comments by pushing code fixes or replying with explanations. Use when a PR has review comments that need to be auto-resolved.

Review blade PRs by fetching diff, checking CI status, and getting Storybook URL. Use when reviewing PRs, checking PR status, or getting preview links for razorpay/blade PRs.

Get agentic metrics for the `razorpay/blade` repo.

Perform a task end-to-end when intent is set to 'perform-task-end-to-end' by checking existence of GITHUB__RZP_SWE_AGENT_APP__APP_ID environment variable in the session.

Heal a Blade PR by fixing CI failures, missing changesets, and sanity issues. Use when a PR has failing CI or other sanity problems that need to be auto-fixed.

Create a pull request ready for review with conventional commit message and structured PR body targeting master branch

Guidelines for reviewing Blade PRs — sanity checks, code quality, API decisions, usecase validity, and UI review.

This rule helps in reviewing the component before shipping to make sure all important things are checked

Orchestrate parallel migration of Blade React components to Svelte 5. Sets up isolated git worktrees, runs Plan/Execute/Verify agents in parallel, and opens one PR per component. Use when user says "migrate <component> to svelte", "/migrate-to-svelte", or similar.

This rule helps in writing API decisions for new components of blade design system

Visually verify component changes in Storybook using the agent-browser CLI tool

Important guidelines for writing frontend UI code. Ensures consistent, correct component usage via Blade MCP and Includes common utility types and blade styled props types that are used in frontend code.

Update an existing Blade component (web only) using Figma designs and knowledgebase documentation

Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks

This rule helps in writing and running unit tests for components of blade design system