What it is
A template repository for building integrations with an AI coding agent. Start a project from the template, fill in a few settings, and the agent arrives already knowing the integration platform, the company's conventions and the limits it must not cross.
It exists because an agent that can deploy is only useful if it provably cannot deploy to the wrong place.
What it does
- Bundles the platform's own agent skill, kept pristine and refreshed by a sync script, next to a separate skill of house rules: topology, known pitfalls and proven component templates.
- Refuses any deploy, undeploy or test execution whose target is not on the allowlist of test environments, even when the target is smuggled in as an inline override.
- Scans every commit for tokens, private keys and populated passwords in component files, and refuses to commit them.
- Gives each developer their own sandbox folder and credentials, so agents cannot trample each other's work.
How it works
- A developer creates a repository from the template and runs a one-time setup that checks the tools and installs the hooks.
- They describe the integration to the agent in plain language.
- The agent loads both skills, verifies its environment, and builds in the developer's sandbox.
- Before every command the agent runs, a hook inspects it; a deploy outside the allowed environments is stopped with a message the agent can read and act on.
- Promotion to production stays a human step in the platform's own interface.
Design choices
- Upstream skill untouched, company rules alongside: syncing the vendor's updates never conflicts with local knowledge.
- Guardrails as hooks, not instructions, so they hold even when the model is confident it is right.
- A smoke test after every change to hooks or skills, so the safety net is itself tested.
- Lessons learned go back into the template through pull requests, so every future project benefits.