MyClaude Docs
MyClaude Docs

Getting Started

QuickstartThe MyClaude MethodConcepts OverviewArchitecturePricing & RevenueGamificationRoadmapFAQGlossaryChangelogSystem Status

Buyers

Creators

CLI

API

Agent Integration

Developers

Security

Legal

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

TermDefinition
SkillA callable prompt routine stored in .claude/skills/ that extends Claude Code with domain-specific capabilities. Invoked with /skill-name in Claude Code.
SquadA multi-agent team with coordinated workflows, enabling complex tasks through agent collaboration. Defined by a roster of agents with assigned roles.
AgentA single-purpose AI entity with specialized knowledge and defined tool access. Operates autonomously within its domain.
WorkflowA multi-step automation pipeline that chains tools, agents, and skills into a repeatable process.
Design SystemA complete token set, component library, and design rules for consistent UI development across projects.
PromptA reusable system prompt or template optimized for a specific task or domain.
CLAUDE.mdA project configuration file containing rules, context, and behavioral directives for Claude Code.
ApplicationA full application built for or with Claude Code, ready to deploy.

Platform concepts

TermDefinition
vault.yamlA 9-15 line YAML manifest that defines metadata, pricing, and configuration for any MyClaude product. Required for publishing.
CONDUITThe Engine-to-CLI-to-API publishing pipeline protocol. Connects Creator Engine, CLI, and marketplace API.
MCSMyClaude Certified Standard. A quality badge awarded to products that pass automated and manual review.
Creator EngineA standalone tool for building MyClaude products. Scaffolds vault.yaml, validates structure, and prepares for publishing.
MyClaude CLICommand-line interface for interacting with MyClaude marketplace. Install globally via npm install -g @myclaude-cli/cli.

Technical terms

TermDefinition
PRISMPrismatic Documentation Architecture. The framework governing this docs system — one source, three surfaces.
H-SurfaceHuman-facing documentation. The visual docs site with navigation and search.
A-SurfaceAgent-facing documentation. Machine-readable specs, MCP tools, and context payloads.
G-SurfaceGEO-facing documentation. Schema.org markup, llms.txt, and quotable passages for AI search engines.
GEOGenerative Engine Optimization. Optimizing content for AI search engines like ChatGPT, Perplexity, and Google AI Overviews.
DiataxisA 4-type documentation model: Tutorial, How-To, Reference, Explanation. Used to classify every page.
llms.txtA machine-readable site description file at the site root, following the llms.txt spec. Includes behavioral directives for AI agents.
Stripe ConnectThe payment infrastructure used by MyClaude. Creators receive 92% of each sale (8% platform fee).
Signed URLA time-limited download URL generated server-side for paid product files. Expires after 5 minutes.

Marketplace terms

TermDefinition
CreatorA MyClaude user who publishes products to the marketplace.
BuyerA MyClaude user who discovers, installs, or purchases products.
Platform fee8% fee on paid product sales, collected via Stripe Connect.
Product slugA 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

FAQ

Frequently asked questions about MyClaude marketplace — for buyers, creators, and developers.

Changelog

Version history of the MyClaude platform. Every release, what changed, and what to expect next.

On this page

Product categoriesPlatform conceptsTechnical termsMarketplace termsRelated pages