README

This is a guide to how I work and how we can do our best work together.

How I work

Communication
- I prefer public channels for shared context. I work async-first, keep subject lines clear, and share quick summaries.
Working hours
- I keep core hours open for sync and protect deep-work blocks most mornings. My calendar is the source of truth.
Feedback
- I value feedback that is kind, candid, and actionable.
- Public praise, private critique.
Assume good intent
- I assume good intent and work to understand the reasons behind decisions. I ask the same courtesy in return.
Working with ADHD
- I have ADHD. Clear, prioritised asks with scope and deadlines help me deliver. Written follow-ups make a difference.
- If I’m quiet, I’m in deep focus, and I’ll share an update once I surface.
- Rapid, actionable feedback helps me with momentum and avoids spirals of uncertainty.
- Gentle nudges are welcome—I’ll return the favour.

Collaborate closely
- I prefer close designer/engineer collaboration. Without it, quality risks staying in Figma.
- Pair early on flows, states (loading, empty, error), motion, and edge cases.
- Document intent and constraints (what must be true), not just pixels, while leaving room for pragmatic implementation.
Design intent
- Optimistic updates: design for perceived latency, smooth transitions, and recovery. Define what’s optimistic vs. confirmed.
- Shape component APIs: converge on clear props, controlled vs. uncontrolled patterns, tokens/variants, etc.

Code reviews
- I review code for: correctness, design, and style
- I ask clarifying questions before requesting rework and offer diff-ready suggestions where possible.
- I only block a PR if the code is not secure and correct—anything else is a nit-pick (but usually a valid one).
Pull requests
- I prefer small, focused PRs with a crisp summary, context, and screenshots or recordings for UI changes.
- I keep commits atomic and squash fixups before merge unless history matters.