builder-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Pre-deployment checklist covering migrations, environment variables, feature flags, rollback plan, and smoke tests. Use when user says "ready to deploy", "deployment checklist", "pre-deploy check", "can I ship this", "deploy review", or needs to verify everything is ready before pushing to production.

Set up monitoring with error tracking, alerts, dashboards, and SLOs for production applications. Use when user says "set up monitoring", "add error tracking", "create alerts", "observability", "SLOs", "health checks", "how do I know if it's broken", or needs production visibility.

RESTful API design conventions covering URL structure, HTTP methods, error formats, pagination, versioning, and authentication patterns. Use when designing, reviewing, or implementing APIs. Triggers on API design, endpoint structure, REST conventions, or backend architecture tasks.

TypeScript best practices and advanced type design patterns. Use when writing, reviewing, or refactoring TypeScript code. Covers type narrowing, generics, utility types, discriminated unions, error handling, and module patterns. Triggers on TypeScript, type safety, or type design tasks.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Perform a structured code review covering correctness, readability, performance, security, and maintainability. Use when user says "review this code", "code review", "check this PR", "review my changes", "is this code good", or needs expert feedback on code quality.

Audit project dependencies for outdated packages, known vulnerabilities, unused imports, and bloated bundles. Use when user says "audit dependencies", "check for vulnerabilities", "update packages", "unused dependencies", "bundle size", "dependency cleanup", or needs to maintain healthy dependencies.

Check code for OWASP top 10 vulnerabilities including injection, XSS, auth issues, and secrets exposure. Use when user says "security audit", "check for vulnerabilities", "security scan", "is this secure", "OWASP check", "find security issues", or needs to verify code security before shipping.

Design a database schema from product requirements. Postgres-first with Supabase awareness. Use when user says "design the database", "create schema", "data model", "database structure", "what tables do I need", "schema design", or needs to translate requirements into a relational schema.

Set up environment variables across local, staging, and production with validation and documentation. Use when user says "set up env vars", "environment variables", "configure secrets", ".env setup", "env validation", or needs to manage configuration across environments.

Scaffold a Next.js project with App Router, TypeScript, Tailwind CSS, and opinionated defaults. Use when user says "start a new project", "scaffold Next.js", "init app", "new Next.js app", "create project", or needs a production-ready project foundation.

Initialize Supabase for a project including database schema, Row Level Security policies, authentication, storage buckets, and edge functions. Use when user says "set up Supabase", "add Supabase", "configure database", "add auth", "Supabase init", "RLS policies", or needs a backend with Supabase.

Deploy a project to Vercel with proper configuration, environment variables, domains, and preview deployments. Use when user says "deploy to Vercel", "set up Vercel", "configure deployment", "add a domain", "preview deploys", or needs to ship a project to production.

Write a test strategy covering what to test, coverage targets, and testing pyramid distribution. Use when user says "test plan", "testing strategy", "what should I test", "test coverage", "how to test this", or needs to plan testing for a feature or project before writing tests.

Generate tests for existing code including unit, integration, and e2e tests. Uses Vitest and Testing Library by default. Use when user says "write tests", "add tests", "test this function", "test this component", "need test coverage", or wants tests written for existing code.

Write a product requirements document from context. Covers problem statement, goals, scope, user stories, success criteria, and edge cases. Use when user says "write a PRD", "product requirements", "requirements doc", "spec this feature", "document requirements", or needs to define what to build and why.

Write a technical specification or acceptance criteria from a PRD or user stories. Bridges product requirements to engineering implementation. Use when user says "write a tech spec", "technical specification", "acceptance criteria", "engineering spec", "how should we build this", or needs to translate product requirements into technical plans.

Write job stories or user stories from product requirements. Uses JTBD format "When [situation], I want to [job], so I can [need]". Use when user says "write user stories", "write job stories", "break this into stories", "story mapping", "acceptance criteria", or needs to translate requirements into implementable units.

Structured competitive analysis with feature comparison, positioning maps, and gap identification. Use when user says "competitive analysis", "analyze competitors", "compare products", "market landscape", "who are our competitors", or needs to understand competitive positioning.

Generate user interview scripts, analyze interview transcripts, and extract actionable product insights. Use when user says "create interview guide", "analyze interview", "user research", "interview questions", "research plan", or needs to understand user needs through qualitative research.

Apply Jobs to Be Done thinking to product decisions. Use when defining what to build, who it's for, why they'd switch, or how to prioritize. Works for new products, feature prioritization, competitive positioning, and growth strategy.

One-page business model framework for rapid validation and strategic clarity. Use when user needs to validate a business idea, map out a product strategy, or evaluate product-market fit. Works for new products, pivots, and feature-level business cases. Trigger phrases include "lean canvas", "business model", "one-page plan", "validate this idea", "product-market fit", "business case".

Create a go-to-market plan with positioning, messaging, channels, and launch checklist. Use when user says "go-to-market plan", "GTM strategy", "launch plan", "how do we launch this", "marketing plan", "launch checklist", or needs to plan how a product or feature reaches users.

Define success metrics and KPIs for a feature or product. Identifies leading and lagging indicators with instrumentation guidance. Use when user says "define metrics", "KPIs", "how do we measure success", "success criteria", "what should we track", "instrumentation plan", or needs to quantify outcomes.

Run a structured retrospective for a sprint, launch, or project. Generates actionable insights from what worked and what didn't. Use when user says "run a retro", "retrospective", "post-mortem", "what went wrong", "lessons learned", "sprint review", or needs to reflect on past work and improve.

Score and rank features or initiatives using proven frameworks like RICE, opportunity scoring, or impact/effort. Use when user says "prioritize features", "what should we build first", "rank these ideas", "RICE scoring", "priority matrix", "stack rank", or needs to make data-informed build decisions.

Cut scope ruthlessly to identify MVP, must-haves, nice-to-haves, and out-of-scope items for a given timeline. Use when user says "cut scope", "what's the MVP", "scope this down", "we have X weeks", "reduce scope", "what can we cut", or needs to ship something meaningful within constraints.

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when user says "add animations", "add motion", "make it move", "add micro-interactions", "add transitions", or wants to enhance a static interface with motion.

Amplify safe or boring designs to make them more visually interesting and stimulating. Use when user says "make it bolder", "too boring", "needs more impact", "more visual interest", "too plain", "too safe", or wants to increase visual energy.

Add strategic color to features that are too monochromatic or lack visual interest. Use when user says "add color", "too gray", "too monochrome", "needs color", "more colorful", or wants to add visual warmth to a neutral interface.

Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Use when user says "add delight", "make it fun", "add personality", "too sterile", "add charm", "add polish", or wants to make a functional interface more enjoyable.

Tone down overly bold or visually aggressive designs. Use when user says "too loud", "too bold", "tone it down", "more subtle", "less intense", "too aggressive", "too busy", or wants to reduce visual intensity while maintaining quality.

One-time setup that gathers design context for your project and saves it to your config file. Run once to establish persistent design guidelines.

Product design framework based on the five planes model. Use this skill when designing or evaluating products end-to-end — from strategy through surface. Provides structured thinking for design decisions at every level of abstraction.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Use when user says "make it responsive", "mobile version", "adapt for tablet", "print layout", "support different screen sizes", "responsive design", or needs a design to work in a new context.

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Use when user says "harden this", "handle edge cases", "error handling", "i18n support", "make it robust", "production-ready", or when an interface needs to handle real-world conditions.

Design or improve onboarding flows, empty states, and first-time user experiences. Use when user says "add onboarding", "empty state", "first-time experience", "welcome flow", "getting started", "new user experience", or needs to help users understand and adopt the product.