Problem
What problem this solves
Entitlement changes are often implemented incorrectly when access checks are mixed with auth, local caches, or provider callbacks without explicit server-owned ownership.
Menu Open navigation menu Close navigation menu
Build & Fix
Skill Detail
sg-product-entitlements
Design product entitlement ownership and server-side access gates before premium behavior changes.
A product-entitlement skill for suite and standalone access models, provider events, redemption codes, support diagnostics, backend authorization, and sync handoffs.
Outcome
What changes when it works
You get a bounded entitlement contract that separates identity, provider events, and durable access authorization, then routes to sync or auth/debug specialists only where owned.
Why It Matters
What this changes for a solo founder
Small access mistakes can expose premium data or block loyal customers; this skill reduces that risk before implementation starts.
When to use it
- When adding or changing product access, paid plans, feature gates, or premium capabilities
- When handling provider events, activation codes, refunds, revocation, or migration
- When local snapshots/caches exist and entitlement freshness or stale access is risky
- When support teams need predictable grant/revoke/refund diagnostics
What you give it
- Product access scope, project, plan/product identifiers, and entitlement mode
- Current project signals and whether a suite ledger exists
What you get back
- A product entitlement contract or routed implementation plan
- Rules for identity separation, provider-event safety, backend gates, and status semantics
- Support-runbook framing for common grant/revoke/refund support needs
- Explicit handoff to sync and auth-debug specialists where ownership is separate
Typical examples
- /sg-product-entitlements define access checks for a new paid plan
- /sg-product-entitlements audit duplicate entitlement tables before implementation
- /sg-product-entitlements route a refund + sync scenario for product-local data
- /sg-product-entitlements support runbook for code redemption and duplicate account access
Limits
- This skill does not write project code; it produces contract and routing guidance
- Provider/webhook behavior must be validated with current docs before implementation changes depend on it
- It does not replace sg-build, sg-local-cloud-sync, sg-auth-debug, or product-specific implementation specs
Related Skills
See the rest of the loop around this move.
Build & Fix
sg-local-cloud-sync
Design local-to-cloud sync without losing user data.
A data-sync skill for local data promotion, cloud hydration, merge/conflict policy, sync UX states, sensitive-data exclusions, and proof routing.
Open skill page Build & Fix
sg-auth-debug
Debug a broken auth flow in a real browser before you start guessing from static code alone.
A browser-level auth diagnosis skill for reproducing login failures, reading local Clerk/Google/Convex/Flutter references, and isolating the exact break point in the flow.
Open skill page Plan & Decide
sg-spec
Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.
The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.
Open skill page Plan & Decide
sg-ready
Pressure-test a spec before implementation so the thread is not coding against loose intent.
A readiness gate for checking whether a spec is complete, safe, and executable by a fresh agent.
Open skill page Build & Fix
sg-build
Run non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill page Build & Fix
sg-start
Start implementation when the task is ready, and force a stronger path when it is not.
The main execution entrypoint for beginning real work after the problem and contract are clear enough, while keeping the chantier flow visible.
Open skill page Audit & Improve
sg-verify
Check whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill page Operate & Ship
sg-docs
Create or repair documentation so the repo stays navigable for both humans and agents.
A documentation skill for maintaining docs, metadata, and governance-layout compliance across project surfaces.
Open skill page Build & Fix
sg-test
Guide the human through the real user flow, then turn the result into test evidence and actionable bugs.
A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.
Open skill page Operate & Ship
sg-prod
Check whether production is actually healthy after a push instead of assuming the deploy tells the truth.
A production verification skill for deployment status, logs, and live health checks after release.
Open skill pageGo Deeper
This public page explains the move. The repository explains the execution contract.
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.