Rules and skills
Give Uno the context your team uses every day.
Read the visual explanation
A repository rule supplies ongoing guidance. A skill describes a repeatable process such as reproducing, fixing, and checking a bug.
Repository rules
Use repository rules for instructions that should apply whenever Uno works on that codebase: conventions, test commands, architectural boundaries, and delivery expectations.
Keep rules concise and current. A useful rule explains the constraint and points to the source of truth.
Use the shared billing service for credit calculations.
Add regression coverage beside the affected module.
Run the package's typecheck and focused tests before opening a PR.Skills
Skills describe a repeatable workflow the agent can use for a task. Use them for a specific process, such as investigating an incident or preparing a release.
Configure the skills available to your workspace in Uno's settings. Preview a skill before installing it and make sure its instructions match your team's process.
Skills in your repositories
Uno also uses skills committed to your connected repositories. Put each skill in its own folder with a SKILL.md file under one of these directories:
.agents/skills/.claude/skills/.cursor/skills/skills/
A SKILL.md starts with frontmatter that names and describes the skill, followed by its instructions:
---
name: release-notes
description: Draft release notes from merged pull requests.
---
1. Read the pull requests merged since the last tag.
2. Group changes by customer impact.Agents read these skills from the branch they are working on, so a change to a skill applies as soon as it is on that branch. Settings → Skills lists the skills found on each repository's default branch, with any that could not be loaded. Workspace admins can turn off a single skill or every skill from a repository.
Tools
Use workspace MCP servers to let Uno call tools outside the repository. Start with the tools a real task needs and verify the connection before depending on it.
Set up the workflow
Use Create and maintain repository rules for the rule editor and revisions, and Install and manage skills for catalog packages, repository discovery, and availability controls. A rule or skill being read is not proof that the work complied; verify the result and checks.