Ken Yasue
80e195b3dc
- Add persistent docs: PRD, functional design, architecture, repository structure, development guidelines, milestones - Add brainstorming notes (docs/ideas/) - Configure tooling: package.json, tsconfig, eslint, prettier, vitest - Add opencode configuration (commands, skills, agents) - Add .gitignore for node_modules, .env, data/, backups/, build outputs
1.7 KiB
| name | description |
|---|---|
| glossary-creation | Detailed guide and template for creating a glossary. Use only when creating a glossary. |
Glossary Creation Skill
This skill is a detailed guide for systematically defining project-specific terms and technical terms.
Prerequisites
Before starting to create a glossary, confirm the following:
Recommended Documents
- docs/product-requirements.md (PRD)
- docs/functional-design.md (Functional Design Document)
- docs/architecture.md (Architecture Design Document)
- docs/repository-structure.md (Repository Structure)
- docs/development-guidelines.md (Development Guidelines)
The glossary defines the terms used across all documents in a unified way. Extract terms from each document and organize them systematically.
Priority of Existing Documents
Important: If an existing glossary is present at docs/glossary.md,
follow the priority order below:
-
Existing glossary (
docs/glossary.md) - Highest priority- Contains project-specific term definitions
- Takes precedence over this skill's guide
-
This skill's guide - Reference material
- Generic templates and examples
- Use when no existing glossary exists, or as a supplement
When creating new: Refer to this skill's template and guide When updating: Update while maintaining the structure and content of the existing glossary
Output Destination
Save the created glossary to the following location:
docs/glossary.md
Template Reference
When creating a glossary, use the following template: ./template.md
Detailed Guide
For a more detailed creation guide, refer to the following file: ./guide.md