Loading...
Loading...
Found 885 Skills
After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the founder returns to every session to see where they are and the single next move. Use right after start-here, whenever the founder doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.
Comprehensive guide for building with Prisma 8 (Prisma Next), the contract-first data layer. Use whenever working on Prisma code in a project that uses it — authoring or editing the data contract (contract.prisma, PSL, TypeScript builders), migrations, queries (db.orm / db.sql), runtime wiring (db.ts, middleware, DATABASE_URL), build-tool integration, Supabase / RLS, reading PN-* structured errors, or filing feedback — and for orientation questions like "what is Prisma Next" or comparisons to other ORMs. Signals that this skill applies: @internal/* imports, prisma-next.config.ts, contract.prisma / contract.json / contract.d.ts, the prisma-next CLI, PN-* error codes. Does not apply to Prisma ORM 7 or earlier (schema.prisma + @prisma/client projects).
Debug Django web applications with systematic diagnostic approaches. This skill covers troubleshooting Django-specific errors including TemplateDoesNotExist, ImproperlyConfigured, IntegrityError, migration conflicts, CSRF failures, N+1 query problems, and circular imports. Includes Django Debug Toolbar setup, ORM query logging, pdb/ipdb usage, shell_plus debugging, and comprehensive logging configuration. Provides four-phase methodology for root cause analysis and regression prevention.
Technical Research - investigates the codebase and builds a catalogue of solution variants per problem area. Iterative — can be re-run to widen the catalogue. Does not make decisions; selection happens in spec:design.
Derive a project's design system from the UI it already ships and keep it true as the code moves — a spec-compliant DESIGN.md at the repo root, validated by the official linter. Use when the user says "write a DESIGN.md", "document our design system", "extract our design tokens", "our design system is out of date", "audit our design tokens", "what colors does this project actually use", or "/designkit". Not a UI generator, not a palette library.
Survey a project read-only — git working tree, GitHub issues and their declared priority, open PRs, unfiled plans — into a one-screen dashboard that crowns one finish-first next move routed to the kit that does it, saved by default as a throwaway snapshot under docs/status/. Use when you sit down at a project and ask "what should I do next", "check project status", "what's next", "what's most important right now", "orient me", "write me a status file", or run "/statuskit" — add "just print it" or "no file" to skip the snapshot.
Generate faceless content video prompts for Seedance 2.0 on Higgsfield. Use for faceless YouTube channels, TikTok content without showing face, anonymous creator content, narration-driven videos, stock-footage-style AI content, or any video where the creator doesn't appear on camera. Triggers on faceless, no face, anonymous, narration, stock footage, b-roll, background video, voiceover video.
Rigorously evaluate an Agent Skill end-to-end across ANY coding-agent CLI — verify its scripts emit the documented numbers (deterministic checks), test whether its description triggers on the right prompts, and measure whether an agent following the SKILL.md beats a no-skill baseline (with/without pass-rate delta, mean ± stddev, benchmarked). Use whenever you need to test, benchmark, validate, grade, or quantify a skill's quality, check if a skill "actually works," compare two skill versions, optimize a skill's triggering, or set up an eval suite — even if the user just says "is this skill any good," "does my skill work," or "benchmark this skill." Drives Claude Code, OpenAI Codex, Antigravity (agy), Cursor, GitHub Copilot, Amp, opencode, or Grok in headless mode.
Define a brand's verbal identity — tone, voice, writing style, vocabulary, and messaging rules. Use when the user says "brand voice", "tone of voice", "how should we write", "writing guidelines", "copy style guide", "brand language", "verbal identity", "how should the brand sound", "tone guide", "our copy doesn't sound right", "copywriter guidelines", "voice and tone", or when onboarding a copywriter or content team. Also use when the user has a brand strategy and wants to define how the brand communicates.
The idea-system craft — never run out of content ideas by running a system instead of waiting for inspiration. Use when someone is out of ideas, stares at a blank calendar, asks where good ideas come from, wants an idea bank/backlog, feels their AI-generated ideas sound like everyone else's, or thinks their niche is "boring." Uses the SPARK framework. Reads brand-profile + social-strategy + content-pillars + audience-research first. The audience is the idea engine (comments/DMs/FAQs clustered into themes); AI expands real signals, it doesn't discover them; systems beat muses; trends are a timing filter, not a source. The agent clusters/expands/scores; the HUMAN supplies proprietary signals and decides; WoopSocial publishes the content, not ideas. Never rewords competitor posts, invents audience questions, or fabricates probe results. Distinct from social-strategy/content-pillars, audience-research, cross-platform-repurposing/ content-recycling, and the format skills.
Turn a SPEC, PRD, or any stated goal into a high-level executable PLAN of outcome-shaped tasks, and regenerate that plan when execution reveals it is wrong. Use this skill whenever the user asks to plan, break down, decompose, sequence, or roadmap work from a spec/requirements document or a goal, and whenever an executor's replan gate fires because a task's postcondition failed, expected state does not exist, a planned task is impossible, or new information invalidates a later task. Runs in two modes, initial planning and replanning, and always produces the same PLAN.md format.
How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.