
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.
This rule helps in writing API decisions for new components of blade design system
This rule helps in writing and running unit tests for components of blade design system
Create a draft pull request with conventional commit message and structured PR body targeting master branch
Guidelines for migrating existing Blade components from React to Svelte
This rule helps in reviewing the component before shipping to make sure all important things are checked
Update an existing Blade component (web only) using Figma designs and knowledgebase documentation
Visually verify component changes in Storybook using the agent-browser CLI tool
Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks