Agents produce fast. I design the conditions to trust what they deliver.
Moving fast with AI is easy. Knowing whether what it produced is correct — that's a different question.
An agent can create a component in 3 seconds. It can also create a component that looks right, compiles, and silently bypasses the design system.
Trust doesn't come from the agent's capabilities. It comes from the system built around it. My work: designing that system.
Time gain
Quality gain
AI trust
Understand
Notes, qualitative feedback, quantitative inputs
Structure
Problem framing, workflows, decision criteria
Explore
Options, scenarios, alternatives, edge cases
Prototype
Interactive flows, states, first implementation paths
Evaluate
Critique, test scenarios, risks, blind spots
Decide
Trade-offs, product risks, solution choices
Document
Specs, memory, guidelines, design system notes
Communicate
Narrative, alignment, presentations, team conversations
Produce — without guardrails
Components, tokens, accessibility: no verification
Produce — with evidence
Verified components, respected tokens, declared compliance
This is one of the flows showing how my design system is implemented and synchronized between code and Figma, while addressing trust issues: context, evidence, checks and guardrails.
1.0.X
Patch or fix
1.X.0
Minor change
X.0.0
Breaking change
Design system edited
Tokens, component updates, new components, ...
Trigger
Protocol triggered manually or by automated routine
Orchestrate
An agent analyzes intent, evaluates risk level and routes to the right lane
Audit
An agent explores what exists in the DS
Explore
An agent challenges choices, edge cases and proposes iterations
Human arbitration
Iterate, reuse, extend or create?
Plan
Agent plan mode
Human validation
Validates the RFC or asks for another iteration
Implement
Implementation of the request in code
Verify
Certify Figma-code parity
Approve
Human validates the PR
Deliver & memorize
Sanity check and memory update
1.0.X
Patch or fix
Design system edited
"Rename the primary color to brand"
Trigger
Protocol triggered manually or by automated routine
Orchestrate
An agent analyzes intent, evaluates risk level and routes to the right lane
Implement
Implementation of the request in code
Verify
Certify Figma-code parity
Approve
Human validates the PR
Deliver & memorize
Sanity check and memory update
Every file has a precise role. Agents read, write and update these files at each step of the flow.
/design-system
# AGENTS.md ## Role Design system agent. You contribute to maintaining and evolving the DS in a governed way. ## Absolute rules - Read /system/governance.md before any action - Check /components/component-catalog.md before creating - Never hardcode token values - Declare every deviation in a compliance report ## Work cycle 1. Read the context files (/system) 2. Analyse the request and evaluate the risk 3. Run the flow for the matching lane 4. Produce deliverables in /reports 5. Update /system/memory.md
# AGENTS.md ## Role Design system agent. You contribute to maintaining and evolving the DS in a governed way. ## Absolute rules - Read /system/governance.md before any action - Check /components/component-catalog.md before creating - Never hardcode token values - Declare every deviation in a compliance report ## Work cycle 1. Read the context files (/system) 2. Analyse the request and evaluate the risk 3. Run the flow for the matching lane 4. Produce deliverables in /reports 5. Update /system/memory.md
What happened
A component implemented without min/max-width and min/max-height tokens, despite them being present in the Figma.
Why
The scan skill didn't target sizing constraint properties, so they were silently ignored.
How I fixed it
scan-figma.md updated with explicit rules to extract all sizing and constraint properties.
What happened
The agent created a Button component that already existed at v2.4 in the design system.
Why
The catalog listed component names but not variants; the agent didn't recognise the existing coverage.
How I fixed it
component-catalog.md enriched with variants, states and version for each component.
What happened
On a composite page, the agent recoded existing components from scratch instead of reusing DS ones.
Why
Figma layers had inconsistent names, so the agent couldn't connect them to existing code components.
How I fixed it
Layer naming convention + strict recognition rules added to AGENTS.md. Added a naming-check agent.
