AGENT SKILLS
Your agent already knows how to build real UI with BuilderKit
Your agent can already build apps. The BuilderKit skill teaches it the components, blocks, and conventions of the system, so the UI it ships is consistent and looks like the rest of your app.
Recorded from a real session. Your agent's results may vary.
Why the output is right the first time
The skill brings the rules, the block metadata, and the reference templates into your project, so your agent builds from the system rather than from memory.
Frequently Asked Questions
Answers to the most common questions about the BuilderKit agent skill, which agents it works with, and what it does in your project.
Can BuilderKit be used in an existing Angular app?
Yes, while the suggested use case is to use one of the templates as a starting point for new projects, BuilderKit can also be integrated into existing Angular applications. The refined Angular Material styles can be applied to upgrade the look and feel of your current components, and individual blocks or templates can be adapted for use within your app’s structure. The agent skill also handles installing BuilderKit into an existing project for you.
What are agent skills?
A skill is a set of instructions and metadata that an AI coding agent reads before it starts building with BuilderKit. It covers the design guidelines, the documentation for every block, and the templates as reference, so the agent builds with the system instead of guessing at it.
Which agents does it work with?
Any agent that supports the skills format. Claude Code is the primary target, and other CLI agents that read skills work the same way. The skill is plain instructions and metadata, so nothing in it is tied to a specific tool.
Does any of my code leave my machine?
No. The skill clones BuilderKit into a .builderkit folder inside your project, and everything after that is a local read. Your agent talks to its own model as it always does. The skill adds no service of its own.
Do I need GitHub access to use the skill?
Yes. The skill reads BuilderKit straight from the private repository, so your agent has to run as the GitHub account that holds your license. Sign in with the GitHub CLI or set up your SSH key before the first task.
How do I get updates?
Run the install command again to pick up the latest skill. The .builderkit folder is disposable, much like node_modules. If it goes missing or falls behind, your agent clones it again.
Do I need to use an AI agent to use BuilderKit?
No, everything works exactly the same if you write the code yourself. Skills are a layer on top for people who build with an agent, not a requirement.
Will I get the same results as the demos?
No, agents are not deterministic. The model you use, its reasoning level, and even the same prompt run twice can produce different results.
What the skill does is ground your agent in BuilderKit’s rules, block documentation and reference templates, so the output lands in the system. It does not make the output identical.