General guide for creating definition documents. Use when you need to define WHAT something IS - concepts, entities, systems, or domains. Routes to specialized sub-skills for specific definition types (business, features, code, marketing, branding, tools).
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install eduardou24/ogt-docs-defineInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
Guide for creating definition documents that establish WHAT things ARE in your system.
Definitions are the foundation of shared understanding.
Before anyone can implement, market, or discuss something, there must be a clear, agreed-upon definition of what it IS.
┌─────────────────────────────────────────────────────────────────┐
│ THE DEFINITION PRINCIPLE │
├─────────────────────────────────────────────────────────────────┤
│ A definition answers: │
│ • WHAT is this thing? │
│ • WHY does it exist? │
│ • WHAT are its boundaries? (what it is NOT) │
│ • HOW does it relate to other things? │
│ │
│ A definition does NOT specify: │
│ • HOW to implement it (that's rules/) │
│ • WHAT to do with it (that's todo/) │
└─────────────────────────────────────────────────────────────────┘
Use ogt-docs-define when you need to:
For specific definition types, use:
| Type | Sub-Skill | Use When |
|---|---|---|
| Business concepts | ogt-docs-define-business |
Pricing, users, revenue, market |
| Product features | ogt-docs-define-feature |
New capabilities, user-facing features |
| Technical architecture | ogt-docs-define-code |
Services, data models, APIs |
| Marketing concepts | `ogt-docs-define-marketing... |
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# OGT Docs - Define Guide for creating definition documents that establish WHAT things ARE in your system. ## Philosophy **Definitions are the foundation of shared understanding.** Before anyone can implement, market, or discuss something, there must be a clear, agreed-upon definition of what it IS. ``` ┌─────────────────────────────────────────────────────────────────┐ │ THE DEFINITION PRINCIPLE │ ├─────────────────────────────────────────────────────────────────┤ │ A definition answers: │ │ • WHAT is this thing? │ │ • WHY does it exist? │ │ • WHAT are its boundaries? (what it is NOT) │ │ • HOW does it relate to other things? │ │ │ │ A definition does NOT specify: │ │ • HOW to implement it (that's rules/) │ │ • WHAT to do with it (that's todo/) │ └─────────────────────────────────────────────────────────────────┘ ``` ## When to Use This Skill Use `ogt-docs-define` when you need to: - Understand the definitions folder structure - Choose the right definition sub-skill - Create a definition that doesn't fit specialized categories **For specific definition types, use:** | Type | Sub-Skill | Use When | | ---------------------- | --------------------------- | -------------------------------------- | | Business concepts | `ogt-docs-define-business` | Pricing, users, revenue, market | | Product features | `ogt-docs-define-feature` | New capabilities, user-facing features | | Technical architecture | `ogt-docs-define-code` | Services, data models, APIs | | Marketing concepts | `ogt-docs-define-marketing...
University for AI agents. 92 courses, 4400+ scenarios, any model via OpenRouter. Auto-training loops generate per-model SKILL.md documents. Works with Claude Code, OpenClaw, Cursor, Windsurf. No fine-tuning req...
macOS WPS Office workflow helper skill for safer document preparation, conversion, export, and compatibility guidance
A股分析技能
A2A4B2B Skill for OpenClaw