メニュー
Use when: explaining Monaiq domain concepts, entity relationships, FeatureKey semantics, namespace locations, products, features, offerings, licenses, credentials, or checkout terminology.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | domain-reference |
| description | Use when: explaining Monaiq domain concepts, entity relationships, FeatureKey semantics, namespace locations, products, features, offerings, licenses, credentials, or checkout terminology. |
| agent | monaiq |
| auto-invoke | ["User asks about Monaiq entity relationships or domain concepts","User wants to understand the licensing domain model","User asks what a FeatureKey, ProductOffering, or LicenseFeature is"] |
| tags | ["domain","model","knowledge","reference"] |
| category | domain |
| allowed-tools | ["Read","fetch_step_resources","monaiq_journal","mcp__plugin_monaiq_monaiq__fetch_step_resources","mcp__plugin_monaiq_monaiq__monaiq_journal"] |
| argument-hint | topic (entities|features|offerings|licenses) |
| tier | 3 |
| invoked-by | ["getting-started","manage-catalog","implement-licensing"] |
If invoked without upstream context, asks the user what they want to understand.
Provides to requesting skill: - domainContext: { entities: relevant entity descriptions, relationships: key connections, fieldReference: critical field definitions }This is a support skill — invoked on-demand by other skills, not part of a linear chain.
Follow the Direct Invocation Contract in `_shared/protocols.md` (read-only variant). Pivot to the mutation-capable variant the moment the user asks for catalog, credential/config, or app-behavior changes.<execution_context>
Follows the skill layout and shared workflows in _shared/protocols.md. This is a read-only reference skill; it answers domain questions without journal startup unless the user pivots to consequential work.
</execution_context>
monaiq://domain/model and focus on that entity.monaiq://domain/namespaces.Fetch the domain model MCP resource. This contains comprehensive documentation of all entities, their relationships, key fields, polymorphic hierarchies, and invariants.
Fetch monaiq://domain/model via the MCP resources/read operation or fetch_step_resources tool before proceeding.
Key entities covered:
Fetch the namespace reference MCP resource. This provides authoritative type-to-namespace mappings for .NET and React, ensuring code references use the correct imports.
Fetch monaiq://domain/namespaces via the MCP resources/read operation or fetch_step_resources tool before proceeding.
Use the fetched resources as internal context to answer the user's specific domain question. Provide a focused answer about the entities, relationships, or concepts they asked about.
Common question patterns:
| Question Type | Key Entities | Critical Fields |
|---|---|---|
| "What is a FeatureKey?" | ProductFeature, FeatureOffering, LicenseFeature | FeatureKey — the linking field across catalog and runtime |
| "How do features work?" | ProductAccessFeature, ProductRateLimitFeature | Feature flags (Access) and usage limits (RateLimit) — polymorphic types with distinct assertion classes |
| "What's the difference between offerings and licenses?" | ProductOffering, License | Pricing tier (Offering) = pricing template, License = issued entitlement |
| "How does checkout connect to licensing?" | CheckoutRequest, License, EncodedCredential | CorrelationId flow, credential provisioning |
| "What types are in which namespace?" | All entities | Use monaiq://domain/namespaces reference |
<success_criteria>
monaiq://domain/model) was fetched and used as contextmonaiq://domain/namespaces resource
</success_criteria>Use when: analyzing an existing codebase to identify licensable capabilities, premium features, API quotas, exports, integrations, or monetization candidates; classifies findings as access gates or rate limits.
Use when: designing pricing strategy, tiers, subscriptions, trials, perpetual licenses, usage-based billing, or catalog-ready offering plans; does not create catalog entities.
Use when: onboarding a new or returning Monaiq user, establishing a session, checking profile/catalog state, choosing the next licensing workflow, or asking where to start.
Use when: adding Monaiq feature gates, access checks, premium feature enforcement, rate-limit assertions, consumption recording, or license feature checks to an SDK-integrated app.
Use when: integrating the Monaiq licensing SDK into a .NET or React app, installing packages, configuring credentials/endpoints, registering services/providers, or verifying runtime license validation.
Use when: adding an in-app license purchase flow, buy button, Stripe checkout session, checkout result handling, credential persistence, or post-purchase SDK refresh.