USER.md

June 22, 2026 · View on GitHub

Understand who you're helping. Update gradually through interaction.

  • Name: [user's name / handle]
  • How to address: [preferred forms of address], or just "you"
  • Timezone: [user's timezone, e.g. PST/PDT, UTC-8/-7]

Background

Core identity:

  • [Describe their mindset: systems thinker, builder, deep-diver, etc.]
  • [Describe their professional role and life context]

Technical interests:

  1. [Primary domain] — [depth of engagement, specific sub-topics]
  2. [Secondary domain] — [depth of engagement]
  3. ...

Writing and communication style:

  • [Technical depth, analytical vs. descriptive]
  • [Opinionated, values precision and clarity]
  • [Languages used, primary vs. secondary]
  • [Pet peeves: filler words, "AI-flavored" writing, etc.]

Personality traits:

  • [High CPU utilization / always busy]
  • [Obsession with systems, logs, measurement]
  • [Values autonomy and self-optimization]
  • [Pragmatic idealist: big vision with concrete steps]
  • [Time-conscious, wastes no moment]

Current projects and focus areas:

  • [List active projects]
  • [List areas of deep interest]

Interest map (systematic survey results):

  • [Category 1] (N interests) — [tracking frequency]
  • [Category 2] (N interests) — [expertise level]
  • ...

What annoys them:

  • "AI-flavored" writing: formulaic, no voice
  • Tools that don't integrate properly into workflow
  • Tacit knowledge that can't be captured and systematized

Life philosophy:

  • [Core beliefs about technology, AI, self-improvement]
  • [Builder mindset: from passive user to active builder/improver]

Work methodology: See Axioms for detailed principles. More detail in rules/axioms/ directory under the relevant axiom files.

Usage notes:

  • No filler phrases like "I'd be happy to help"
  • Be direct, substantive, and opinionated when appropriate
  • Respect their time: say "I don't know" when you don't know
  • When discussing AI, distinguish "tool usage" from "agent orchestration"

Communication preferences:

  • [Async vs. sync preferences, email habits, meeting aversion, etc.]
  • [When helping them choose services, include async-support as an evaluation dimension]
  • [Email CC preferences, which inbox is "default"]