Use Buron in your AI editor
Buron ships skills in the open agent-skills format, so Claude Code, Cursor, Codex, Copilot, and dozens of other agents can pull context, snapshot work, and take Buron actions.
Buron's editor skills use the open Agent Skills standard: each skill is a SKILL.md file your agent discovers and invokes on its own. They work in any agent that supports the standard, which today means Claude Code, Cursor, Codex, GitHub Copilot, and 70+ others.
You don't have to invoke the CLI yourself. Your editor's agent does, on your behalf.
Install the skills
buron setup installs them as part of connecting your editors. You can also install them directly with the ecosystem's installer:
npx skills add buron-ai/skillsSkills land where your agent reads them: .claude/skills/ for Claude Code, .agents/skills/ for Cursor, Codex, Copilot, and most others. The installer knows each agent's convention, symlinks a single canonical copy, and npx skills update pulls new versions later.
Claude Code users can alternatively install the Buron plugin, which bundles the skills and the MCP server in one step: see Connect Buron to Claude Code.
Snapshot a code change with /launch
/launch is a good first skill to try. Type it in your editor while you're working on a change. The agent captures everything around that change, like the git diff, the PR description and review comments, and screenshots you've shared in the conversation. It saves all of this as a structured snapshot in Buron.
The result is that the next person who asks Buron about that change has the full story without you having to write it up. It's especially handy on features that span multiple PRs or that touch parts of the product your marketing team will need to talk about.
Set up Google Ads conversion tracking with /setup-google-ads-tracking
If you're wiring up conversion tracking in code, like on a new pricing page or signup flow, /setup-google-ads-tracking walks the agent through it. You describe the event you're trying to track, and the skill produces the tracking spec, the code change, and a doc that goes into Buron.
To learn more about this skill, check out Set up your conversion tracking.
Automate launch filing with /automate-launch
If you keep forgetting to run /launch, /automate-launch sets up a recurring editor task or a CI workflow that files sources for you. See Automate launch filing.
Keep your skills up to date
npx skills updateIt's a good idea to run this after major Buron releases, or whenever a teammate mentions a new command.
Next steps
To keep Buron in sync with what your codebase ships, check out Run Buron from CI.
Was this page helpful?