Buddy is the app-wide assistant you meet everywhere in the admin app. It knows your business, reads your current project configuration, and can change that configuration on your behalf when you ask it to.Documentation Index
Fetch the complete documentation index at: https://docs.frontic.com/llms.txt
Use this file to discover all available pages before exploring further.
What Buddy can do
Buddy handles the backend side of your project. You talk to it the way you’d talk to a teammate who already knows your setup.Set up integrations
Connect Shopify, commercetools, a PIM, a CMS, or any REST source. Buddy
walks the setup, fetches a sample, and gets data flowing.
Shape your data
Define Data Storages and the schemas that make your data semantically
meaningful — products, articles, categories, whatever your experience
needs.
Wire Data Syncs
Map incoming feed records into your Data Storages using the Value
Composer. Buddy explains why a transformation looks the way it does and
suggests alternatives.
Build the API
Create Detail Blocks, Search Listings, and Page URLs that expose exactly the
data your experience needs.
Edit Context Base
Read and update Skills, Rules, and Commands in the
Context Base — shaping how Studio and editor
agents work on your project.
Answer questions
“Why is this record missing a title?”, “What does this composer
expression return?”, “Which listings depend on this storage?” — Buddy
can inspect your project to answer.
Buddy works on your backend configuration — not on code. For writing and editing code, open a Studio workspace or use your editor where the right tools for building are available.
You stay in control
Buddy aligns with you on every change before acting. Your project role and permissions are delegated to Buddy, so it can work on your behalf — but with guardrails:- Creating new resources (blocks, listings, storages) and read-only operations (inspecting, querying, previewing) are auto-allowed
- Changing existing configuration requires your approval before Buddy proceeds
- Publishing a release is always your call — Buddy can help prepare a release, but has no access to Release Control
How Buddy knows your business
Buddy has its own setup routine — similar to Studio’s/init-context, it runs a short interview to understand your business, your products, and your goals. From that conversation, Buddy derives:
- a system prompt that shapes its general behavior — who it’s working for and on what
- a project context that covers the basics Buddy needs on every session without having to rediscover them
The Context Base (Skills, Rules, Commands) is designed for the build track — Studio and your editor. Buddy can read and edit context documents, but they aren’t its primary source of knowledge since they’re written for a different purpose.