Contact
A small public routing layer for project discussion, source context, writing, and focused collaboration.
Available for focused product, interface, and system work.Public project threads first; private routes are handled case by case.
A precise contact surface, not a decorative form.
Start with the route that best matches the conversation. The current public path is GitHub Issues, with context links nearby so messages stay grounded in real pages, code, and project history.
Issue formOpen a structured issueBest for public project feedback, collaboration ideas, and design discussion with context.GitHubInspect the repositoryUse the source history, docs, and issues when you need concrete project context.GovernanceRead collaboration guideSee how feedback, creative ideas, issue forms, Feishu notes, and phase records connect.Studio profileRead the profileStart here for principles, capabilities, timeline, and working agreements.EssaysReference the writingUseful when a conversation starts from an essay, note, or interface principle.PortfolioReference selected workUse project pages when the conversation is about systems, components, or portfolio work.
Best fit
Where a message is likely to become useful.
Product direction, interface systems, and code-backed UI work.Writing, knowledge architecture, and long-lived personal site structure.Component behavior, accessibility contracts, deployment trace, and public repo feedback.
Boundaries
What this first version refuses to fake.
No fake private form until a real inbox or backend exists.No urgent support promise; GitHub Issues is public and asynchronous.No generic sales funnel. A useful message should include context, goal, and constraints.