All Skills

GSD Execute — Get Shit Done

Use when the app is slow, pages take too long to load, API responses exceed 200ms, memory usage is high, or renders are excessive. For profiling, identifying bottlenecks, optimizing React renders, reducing bundle size, improving database query speed, and measuring before/after improvements. Activate when user says "it's slow", "optimize this", "reduce load time", or "too many re-renders".

Use this when designing scripts or small tools for automation, maintenance, CI tasks, file manipulation, config generation, or local workflow support across shell, Python, or mixed environments.

Use this when the system needs explicit runtime validation for API inputs, config, queue messages, webhook payloads, file metadata, or external provider responses in TypeScript, JavaScript, Python, or mixed systems.

Use this when reviewing or designing how secrets, API keys, service credentials, signing keys, tokens, and environment-specific credentials are stored, loaded, rotated, and kept out of untrusted runtimes.

Use when designing a new system, choosing between architectural patterns, planning how components will connect, evaluating scalability and reliability trade-offs, or reviewing an existing system for structural problems. For system design, service boundaries, database design, API structure, monolith vs microservices decisions, and architecture decision records (ADRs). Activate when user says "how should I structure this", "design the system", "is this architecture right", or "plan the backend".

Use this skill when designing UI components, choosing color palettes, implementing responsive layouts, or reviewing code for UX issues. For landing pages, dashboards, e-commerce, SaaS, and mobile apps. Provides 50+ design styles, 97 color palettes, 57 font pairings, and stack-specific guidelines for React, Vue, Next.js, Flutter, SwiftUI, and more.

Plan backend domains, services, jobs, integrations, and failure handling for a product or major feature. Use when UX and product scope are defined and the team needs a production-minded backend design without defaulting to premature microservices.

Use when a Supabase app needs Row Level Security policies for multi-tenant access, ownership checks, roles, service paths, or safe data exposure. Trigger on requests to design or review Supabase RLS and SQL authorization logic.

Evaluate a raw app, startup, SaaS, internal tool, marketplace, or AI product idea before planning features. Use when the user shares a vague concept and needs pain analysis, market realism, feasibility, differentiation, risks, or a build/no-build recommendation.

Plan screens, views, and page responsibilities for a product flow. Use when user journeys already exist and the team needs a screen inventory, screen purpose, key states, and component-level responsibilities without jumping into visual styling too early.

Use this when reviewing whether an app, service, worker, CLI, or serverless system is ready for its target environment with respect to config, secrets, migrations, dependencies, observability, rollback, and runtime constraints.

Use when context window is filling up, sessions are getting slow, or you need to preserve state across sessions. For context compression, state snapshots, search-first discipline, and cross-session memory management.

Use when creating React/TypeScript components, pages, or features. For modern patterns including Suspense, useSuspenseQuery, lazy loading, MUI v7 styling, TanStack Router, and performance optimization.

Use when the user wants to create a new Antigravity skill pack or add a focused skill folder with SKILL.md, references, examples, or scripts. Trigger on requests to generate a skill, scaffold a skill, or expand the local skill library.

Use this when reviewing or designing Firebase security rules for Firestore or related client-accessed Firebase data. Trigger on requests about Firebase rules safety, access constraints, auth-claim checks, or client data exposure.

Use this when a Python repository needs package-level planning, import boundaries, module naming, reusable library extraction, or distribution-friendly structure.

Use this skill when the user is working with Supabase and needs help with Edge Functions, SQL schema or migrations, Auth, Row Level Security, database functions, local CLI workflows, or deployment. Use it for building features, reviewing Supabase code, creating migrations, writing policies, implementing auth-aware server logic, and debugging full Supabase app flows.

Use this when a Supabase app needs file or object storage design, bucket strategy, signed URL handling, metadata patterns, upload trust boundaries, or storage access controls.

Design product-led growth loops, activation paths, and expansion mechanics for a software product. Use when the team needs onboarding-to-value planning, sharing or collaboration loops, retention hooks, or realistic post-launch growth motions tied to product usage.

Use when the team needs pricing, packaging, free-tier, trial, usage metering, or business-model guidance for a software product. Trigger on requests to design how the product should make money or control value access.

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

Review whether a product, MVP, or feature is actually ready to launch. Use when the team needs a production-minded check across product quality, UX edge cases, auth and security, observability, support readiness, pricing readiness, and post-launch measurement.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Extract the core product philosophy, strategic posture, and design principles from a raw concept or founder brief. Use when the team needs a crisp product promise, guiding principles, product point of view, or a philosophy statement before scope and UX planning.

Design pricing, packaging, and monetization strategy for a software or AI product. Use when the team needs plan structure, free-tier logic, usage vs seat pricing tradeoffs, paywall timing, or monetization guardrails tied to product value and costs.

Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Use this skill to write and run SQL queries, pull data, build metrics, or answer analytical questions. Always use this skill when you need to query data.

Use this skill for any data or analytics task — querying databases, analyzing metrics, exploring data warehouses, processing datasets, or creating visualizations.

Creates a git commit and pushes to remote. Use -a to amend. Optionally accepts a commit message.

Use this skill for any coding task that involves working with repositories, writing code, creating branches, or opening pull requests. Covers the full development workflow from cloning to PR.

Expert jq usage for JSON querying, filtering, transformation, and pipeline integration. Practical patterns for real shell workflows.

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

Fetch any X/Twitter post as clean LLM-friendly JSON. Converts x.com, twitter.com, or adhx.com links into structured data with full article content, author info, and engagement metrics. No scraping or browser required.

Cirq is Google Quantum AI's open-source framework for designing, simulating, and running quantum circuits on quantum computers and simulators.

Build ultra-fast web APIs and full-stack apps with Hono — runs on Cloudflare Workers, Deno, Bun, Node.js, and any WinterCG-compatible runtime.