Working in a Workspace
Skills
Verified against Soffi ·
A skill is a playbook Soffi follows when you ask for it: a review checklist, your naming conventions, the steps your team takes before calling a screen done. Instead of pasting the same instructions into every request, you write them once and anyone on your team runs them with a command.
Running a skill
In the message box in Soffi's panel, type / and pick a skill from the list, or click Skills next to the message box. Either way the skill's command goes into your message, and you can add whatever else you want Soffi to know before sending, for example /design-system-review the settings page.
Every Organization starts with one skill from Soffi, /design-system-review. It checks whether UI code uses your Project's own tokens and components, and reports hard-coded values or hand-rolled components with the evidence for each.
Adding your own
Skills belong to your Organization, so a skill one person adds is available to everyone on the team. Editors, Admins and Owners manage them under Settings, in Skills.
A skill is a Markdown file. Write the playbook the way you'd brief a new teammate: what to look at, what good looks like, and what to report back. Then:
Add the file
Click Add skill and drop in a .md or .txt file, up to 200 KB. If the file starts
with YAML frontmatter carrying a name and a description, Soffi fills those in for you.
Name it
Give it a Name and a Command. The command is what people type after the
/, in lowercase letters, numbers and dashes, like component-naming.
Describe it
Add a short Description. It shows next to the skill in the list, so people can tell which one they want.
To update a skill's instructions later, use Replace file from its menu. Edit changes its name, command and description.
On the Soffi skills tab you can turn Soffi's own skills on or off for your team. They can't be edited.