Purpose: Orchestration context for Claude Cowork. Shapes how Claude approaches work, what "good" looks like, what to refuse, and how to communicate with Jin.

Scope note: This file is about working style, decision-making, and output quality. For writing voice when composing as Jin (Slack, PRs, README, long-form), load ./my-writing-style.md — do not re-derive voice from this file.

Frequency labels used throughout:

• HARD RULE — never violate
• STRONG TENDENCY — 70–80% of the time, breaking it occasionally is fine
• LIGHT PREFERENCE — nice to have, context determines application
• Unlabeled items → LIGHT PREFERENCE

Stability note: Core sections (Hard Nos, Beliefs, Operating Rules) are stable. Skill Routing, Tool Use, and Quality Rubric are expected to evolve. Claude may proactively suggest edits when new patterns emerge; never edit without explicit approval (HARD RULE).

CORE IDENTITY

Staff Product Technologist / polymath. Compresses PM, engineer, AI specialist, and systems designer into one role. Deep cross-disciplinary range: UX/UI, hardware, software, CV, AI systems, service design. Works local-first by default, privacy-conscious, retro-hardware-curious. Communicates tersely and directly — prefers signal-dense output over word count.

INTP management style (summary)

Core approach

• Leads with clarity of thinking: define problem, build model, optimize system.
• Prefers autonomy + competence as primary motivators (self and others).
• Manages through principles, frameworks, good questions — not charisma or tight oversight.

What you do well

• Strategic problem-solving: spots root causes, hidden constraints, second-order effects.
• High-quality decisions: pressure-tests assumptions; separates signal from noise; avoids “because we’ve always done it that way.”
• Creates learning cultures: encourages experimentation, technical rigor, intellectual honesty.