design-note

What problem does it solve?

Capture and preserve design discussions and decision rationale from conversations so that future readers can understand the context, alternatives, and final judgments without relying on memory. It eliminates scattered notes and ad-hoc messaging by consolidating the outcome into a single, discoverable Markdown file in the ideas repository.

Core Features & Use Cases

• Repository-aware saving: Verifies the user's ghq root and the presence of the github.com/RyoMa99/ideas repository before proceeding.
• Japanese filename selection: Chooses a concise Japanese filename that reflects the discussion topic and asks the user to confirm when a file would duplicate an existing note.
• Reproducible summary template: Produces a Markdown summary that includes context, comparisons, code examples, and a clear decision flow so later readers can reproduce the rationale.
• Use case: After an architecture call about multi-tenant authentication, generate a design note that records options considered, trade-offs, and the final chosen approach.

Quick Start

Create a design note summarizing our discussion about the authentication flow and save it to ideas/design using a concise Japanese filename.