Hey all, I’m experimenting with an idea called ReActions which are executable recipes for coding agents. The basic idea:

Coding agents can build UI/features, but they often invent a different implementation every time. One model may add accessibility, another may skip it. One may verify in the browser, another may just say it is done.

A ReAction is a Markdown file that gives the agent a reusable recipe for implementing something consistently.A ReAction includes things like:

Each ReAction can define:

\- required capabilities  
Example: inspect files, edit files, run commands, open browser, click UI

\- pause conditions  
Example: ask the user if the placement is ambiguous or required info is missing

\- safety rules  
Example: destructive actions must require confirmation

\- accessibility requirements  
Example: icon-only buttons must have accessible labels

\- browser verification  
Example: open the app, click the button, verify the state changes

\- final reporting  
Example: changed files, verification status, what passed/failed

So instead of saying: “Add a delete button” you can say: “Use /ReAction-verified-destructive-confirm-button-red” and the agent has a recipe for:

\- detecting the project

\- finding the right place to edit

\- adding a destructive button

\- requiring confirmation

\- checking the cancel path

\- checking the confirm path

\- running static checks

\- verifying in the browser

\- reporting what changed

I started with a small **Frontend Button** ReActions Pack because buttons are simple enough to demo but still easy for agents to mess up. Just add **Vercel**

Current ReActions include:

\- async CTA button

\- secondary button

\- destructive confirm button

\- copy button

\- icon button

\- toggle button

\- floating action button

\- split button menu

I also added two early demo videos:

\- Demo 1: destructive confirm button

\- Demo 2: switching from destructive button back to green submit / async CTA

Would love honest feedback:

\- Is “executable recipes for coding agents” clear?

\- Would you use something like this with Cursor/Claude/Codex/Gemini/local agents?

\- What ReActions would be useful beyond buttons?

\- Does this feel like a real abstraction or just fancy prompting?

\- What would make the repo easier to understand?

Would you use this to speed up Vibe coding? I’m experimenting with “ReActions” — executable recipes for coding agents. Would love feedback