productivity▌

Client-side tracking with Analytics.js. Include track, identify, page, and group calls. Anonymous ID persists until identify merges with user.

Brainstorm unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring name options that strengthen your brand positioning.

Create maintainer-friendly pull requests while avoiding 16 common rejection mistakes. \n \n Prevents personal development artifacts (SESSION.md, planning docs, debug screenshots, temp test files) from being committed using a pre-PR check script \n Enforces three critical workflow rules: always use feature branches, test thoroughly before submitting, and keep PRs focused on a single change under 400 lines \n Provides templates and guides for PR descriptions using What/Why/How structure, conventio

You are an expert in viral growth and referral marketing with access to referral program data and third-party tools. Your goal is to help design and optimize programs that turn customers into growth engines.

Fault tolerance and resilience patterns for Spring Boot microservices using Resilience4j. \n \n Provides six core patterns: circuit breaker, retry with exponential backoff, rate limiter, bulkhead (semaphore and thread pool), time limiter, and fallback mechanisms \n Annotation-based integration with Spring Boot 3.x AOP; patterns can be stacked on single methods for comprehensive fault tolerance \n Includes configuration examples for all patterns in YAML, with health indicator and Actuator endpoin

Before giving CRO advice, calculate the Page Conversion Readiness & Impact Index.

Use grizzly to create, read, and manage notes in Bear on macOS.

Use this skill to bulk-create or bulk-update display names (and descriptions) for subscriptions, subscription groups, and in-app purchases across all App Store Connect locales. This eliminates the tedious manual process of clicking through each language in App Store Connect to set the same display name.

Capture conversations and decisions into structured, linkable Notion pages for documentation and knowledge reuse. \n \n Supports six content types: decisions, how-to guides, FAQs, wiki entries, learning notes, and documentation pages, each with dedicated database templates and schemas. \n Workflow includes search and fetch of existing Notion pages to avoid duplication and establish proper linking and relations. \n Requires Notion MCP connection; includes setup steps for OAuth login and remote MC

Technical rigor in code review: receiving feedback critically, requesting systematic reviews, and verifying before any completion claims. \n \n Three core practices: receiving feedback with technical evaluation over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before status claims \n Includes decision tree and protocols for handling feedback from human partners versus external reviewers, with explicit rules against performative