Glossary

The repository glossary records established terms, definitions, local scope, and source evidence. Its entries remain provisional because independent reader review is absent. A provisional glossary does not authorize a repository-wide rename. The JSON glossary owns the definitions. Its generated reader view gives the complete entries and citations.

Distinguish the concepts

Concept	Distinction
`marketplace`	The catalog lists installable packages and their sources.
`plugin`	One package adds capabilities to an agent application.
`plugin manifest`	A file declares that package’s metadata and components.
`skill`	A directory supplies task instructions in `SKILL.md` and optional resources.
`hook`	A configured action responds to a lifecycle event and its filter.
`agent profile`	A named configuration selects tools and settings for an agent’s workflow.
`style rule`	A linter configuration defines a prose condition and its reported finding.
`vocabulary`	A prose linter’s collection of accepted or rejected word forms.

This table explains distinctions for site readers. It does not create another glossary contract. Consult the JSON source for the complete definition and scope.

Change terminology

Use current domain sources for a new term. Do not infer synonymy from similar wording or related roles. A replacement target needs evidence of the same concept throughout the declared scope. An ambiguous form needs context review. The glossary currently registers no replacement or review targets. That result does not prove that the domain contains no alternate labels. The glossary contract defines scope and registration rules. The writing procedure uses this source during assessment.

Plugins

Contracts

Distinguish the concepts

Change terminology

​Distinguish the concepts

​Change terminology

Distinguish the concepts

Change terminology