Files

Ken Yasue ced279e2df feat: initial commit - opencode spec-driven development boilerplate

Converted from Claude Code boilerplate to opencode:
- CLAUDE.md -> AGENTS.md (opencode instructions)
- .claude/settings.json -> opencode.json (permissions schema)
- .claude/agents/ -> .opencode/agent/ (subagents with mode: subagent)
- .claude/commands/ -> .opencode/command/ (slash commands with )
- .claude/skills/ -> .opencode/skills/ (7 skills, removed allowed-tools)
- DevContainer updated to install opencode
- All .claude/ paths and Claude Code references updated

2026-06-24 22:32:45 +02:00

1.7 KiB

Raw Blame History

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:

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

1.7 KiB Raw Blame History