Getting Started
Glossary
Definitions of key terms used throughout MyClaude documentation.
ReferenceUpdated 2026-03-25
Definitions of key terms used throughout MyClaude documentation.
Product categories
| Term | Definition |
|---|---|
| Skill | A callable prompt routine stored in .claude/skills/ that extends Claude Code with domain-specific capabilities. Invoked with /skill-name in Claude Code. |
| Squad | A multi-agent team with coordinated workflows, enabling complex tasks through agent collaboration. Defined by a roster of agents with assigned roles. |
| Agent | A single-purpose AI entity with specialized knowledge and defined tool access. Operates autonomously within its domain. |
| Workflow | A multi-step automation pipeline that chains tools, agents, and skills into a repeatable process. |
| Design System | A complete token set, component library, and design rules for consistent UI development across projects. |
| Prompt | A reusable system prompt or template optimized for a specific task or domain. |
| CLAUDE.md | A project configuration file containing rules, context, and behavioral directives for Claude Code. |
| Application | A full application built for or with Claude Code, ready to deploy. |
Platform concepts
| Term | Definition |
|---|---|
| vault.yaml | A 9-15 line YAML manifest that defines metadata, pricing, and configuration for any MyClaude product. Required for publishing. |
| CONDUIT | The Engine-to-CLI-to-API publishing pipeline protocol. Connects Creator Engine, CLI, and marketplace API. |
| MCS | MyClaude Certified Standard. A quality badge awarded to products that pass automated and manual review. |
| Creator Engine | A standalone tool for building MyClaude products. Scaffolds vault.yaml, validates structure, and prepares for publishing. |
| MyClaude CLI | Command-line interface for interacting with MyClaude marketplace. Install globally via npm install -g @myclaude-cli/cli. |
Technical terms
| Term | Definition |
|---|---|
| PRISM | Prismatic Documentation Architecture. The framework governing this docs system — one source, three surfaces. |
| H-Surface | Human-facing documentation. The visual docs site with navigation and search. |
| A-Surface | Agent-facing documentation. Machine-readable specs, MCP tools, and context payloads. |
| G-Surface | GEO-facing documentation. Schema.org markup, llms.txt, and quotable passages for AI search engines. |
| GEO | Generative Engine Optimization. Optimizing content for AI search engines like ChatGPT, Perplexity, and Google AI Overviews. |
| Diataxis | A 4-type documentation model: Tutorial, How-To, Reference, Explanation. Used to classify every page. |
| llms.txt | A machine-readable site description file at the site root, following the llms.txt spec. Includes behavioral directives for AI agents. |
| Stripe Connect | The payment infrastructure used by MyClaude. Creators receive 92% of each sale (8% platform fee). |
| Signed URL | A time-limited download URL generated server-side for paid product files. Expires after 5 minutes. |
Marketplace terms
| Term | Definition |
|---|---|
| Creator | A MyClaude user who publishes products to the marketplace. |
| Buyer | A MyClaude user who discovers, installs, or purchases products. |
| Platform fee | 8% fee on paid product sales, collected via Stripe Connect. |
| Product slug | A URL-safe identifier for a product, auto-generated from the product name. |
Related pages
- Concepts Overview — marketplace mental model
- vault.yaml Specification — product manifest reference
- CLI Commands Reference — all 12 CLI commands