agent-skills

Initialize a production-ready Next.js web application with TypeScript, an application auth layer, Stripe payments, and database setup. Use when creating SaaS applications, e-commerce sites, or full-stack web applications.

Bootstrap a complete SaaS application using Turborepo with Next.js backend, Expo mobile app, an app-level auth layer, Stripe payments, Turso database, Sentry monitoring, PostHog analytics, tRPC, and TanStack Query.

Integrate Stripe payments into Next.js and Expo applications with subscriptions, one-time payments, webhooks, and customer management. Use for SaaS billing and e-commerce.

Use when provisioning, reviewing, or hardening infrastructure that runs on Hetzner Cloud. Inventories hcloud, Terraform, cloud-init, and service bootstrap signals in the repo, then writes an operations plan for server lifecycle, networking, bootstrap, and drift instead of treating Hetzner as an opaque VPS host.

Use when planning or reviewing domain and DNS operations for domains registered at Namecheap. Inventories domain, nameserver, and host-record signals in a repo, checks whether the workflow belongs in Namecheap or a third-party DNS provider, and produces a concrete DNS operations plan instead of ad hoc panel clicking.

Use when a web app or product surface needs PostHog instrumentation reviewed or added with discipline. Inventories SDK setup, provider wiring, event capture calls, identify/group usage, and feature-flag boundaries, then produces a concrete instrumentation plan instead of ad hoc analytics sprawl.

Use when a web app or service has Sentry installed and the task is to verify release readiness, source map correctness, environment wiring, or basic issue-triage hygiene before or after shipping. Inventories SDK setup, config files, release markers, and error-boundary coverage, then writes a focused triage plan.

Use when adding, debugging, or hardening Cloudflare D1 usage in a Workers app. Inventories Wrangler D1 configuration, local-vs-remote database assumptions, migration and seeding workflow, and app-level access patterns, then produces a concrete development plan before deeper implementation work.

Use when a vinext project already builds or runs, but the Cloudflare deployment surface still needs hardening. Reviews Wrangler config, assets and image bindings, cache strategy, environment boundaries, and production-risk gaps, then writes a concrete hardening plan before deploy work.

Use when setting up, debugging, or hardening local development for a Cloudflare Workers project that depends on bindings like D1, KV, R2, Queues, Durable Objects, or Workflows. Inventories Wrangler config, environment-specific bindings, and local-versus-remote development assumptions, then produces a concrete local-dev plan.

Use when adopting, validating, or hardening a Next.js deployment on Cloudflare Workers via OpenNext. Maps the repo shape, checks adapter and Wrangler prerequisites, reviews bindings and local-dev setup, and produces an adoption plan before deeper implementation or migration work.

Use when an Expo app is already validated and you need to build or upload it with EAS Build and EAS Submit. Handles profile selection, credential assumptions, TestFlight or Play upload flow, and submission sequencing after technical readiness and QA are already complete.

Use when validating an Expo app before internal release, TestFlight, Play testing, or store submission. Checks project config, EAS profiles, identifiers, assets, environment handling, and build-significant drift so the app is technically ready before QA handoff or submission.

Use when preparing a React Native or Expo app for internal release, TestFlight, Play internal testing, or store submission. Discovers the project’s release surface, sequences Maestro QA, Expo validation, versioning, environment, OTA, and review-note checks, then hands off to narrower skills for fixes, App Store review, and submission.

Use when a React Native or Expo app needs local mobile QA with Maestro plus targeted fixes. Starts with a report-only Maestro pass, isolates one verified failure at a time, maps it back to app or flow code, applies the smallest fix, and reruns the narrowest failing flow before broadening back out.

Use when a React Native or Expo app needs report-only mobile QA with Maestro on a simulator or emulator. Verifies local prerequisites, runs flows with explicit artifact and report output, captures screenshots and logs, classifies severity, and produces exact repro notes without making code changes.

Use when adding, migrating, or reorganizing skills, tools, or agent definitions in an `agent-skills` style repo and you need to keep the catalog surface coherent. Maintains a merged view of metadata-backed skills, checks for missing metadata, and updates repo-facing catalog snapshots without treating ad hoc notes as the source of truth.

Use when reviewing recent Codex, Claude Code, or repo planning work to extract reusable patterns, mistakes, and candidate skills. Automatically searches the current repo, nearby repos, and home skill/session directories, then writes a retrospective report, proposed skill ideas, or scaffolds depending on the request.

Use when an agent should discover relevant local context on its own before asking for pasted files or paths. Scans the current repo, nearby working repos, and local Claude or Codex directories for plans, docs, reviews, TODOs, and skill artifacts so later workflows can start from real project evidence instead of user-supplied excerpts.

Use when working on the x402 challenge, `smol-agent`, or adjacent agent-economics demos where the task involves turning a small agent system into a credible product or challenge submission. Guides repo mapping, milestone shaping, demo-path prioritization, and what should become a reusable skill versus local glue.

Use when naming or renaming a product, startup, feature, or app and the work depends on brand identity, design culture, domain research, or TLD tradeoffs. This skill starts by diagnosing the product's brand character from the app itself, treats the current name as a disposable codename unless told otherwise, generates naming territories from that identity, checks `.com`, `.net`, `.ai`, and `.io`, and recommends a full brand-plus-domain direction instead of treating availability alone as success.

Migrates Next.js projects to vinext (Vite-based Next.js reimplementation for Cloudflare Workers). Load when asked to migrate, convert, or switch from Next.js to vinext. Handles compatibility scanning, package replacement, Vite config generation, ESM conversion, and Cloudflare deployment setup.

Initialize a new ESP32 project with proper structure and configuration using ESP-IDF. Use when creating ESP32 embedded projects, IoT devices, or microcontroller applications.

Configure and implement WiFi connectivity in ESP32 projects using ESP-IDF

Advanced React debugging techniques using browser DevTools, React DevTools, performance profiling, and error boundaries. Use for troubleshooting complex React applications and performance issues.

Initialize a modern React project with Vite, TypeScript, TanStack Query, Zustand, and shadcn/ui. Use when creating new React applications or setting up React development environments.

Generate modern React UI components using shadcn/ui and Tailwind CSS. Create forms, dashboards, data tables, and interactive components with consistent design patterns.

Debug Unity projects using console logs, breakpoints, profiler, and unity-mcp integration. Use when troubleshooting Unity games, performance issues, or runtime errors.

Initialize a new Unity game project with proper structure, settings, and essential packages. Use when creating Unity games, prototypes, or interactive applications.

Advanced Unity C# scripting patterns, component architecture, and AI-assisted development with unity-mcp. Use for complex gameplay systems, performance optimization, and maintainable code.