Create portable, user-owned Markdown knowledge. The skill supplies the process; the person's brain is a separate output, never written into this installed skill.
Choose the activity
| Request | Read next | Result |
|---|---|---|
| Create, interview, or resume setup | Interview | Personalized draft, then saved brain |
| Remember a correction, evolve, or review learning | Updates | Scoped changes under the chosen policy |
| Use an existing brain in a feature | Read that brain's README and relevant files | Apply personal methods alongside company context |
For output structure, read Brain format. Consult Sources for attribution or framework explanations; the interview works offline.
Start from what is known
Use the brain location supplied by the user or established in this session. Otherwise inspect the current workspace's README and likely personal-brain folders narrowly. Do not search unrelated personal directories. Read an existing brain before changing it. Preserve prior answers and resume at unanswered questions.
For a new brain without a specified location, use my-designer-brain/ under the current workspace and state the location. Explain that a separate personal repo can hold the same files later. Do not initialize Git, change global instructions, install integrations, or publish anything unless requested.
Interview behavior
Order: critique methods → working with AI → optional references and taste → lessons and evolution. Ask two unanswered questions per round, then wait. All choice questions accept a written answer. Ranking accepts an ordered text response; do not convert it to single selection. Explain examples without treating them as the person's beliefs.
Use a host's question UI only if it preserves the question's answer type, write-in, and skip behavior. Otherwise ask in chat. Do not require a screenshot, company project, named framework, Mobbin access, or a particular app.
Skip already answered questions. Honor explicit requests to skip, shorten, or use proposed defaults; label defaults unconfirmed and leave unprovided rankings unset. Show a concise draft for correction before treating it as confirmed. Explicit instructions to save a draft authorize a draft save. Save partial progress when requested, with unanswered items visible.
Scope and persistence
Personal methods and taste do not silently override company requirements. Feature-specific decisions remain local. Do not copy restricted company material into the personal brain.
During use, follow the existing evolution policy. Until selected, suggest durable updates rather than silently writing them. A temporary exception never replaces a standing preference. Ambiguous frustration does not establish a new rule.
Write files when authorized and supported. Without file access, return downloadable files if possible, otherwise labeled Markdown for the user to save. Never claim an unsaved change persisted. A skill is not a background watcher: updates require active instructions and access to the brain. Verify written files and report exact paths and changes.