All Skills

Extract reusable code patterns into clean abstractions and comprehensive tests

Expert guide for building CI/CD pipelines with GitHub Actions, Vercel, and other platforms. Use when automating builds, tests, deployments, or release workflows.

Guidelines for web development projects using JavaScript/TypeScript frameworks. Activate when working with web projects, package.json, npm/yarn/pnpm, React, Next.js, Vue, Angular, Svelte, or other web frameworks, frontend components, or Node.js applications.

PREFER /brand-init for new projects (outputs unified brand.yaml). This skill outputs the legacy brand-profile.yaml format. Use --legacy flag or when brand-kit is not available. Interactive brand discovery for a project. Creates brand-profile.yaml that guides all future content generation. Run once per project to establish voice, audience, topics.

Audit landing page: value prop, CTA, social proof, mobile, load time. Outputs structured findings. Use log-landing-issues to create issues. Invoke for: landing page review, conversion audit, launch readiness.

Add observability to any repo: Sentry (errors), PostHog (analytics), Helicone (LLM costs). Auto-detects language/framework. Creates Sentry project via MCP. Installs SDKs, writes config, updates .env.example, opens PR. Supports: Next.js, Node/Express/Hono, Go, Python, Swift, Rust, React Native.

Complete Stripe lifecycle management. Audits current state, fixes all issues, and verifies checkout flows work end-to-end. Every run does all of this. Auto-invoke when: files contain stripe/payment/checkout/webhook, imports stripe package, references STRIPE_* env vars, webhook handlers modified.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Build and maintain AI-accessible knowledge bases for projects

PostHog Auditor Agent

Design a Stripe integration based on business requirements and organizational preferences. Produces a design document that stripe-scaffold will implement.

Reviews React/Next.js code for common runtime pitfalls and anti-patterns not caught by linters

Generate programmatic SEO pages from JSON data using Next.js/React templates, plus sitemap + validation tooling. Use when creating comparison pages, alternatives lists, or “best for [persona]” pages at scale, or when asked to scaffold pSEO data schemas, generate pages, build sitemaps, or check for duplicate/thin content.

Top-level design orchestrator. Compose Tier 1 static skills + design-tokens into complete design systems. Two modes: Explore (greenfield, 6 distinct directions) or Extend (6 targeted refinements to existing system). Replaces evolve, aesthetic-system, design-theme, ui-skills.

Fix Stripe webhook 400 errors in local development. The problem: `stripe listen` generates a new secret each time it starts, but your app uses a stale secret from .env.local. This skill auto-syncs the ephemeral secret before your dev server starts. Auto-invoke when: stripe webhooks return 400, "signature verification failed", "No signatures found matching", webhooks not working locally, checkout succeeds but subscription doesn't update, STRIPE_WEBHOOK_SECRET mismatch, setting up stripe listen, configuring dev scripts with Stripe.

Comprehensive guide for integrating Gemini CLI as research assistant. Use when you need to delegate research to Gemini, understand its capabilities vs Claude's, or determine the right tool for a task.

Documentation clarity, completeness, maintainability, and naming quality

When to use Bun, patterns, and anti-patterns. Covers Bun as package manager vs runtime, workspace configuration, compatibility considerations. Invoke for: bun adoption decision, bun vs pnpm, bun migration planning.

Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.

Apply structured logging best practices using Pino for Node.js applications: JSON output, log levels, context, redaction, correlation IDs, and centralization. Use when implementing logging, reviewing log statements, or discussing observability.

Launch post generator for multiple platforms. Creates Twitter, HN, Reddit, and Indie Hackers announcements. Use for product launches, major updates, or milestone announcements.

Sentry error tracking and production observability. Invoke when: - New Next.js project without error tracking → Suggest setup - Deploying to Vercel → "Add observability before deploying" - Discussing error handling, try/catch → "Track these in production" - Production bug, users reporting errors → Triage with scripts - Setting up monitoring, configuring alerts, reviewing PII handling Scripts: detect_sentry.sh, init_sentry.sh, list_issues.sh, triage_score.sh Keywords: Sentry, production errors, error tracking, triage, alerts, observability, Session Replay, PII redaction, source maps, monitoring

TUI Builder - Senior Terminal UI Designer & Developer

Audit documentation: README, architecture, API docs, .env.example. Outputs structured findings. Use log-doc-issues to create issues. Invoke for: documentation audit, gap analysis, staleness check.