design-note

Record design discussions and decisions as Markdown files in the ideas repository.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RyoMa99/dotfiles --skill design-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-note
Source: https://github.com/RyoMa99/dotfiles/tree/main/dot_claude/skills/design-note
Command: npx skills add https://github.com/RyoMa99/dotfiles --skill design-note

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about design-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save design decisions to a markdown decision log automatically?

To record design decisions in a markdown decision log, this Skill summarizes engineering or product design conversations into a structured Markdown file. It consolidates context, comparisons, and final judgments into a single, discoverable note within your repository.

What is the best way to document architectural proposals and design discussions?

The best way to document architectural proposals is to use a reproducible summary template that captures context, code examples, and a clear decision flow. This approach ensures later readers can reproduce the rationale without relying on scattered notes or memory.

Do I need ghq and a specific repository to record design notes?

Yes, you need ghq and the github.com/RyoMa99/ideas repository to record design notes. The Skill verifies your ghq root path and checks that this specific repository exists locally before proceeding with saving any files.

How does this tool handle duplicate filenames when saving markdown ideas?

When saving markdown ideas, the tool handles duplicate filenames by choosing a concise Japanese filename that reflects the discussion topic. If the generated filename would duplicate an existing note, it prompts the user to confirm before overwriting or saving.

Can I use my own repository instead of the default ideas repository for decision logs?

No, you cannot use your own repository for decision logs. The Skill specifically requires the github.com/RyoMa99/ideas repository to exist within your ghq root directory to successfully save the markdown design notes.