メニュー
Use when: designing pricing strategy, tiers, subscriptions, trials, perpetual licenses, usage-based billing, or catalog-ready offering plans; does not create catalog entities.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | design-monetization |
| description | Use when: designing pricing strategy, tiers, subscriptions, trials, perpetual licenses, usage-based billing, or catalog-ready offering plans; does not create catalog entities. |
| agent | monaiq |
| auto-invoke | ["User wants to design pricing tiers or a monetization strategy for their product","User asks 'how should I price this' or 'subscription vs perpetual' or 'what pricing model should I use'","User wants help structuring pricing plans, billing intervals, or tier definitions","User mentions pricing confusion, pricing strategy, or monetization approach"] |
| tags | ["strategy","pricing","monetization","tiers","design"] |
| category | strategy |
| allowed-tools | ["register_or_login","product","product_feature","offering","feature_offering","fetch_step_resources","monaiq_journal","mcp__plugin_monaiq_monaiq__register_or_login","mcp__plugin_monaiq_monaiq__product","mcp__plugin_monaiq_monaiq__product_feature","mcp__plugin_monaiq_monaiq__offering","mcp__plugin_monaiq_monaiq__feature_offering","mcp__plugin_monaiq_monaiq__fetch_step_resources","mcp__plugin_monaiq_monaiq__monaiq_journal"] |
| tier | 1 |
| invoked-by | ["user","analyze-codebase","getting-started"] |
Also accepts from analyze-codebase (if chained directly):
If invoked without upstream context, gathers requirements through conversation.
Provides to manage-catalog: - pricingPlan: { tiers: [{ name, classification, baseRate, currency, interval, features: [{ key, type, value }] }] } - productName: user's product nameDiscovery chain endpoint: design-monetization [pricingPlan] → manage-catalog (creates catalog entities from the plan)
<execution_context>
Follows the skill layout and shared workflows in _shared/protocols.md. This skill contributes only catalog-ready pricing strategy and feature-assignment recommendations; catalog mutation belongs to manage-catalog.
</execution_context>
Determine design inputs from available context:
scenario-advisor was run: use the selected scenario (app type, chosen model, feature types) to inform tier structureanalyze-codebase was run: use identified capabilities and their classificationsInfer the appropriate number of tiers from: scenario-advisor output (if available), application complexity, identified feature count, and market norms for the application type.
Using pricing patterns from monaiq://patterns/pricing, propose a complete tier structure:
| Tier | Name | License Type | Price | Interval | Features Included |
|---|---|---|---|---|---|
| 1 | [e.g., Free] | Subscription | $0 | 1 Month | [list with access/rate-limit values] |
| 2 | [e.g., Pro] | Subscription | $X | 1 Month | [list with access/rate-limit values] |
| 3 | [e.g., Enterprise] | Subscription | $Y | 1 Month | [list with access/rate-limit values] |
For each feature in each tier, specify:
Allowed or DeniedUnlimited tiers. When calling the
feature_offeringMCP tool, set bothRateLimitandSampleSecondsto the string"unlimited"for an uncapped assignment. The tool maps that input to the domain's zero-as-unlimited representation internally. Paid capped tiers set explicit positive values (e.g.RateLimit = 1000withSampleSeconds = 3600for 1000/hour).
Explain the rationale: why this many tiers, why these price points relative to each other, and which pricing pattern from monaiq://patterns/pricing this follows.
Present the proposal and invite feedback. Common refinements:
LicenseClassification in Monaiq)Iterate until the user approves the tier structure.
Produce a final structured summary table ready for manage-catalog input:
| Tier Name | Code | License Type | Price | Currency | Interval | Included Features (FeatureKey: Value) |
|---|---|---|---|---|---|---|
| [name] | [code] | [type] | [price] | [currency] | [interval] | [feature1: Allowed, feature2: 500/hr] |
This table contains all fields needed by the manage-catalog skill to create the catalog: product code, offering codes, feature keys with assignment values.
Suggest: "To create this catalog in Monaiq, run the manage-catalog skill with the specification above."
<success_criteria>
monaiq://patterns/pricing was fetched and used for pattern knowledgemanage-catalog suggested as next step
</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: explaining Monaiq domain concepts, entity relationships, FeatureKey semantics, namespace locations, products, features, offerings, licenses, credentials, or checkout terminology.
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.