Browse the documentation
Agent skills
Five skills that carry the Bondry contracts into your coding agent. Each one opens with the rules the kernel enforces, then walks the work step by step. They work on their own, and they stop guessing entirely when the MCP server is connected.
The files are in English
The site speaks four languages; the skills do not. The Bondry development vocabulary is English, from the manifest fields to the route names, and a translated skill would teach names that do not exist in the code.
-
bondry-module
Build a Bondry module from an empty directory to a package that installs, with the manifest, the service provider, prefixed migrations, routes, permissions, admin screens and its own language files. Use when the user is writing, extending or fixing a module for the Bondry community platform.
-
bondry-theme
Build a Bondry theme from zero, with theme.json, the template hierarchy, customizer.json, child themes and functions.php, including the Tailwind build that ships compiled so the buyer never builds anything. Use when the user is writing, customising or fixing a theme for the Bondry community platform.
-
bondry-designer-widget
Extend the Bondry Designer page builder from a module or a theme, with widgets, surfaces, collections, dynamic tags, conditions and form actions, and the control schema each one accepts. Use when the user wants their Bondry content placeable in the page builder, or their screens replaceable by a published layout.
-
bondry-publish
Take a finished Bondry module or theme zip from registration to approval, through the MCP tools or the signed HTTP routes, including the review, the webhooks your server receives and what to do on each refusal. Use when the user is ready to register, announce, upload or publish a Bondry artifact, or is reacting to a review decision.
-
bondry-upgrade
Migrate a Bondry module or theme across core versions when the contract changes, covering the compatibility states, onUpdate migrations, tested_up_to, deprecations and the release that carries the change. Use when a Bondry module stopped working after a core update, went incompatible, or needs to support a new major core version.
Where to put them
Most agents read skills from a folder in your project or in your home directory. For Claude Code, one folder per skill, with the file named SKILL.md:
.claude/skills/bondry-module/SKILL.md
.claude/skills/bondry-theme/SKILL.md
.claude/skills/bondry-designer-widget/SKILL.md
.claude/skills/bondry-publish/SKILL.md
.claude/skills/bondry-upgrade/SKILL.mdWith the MCP server
The skills are the route; the MCP server is the source. Connected, your agent reads the current documentation, validates a package before you send it and publishes without leaving the editor: MCP server