The Docs Agent watches for changes in Figma and proposes changes to your design system in zeroheight. This works by looking at changes to Figma like updates to components, the agent then identifies the change, reads your documentation and determines if anything needs to be changed so you can keep your docs up to date without manual work.
We want to make the Docs Agent useful to you and your team, that's why we're asking for beta testers so we can learn what works and what doesn't. It's a chance to shape the Docs Agent into a helpful and powerful tool that can help automate changes to your documentation.
What to expect
- You'll be given access to a new Docs Agent area of zeroheight to review proposals
- The Docs Agent won't make any changes just yet, it will only offer suggestions
- Figma is the only supported design tool for change events
- Not all events from Figma may result in a proposal (file comments do not result in proposals to update documentation)
- It may take up to 30 minutes from when a change is seen to when a proposal is presented
- You will not receive notifications when proposals are ready, they will show up in the Docs Agent area
Setting up the agent
- Connect to Figma via OAuth - this connection will be used to watch for changes in Figma.
- Make a change in Figma (update a component, change a token value, rename something).
- The agent will detect the change, generate a proposal, and show it in the Docs Agent area of zeroheight.
- Review the proposal - accept or reject it, nothing in your styleguide will change just yet but we'll use this as a way to improve the Docs Agent before release.
Providing feedback
Your feedback is important to us and will help shape the Docs Agent from the way it looks, to what suggestions it makes, and how it improves over time.
Read the proposal for the change you made and ask yourself
- Is the proposal accurate?
- Is it a change I would have made?
- What would I do differently?
A proposal approval/rejection is useful to see where the Docs Agent succeeds and fails. Providing additional feedback can help us understand why a change was good or where it missed the mark. We're open to feedback on the experience of interacting with the agent as well as the proposals generated.
FAQ
Are there any prerequisites for the Beta?
- You must be on an Enterprise plan
- Your organization must have "Allow use of AI features in styleguides" enabled
- You must have at least one styleguide setup that corresponds to one or more Figma files
If you're interested in joining the beta and meet the prerequisites, contact us today.
How long will the beta run?
The beta period will last for 4 weeks.
What changes are watched?
The Docs Agent will watch changes to Figma files that are included in styleguides, all styleguides in the organization will be monitored for changes and proposals suggested.
What data is used and how is it used?
Data from the styleguides in your organization and connected Figma files will be analyzed by an LLM, OpenAI is our AI provider and the sub-processor of this data. zeroheight will use feedback you've provided directly along with the transcripts from the agent and your final approval/rejection. We may ask to arrange a feedback session to elaborate further.
Will you use our data for training purposes?
Neither zeroheight nor OpenAI will use customer data for model training purposes.
What if the agent makes a change to my styleguide?
No changes are made to your styleguides during the beta, approving a proposal is to signal intent rather than change any documentation directly.