Team rules tell AI agents what your design system expects: which components to skip, which to reach for first, and what must never appear in code. Agents receive the rules through the FISYCO MCP server before they write code. The agents report then shows how agents used the design system and what they could not find.
Before you start
- The design system in code is set up for the project: open the project and find Design system in code under From code. See Connect your design system.
- Developers have connected their agents to FISYCO. See Connect AI agents through MCP.
How agents receive the rules
Rules don't sit in a file the agent may or may not read. They shape the answers the MCP server gives:
- Search. When an agent looks for a component, search doesn't offer hidden components and ranks preferred ones first.
- Rules and guide. The
get_design_system_rulestool and the design system guide tell the agent the rules in full. - Code check.
check_ui_codelists rule violations first, with your team's message.
The pull request check applies the same rules, so an agent and a reviewer see the same note for the same code.
Where rules live
Rules have two levels.
Workspace rules apply in every project of the workspace. A project can add rules on top of them but can't relax them. Lists from both levels combine, and a switch that is on at either level stays on. The project card shows how many workspace rules also apply there.
Add a rule to a project
- Open the project, then Design system in code → Settings.
- Find the Rules for AI agents card.
- Turn on a switch, or type into a list with one entry per line.
- Click Save rules. The button becomes active once something has changed.
What a rule can say
A line in Forbidden in code looks like this:
!important | Use a component variant insteadThe text before the bar is matched literally, without regular expressions. Comment lines and import lines are skipped. The message after the bar is what the agent and the pull request reviewer see.
Read the agents report
Open the project, then Design system in code → AI agents. The report covers up to the last 30 days, and the dates of the period sit at the top.
Below the numbers, a line shows the design system health score out of 100 and how it changed since the period started. See Design system health. The Agents list shows each agent by name, with its calls and developers.
Missing components
Missing components lists searches that found nothing close in the design system, with how many times each was asked. It shows up to 20, most frequent first. A request that keeps coming back is a component worth adding to your ui-kit. When the list is empty, agents found everything they looked for.
When the report is empty
Until someone's agent calls FISYCO for the project, the tab says no agent has used this design system yet. Connect an agent opens the AI agents page in your account settings.
The monthly email
Workspace owners get the same report by email every month, for the previous month. It goes out only for projects whose agents called FISYCO that month.
FISYCO counts tool calls: which agent, which tool and what the outcome was. It doesn't store your source code, and code sent to check_ui_code isn't saved. The only search text it keeps is a short phrase from component searches that found nothing. Anything that looks like code is dropped, and the phrase is deleted after 30 days.