Learn how to create Knowledge entries in the Devin web UI so Devin automatically recalls design system rules and terminology in every session.
CONTEXT This is a training skill for UX designers. The designer does not code. All instructions reference the Devin webapp UI only.
IMPORTANT: Display the Training Progress section (at the bottom of this skill) as the FIRST thing when this skill is invoked, and again as the LAST thing before directing the designer to the next skill.
Explain the concept. Knowledge is Devin's long-term memory. When you create a Knowledge entry, Devin can recall it in any future session when the topic is relevant. Think of it like onboarding notes for a new team member — things they should always know.
Explain the three Devin primitives. Before diving in, give a quick overview of how Knowledge fits alongside the other two:
This lesson covers Knowledge. The next two cover Playbooks and Skills.
Walk through creating a Knowledge entry. Guide the designer step by step:
a. In the Devin webapp, click the gear icon or navigate to Settings & Library
b. Click the Knowledge tab
c. Click Add Knowledge in the top right
d. For the Trigger Description, enter: when working with colors, spacing, typography, or design tokens
e. For the Content, enter the following (read from docs/design-system.md and summarize the key token values):
Design System Token Rules for Comarch XL Web:
- Error color: #dc2626 (--color-error)
- Primary color: #1a56db (--color-primary)
- Modal padding: 32px (--modal-padding)
- Standard spacing scale: 4/8/16/24/32/48px
- Font family: Inter
- All error messages follow: [What happened]. [What to do next].
- Button labels must use action verbs, never "Submit"
f. Pin it to the repo — select the comarch-devin-demo repository so this Knowledge is always active when working in this codebase. g. Click Save.
Test it. Tell the designer to start a new session (or continue this one) and ask: "What color should I use for error states?" Devin should recall the Knowledge entry and answer #dc2626. If it doesn't, explain that Knowledge retrieval is based on trigger relevance — refining the trigger description can improve recall.
Tips for good Knowledge entries.
Mention Knowledge suggestions. Devin can also suggest Knowledge entries based on your interactions. If Devin learns something useful during a session, it will offer to save it as Knowledge. The designer should accept and edit these suggestions when they appear.
Wrap up. Tell the designer to start a new session and invoke: @skills:learn-playbooks
Estimated total training time: ~55 minutes
Phase 1 — Foundations:
Phase 2 — Design Workflows:
4. research-benchmarking (~7 min)
5. figma-verification (~7 min)
6. ux-writing-review (~6 min)
Phase 3 — Building Reusable Automation: 7. learn-knowledge (~5 min) — You are here 8. learn-playbooks (~7 min) 9. learn-skills (~8 min)