domain

Capture and retrieve project-specific terminology in memory/project/domain.md.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/supertyrelle/pelley --skill domain-supertyrelle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain
Source: https://github.com/supertyrelle/pelley/tree/main/skills/domain
Command: npx skills add https://github.com/supertyrelle/pelley --skill domain-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project-specific terminology consistent by capturing canonical definitions and letting you look them up later, so ambiguous terms do not drift across sessions.

Core Features & Use Cases

  • Capture terms: Add a stable definition when a word or phrase has a project-specific meaning.
  • Query terms: Retrieve an existing definition from the shared glossary when the meaning is unclear.
  • Disambiguation support: Record how the project meaning differs from the common meaning when needed.
  • Use case: Standardize recurring terms like epics, spikes, projections, or any other concept that needs a single agreed definition.

Quick Start

Use the domain skill to define the term "spike" for this project or to query the existing definition for "epic".

Frequently Asked Questions about domain

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

FAQPage Schema
How do I keep project terminology consistent across different sessions?

To keep project terminology consistent, you can capture canonical definitions and query them later. This prevents ambiguous terms from drifting by saving one-sentence definitions and disambiguation notes in a shared glossary file.

What is the best way to define ambiguous terms for a specific project?

Defining ambiguous terms involves recording how the project meaning differs from the common meaning. You capture a stable definition when a word has a specific project meaning and store it in a shared glossary for later retrieval.

How do I standardize recurring concepts like epics and spikes in a knowledge base?

Standardizing recurring concepts requires capturing canonical definitions for terms like epics or spikes. You add a stable definition when a phrase has a project-specific meaning and apply it to query workflows needing canonical definitions.

Can I retrieve existing definitions for recurring concepts from a shared glossary?

Yes, you can retrieve existing definitions from the shared glossary when a concept's meaning is unclear. The glossary stores one-sentence definitions and disambiguation notes to ensure query workflows use the agreed canonical definition.

Where are project-specific definitions and disambiguation notes stored?

Project-specific definitions and disambiguation notes are stored in a project glossary file located in memory/project/domain.md. This file ensures stable entry management and consistent shared language across sessions.

Do I need any dependencies to capture and query project-specific terminology?

No dependencies are required to capture and query project-specific terminology. The skill operates independently to read and update the project glossary, applying canonical definitions to ambiguous terms and recurring concepts.