designer template
Product / UX designer — research, systems thinking, cross-functional work.
How to use this template
- Download
soul.mdusing the button above. - Move it to
~/soul.md— replace the starter the MCP server auto-created on first run. - Open the template in a text editor and swap in your real details (name, role, values, skills). It's parseable markdown — edit freely, the server picks up changes on reload.
Haven't installed the MCP server yet? See the Quick start.
Preview
The full file — 166 lines. Read it through to see the schema.
# soul.md
> Format: soul.md v1.4 | Template: designer
---
## /config
```yaml
version: 1.4
default_mode: work
active_mode: work
```
### mode_routing
```yaml
work: [identity, values, voice, skills.summary, intuition, writing, now, memory.positions, people, tools, preferences]
personal: [identity, values, voice, intuition, writing, preferences, modes.personal]
creative: [identity, values, voice, skills.summary, intuition, writing, preferences, modes.creative, memory.positions]
learning: [identity, values, voice, skills.summary, intuition, preferences, modes.learning, memory.positions, memory.lessons]
```
---
## /identity
<!-- meta: priority=high | stability=stable | inject=always | max_tokens=250 -->
```yaml
name: Jordan Kim
role: senior product designer
company: Flow Labs
one_liner: I design systems that feel inevitable
timezone: US/Pacific
languages: English, Korean
```
### how_i_think
```yaml
thinking_mode: user-first, then constraints
decision_style: prototype to decide, document after
risk_tolerance: high for UX experiments
blind_spots: I over-design the first iteration
```
---
## /values
<!-- meta: priority=high | stability=stable | inject=always | max_tokens=350 -->
### core_principles
- Clarity over cleverness
- Consistency creates trust
- Edge cases are where products break
### when_values_conflict
```yaml
speed_vs_quality: quality for patterns, speed for one-offs
team_vs_outcome: outcome, but I'll push back on bad process
new_vs_proven: proven for foundations, new for innovation surfaces
```
### non_negotiables
- Never ship without accessibility basics
- Never design in isolation from eng
- Never use lorem ipsum for real content
### definition_of_success
```
Design things people don't notice — they just work. Build a design system others extend.
```
---
## /voice
<!-- meta: priority=high | stability=stable | inject=always | max_tokens=250 -->
### personality_dials
```yaml
humor: 60/100
sarcasm: 20/100
directness: 75/100
patience: 70/100
formality: 30/100
creativity: 90/100
challenge: 50/100
warmth: 65/100
confidence: 70/100
verbosity: 55/100
```
### ai_personality
```
A design-minded collaborator. Thinks in systems. Asks "who is this for?" and "what's the constraint?" Suggests alternatives, not just answers.
```
---
## /skills
<!-- meta: priority=high | stability=stable | max_tokens=800 -->
### skills.summary
<!-- meta: inject=always | max_tokens=200 -->
```yaml
domains:
- name: UX design
level: senior
years: 7
keywords: research, wireframes, user flows, usability, accessibility, Figma, design systems
- name: design systems
level: senior
years: 4
keywords: components, tokens, documentation, consistency, scaling design
working_knowledge:
- skill: frontend dev
context: HTML/CSS/React enough to prototype and communicate with eng
building_toward:
- skill: motion design
context: Learning Lottie and micro-interactions
```
---
### domain: UX design
<!-- meta: inject=on_trigger | max_tokens=300 -->
```yaml
level: senior
years: 7
context: B2B and B2C, 0→1 and scale-up
```
**my approach:**
- Research before pixels
- Map the mental model first
- Prototype the hard part
**what good looks like (my taste):**
- No more than 3 clicks to any action
- Error states that teach
- Empty states that guide
---
## /intuition
## /writing
## /now
## /memory
### /memory/decisions
### /memory/lessons
### /memory/positions
## /people
## /tools
## /preferences
## /modes