How do I install the Skill Saas Core Limits skill?

Run npx skillmds@latest add iapro-community/skill-saas-core-limits in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skill Saas Core Limits safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skill Saas Core Limits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skill Saas Core Limits free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skill Saas Core Limits?

IAPro-Community (@iapro-community) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skill Saas Core Limits by iapro-community

Name: Skill Saas Core Limits
Author: IAPro-Community

Skill Saas Core Limits

Implement SaaS plan limits, quotas, entitlements, feature flags, trials, grace periods, blocked accounts, usage counters, and access checks after AbacatePay, Stripe, webhook, or manual admin subscription changes.

File contents

skill-saas-core-limits

Workflow

Identify the billable actor: user, tenant, workspace, account, organization, or project.
Inventory gated features and usage counters. Classify each as hard limit, soft limit, feature flag, trial-only feature, admin override, or informational banner.
Model entitlements independently from payment provider objects. Store provider IDs as evidence, not as the product access model.
Enforce important limits server-side, in RPC, or through RLS. Use frontend checks only for early feedback.
Make usage updates atomic when races are possible.
Add audit logs for payment sync, admin overrides, blocked states, automatic deactivation, and limit resets.
Verify transitions with focused tests, SQL checks, or manual scenarios.

Data Model

plans: code, display name, active flag, currency, price, interval, feature limits JSON.
entitlements: actor ID, plan ID, status, starts_at, ends_at, grace_until, provider, provider IDs, override fields.
usage_counters: actor ID, feature key, period start/end, used count, hard limit, reset policy.
audit_logs: actor, action, before/after, reason, source, correlation ID.

Status Contract

Subscription/access states: trialing, active, grace, past_due, cancelled, expired, blocked.
Usage states: ok, caution, warning, limit_reached, expired.
Suggested thresholds: caution at 70%, warning at 90%, limit_reached at 100%.

Guardrails

Do not grant or revoke access from a checkout success redirect alone.
Do not trust frontend counters for enforcement.
Do not scatter plan logic across UI components. Centralize in backend services, RPC, or shared domain helpers.
Do not block paid users silently. Return actionable errors and show upgrade/recovery paths.
Keep grace-period and cancellation policy explicit; do not infer it from provider defaults.

Local Reference

For a concrete local pattern, inspect {{USER_HOME}}/Documents\Code\example-saas\src\lib\planLimitChecker.ts only when implementing similar Supabase/RPC usage checks.

Related Skills

skill-saas-factory
skill-abacatepay-integration
skill-stripe-integration
skill-supabase-rls

---name: skill-saas-core-limitsdescription: Implement SaaS plan limits, quotas, entitlements, feature flags, trials, grace periods, blocked accounts, usage counters, and access checks after AbacatePay, Stripe, webhook, or manual admin subscription changes.---# skill-saas-core-limits## Workflow1. Identify the billable actor: user, tenant, workspace, account, organization, or project.2. Inventory gated features and usage counters. Classify each as hard limit, soft limit, feature flag, trial-only feature, admin override, or informational banner.3. Model entitlements independently from payment provider objects. Store provider IDs as evidence, not as the product access model.4. Enforce important limits server-side, in RPC, or through RLS. Use frontend checks only for early feedback.5. Make usage updates atomic when races are possible.6. Add audit logs for payment sync, admin overrides, blocked states, automatic deactivation, and limit resets.7. Verify transitions with focused tests, SQL checks, or manual scenarios.## Data Model- `plans`: code, display name, active flag, currency, price, interval, feature limits JSON.- `entitlements`: actor ID, plan ID, status, starts_at, ends_at, grace_until, provider, provider IDs, override fields.- `usage_counters`: actor ID, feature key, period start/end, used count, hard limit, reset policy.- `audit_logs`: actor, action, before/after, reason, source, correlation ID.## Status Contract- Subscription/access states: `trialing`, `active`, `grace`, `past_due`, `cancelled`, `expired`, `blocked`.- Usage states: `ok`, `caution`, `warning`, `limit_reached`, `expired`.- Suggested thresholds: `caution` at 70%, `warning` at 90%, `limit_reached` at 100%.## Guardrails1. Do not grant or revoke access from a checkout success redirect alone.2. Do not trust frontend counters for enforcement.3. Do not scatter plan logic across UI components. Centralize in backend services, RPC, or shared domain helpers.4. Do not block paid users silently. Return actionable errors and show upgrade/recovery paths.5. Keep grace-period and cancellation policy explicit; do not infer it from provider defaults.## Local ReferenceFor a concrete local pattern, inspect `{{USER_HOME}}/Documents\Code\example-saas\src\lib\planLimitChecker.ts` only when implementing similar Supabase/RPC usage checks.## Related Skills- `skill-saas-factory`- `skill-abacatepay-integration`- `skill-stripe-integration`- `skill-supabase-rls`

Frequently asked questions