Skip to content

Add glossary_guide.md to standardize glossary.md generation#17

Merged
kikaineko merged 2 commits into
mainfrom
claude/glossary-simplify-descriptions-30cxb6
Jul 23, 2026
Merged

Add glossary_guide.md to standardize glossary.md generation#17
kikaineko merged 2 commits into
mainfrom
claude/glossary-simplify-descriptions-30cxb6

Conversation

@kikaineko

Copy link
Copy Markdown
Contributor

Summary

Adds a comprehensive generation guide for glossary.md to prevent implementation details from being included in the glossary. This addresses the problem where glossary entries become outdated whenever implementation changes occur.

Key Changes

  • New guide document (ofuda/guides/glossary_guide.md): Establishes clear principles for writing glossary entries

    • Introduces the "implementation replacement test": if a definition changes when implementation technology is swapped, it's implementation detail, not a definition
    • Provides a reference table of what to write vs. what not to write
    • Sets length guideline: 1-2 sentences per entry
    • Includes before/after examples showing how to rewrite implementation-focused entries into business-focused definitions
  • Updated skill workflows: All miko skills that update glossary.md now reference the new guide

    • miko.setup, miko.new-cap, miko.catchup, miko.quick-catchup, miko.propose
    • Each explicitly instructs to avoid implementation details (class names, method names, APIs, processing steps)
  • Updated documentation:

    • business_rules_driven_development.md: Added glossary_guide.md to the reference materials table
    • ofuda/examples/glossary.md: Added note that entries contain only definitions, not implementation details
    • CLAUDE.md: Added glossary_guide.md to required reading list
  • Version bump: v1.4.0 → v1.5.0

Implementation Details

The guide establishes a consistent judgment criterion across all miko workflows: glossary entries should capture what a term means in the business domain, not how it is implemented. This ensures glossary.md remains stable even as technical implementation evolves, reducing maintenance burden and AI follow-up errors.

https://claude.ai/code/session_012ZqeVeR6bCYCJ8Ze1BxVkb

claude added 2 commits July 23, 2026 01:14
用語集の項目に実装の詳細(クラス名・メソッド名・API・処理手順)が書かれてしまい、実装変更のたびに glossary への追従が必要になる問題に対処。glossary_guide.md を新設し、判定テスト・書くもの/書かないもの・長さの目安を明文化。setup / new-cap / catchup / quick-catchup / propose の glossary.md 更新手順から参照するようにした。

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ZqeVeR6bCYCJ8Ze1BxVkb
glossary_guide.md は判断がシンプル(実装技術を置き換えても定義文は変わらないか、の一問)なので独立ファイルにするほどではないと判断。判定テストと悪い例/良い例を .miko/examples/glossary.md に直接書き、各スキルの glossary.md 更新手順には一文だけ追記した。

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ZqeVeR6bCYCJ8Ze1BxVkb
@kikaineko
kikaineko merged commit b15ab52 into main Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants