Menú
ShipRadar subscription tiers, pricing strategy, and Pro feature definitions. Use when discussing pricing plans, comparing tiers, implementing tier-gated features, or wiring up the billing provider.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
| name | pricing-tiers |
| description | ShipRadar subscription tiers, pricing strategy, and Pro feature definitions. Use when discussing pricing plans, comparing tiers, implementing tier-gated features, or wiring up the billing provider. |
| Feature | Free | Pro |
|---|---|---|
| Repos tracked | 25 | Unlimited |
| AI summaries | 25/month | Unlimited |
| Channels | Telegram, Discord, Email | All + webhooks |
| Webhooks | 1 | 5 |
| Check frequency | 15 min | 15 min |
| Release type filters | Yes | Yes |
| Notification history | 7 days | 90 days |
| GitHub stars import | - | Yes |
Launch (Early Adopters):
Regular (After Launch):
Handled by the billing provider (TODO: Stripe):
notification_history tableGET /notifications/history endpoint (Pro only)/dashboard/historyuser_webhooks table// packages/database/src/schema/user-limits.ts
export const userLimits = pgTable("user_limits", {
userId: text().primaryKey().references(() => users.id, { onDelete: "cascade" }),
tier: text().default("free").notNull(), // 'free' | 'pro'
aiSummariesUsed: integer().default(0).notNull(),
aiSummariesResetAt: timestamp(), // Reset monthly
});
const TIER_LIMITS = {
free: { maxRepos: 25, maxAiSummaries: 25, maxWebhooks: 1 },
pro: { maxRepos: Infinity, maxAiSummaries: Infinity, maxWebhooks: 5 },
};
Apply middleware to:
POST /repos - Check repo count vs tier limitPOST /webhooks - Check webhook count vs tier limitPolar has been removed. The subscription/tier UI and
useUserTierhook remain in place but inert — every user is treated asfreeuntil a provider is wired in. Checkout/portal CTAs are commented out withTODO(stripe)markers in:subscription-section.tsx,pricing-cards.tsx,marketing-pricing.tsx,upgrade-prompt.tsx, anduse-user-tier.ts.
When integrating Stripe, the provider should supply:
authClient.checkout()
/ authClient.customer.* calls).profree/app/(marketing)/pricing/page.tsx