Design recipes
What are design recipes?
Design recipes customize the Design Assistant so it follows your team’s terminology, standards, and typical design work. Each recipe is a versioned ZIP bundle of skills (expertise the assistant applies when a request matches) and commands (shortcuts that insert a prepared prompt). They are not the same as implementation recipes used by coding assistants.
The recipes apply in two layers that work together: baseline recipes, which administrators upload and attach to a project baseline so everyone on those projects gets the same skills and commands, and user-specific recipes, which any user can enable in User settings. Personal recipes add on top of the baseline; they do not replace it. When working with the workbench, commands from both sources show up as slash commands and as actions on selected model elements, and skills from both sources are considered when you send a message.
Related documentation
- Design recipe overview — understand design recipes as a part of the Design Assistant
- Manage design recipes — upload, enable, and maintain your personal recipes
- Design recipe reference — ZIP layout,
k5-design-recipe.yaml,SKILL.md, andCOMMAND.mdformats - Design Assistant — prerequisites, chat usage, and built-in example prompts
- Use the Design Assistant — day-to-day prompting patterns, including @ mentions
- Project baselines — associating profiles, recipes, and design recipes with projects
- OML profiles — modelling vocabulary referenced by baselines
- Implementation recipes — skills and commands for coding assistants in Git
- Install initial design recipes, profiles and baselines — loading default bundles after installation