Loading...
Loading...
Found 2,612 Skills
Build Next.js web applications with Google Gemini Nano Banana image generation APIs (gemini-2.5-flash-image, gemini-3-pro-image-preview). Use when creating image generators, editors, galleries, or any app integrating conversational image generation with server actions, API routes, and storage. Use for "image generation app", "nano banana", "text to image", "AI image generator", or "gemini image". Do NOT use for non-Gemini models, Python/Go backends, model fine-tuning, or image classification/input tasks.
Grafana-to-Perses dashboard migration: export Grafana dashboards, convert with percli migrate, validate converted output, fix incompatibilities, deploy to Perses. Handles bulk migration with parallel processing. Use for "migrate grafana", "grafana to perses", "perses migrate", "convert grafana". Do NOT use for creating new dashboards from scratch (use perses-dashboard-create).
Scene-graph-driven 4-phase Three.js app builder: Design, Build, Animate, Polish. Use when user wants a 3D web app, interactive scene, WebGL visualization, or product viewer. Use for "create a threejs scene", "build 3D web app", "make a 3D animation", or "interactive 3D showcase". Do NOT use for full game engines, 3D model creation, VR/AR experiences, or CAD workflows.
Capture a forward-looking idea as a seed with trigger conditions, scope, and rationale so it surfaces automatically during future feature design. Use for "plant seed", "save this idea for later", "defer this idea", "remember this for when", "seed", or "/plant-seed". Do NOT use for TODOs, immediate tasks, bug reports, or work that should happen in the current session.
Detect and remediate Go anti-patterns: premature interface abstraction, goroutine overkill, context soup, error wrapping mistakes, generic abuse, channel misuse, unnecessary function extraction, and interface pollution. Use when reviewing Go code for quality, detecting over-engineering, or when user mentions "anti-pattern", "code smell", "Go mistake", or "bad Go". Do NOT use for feature implementation, performance optimization without a code smell, or non-Go languages.
Validate content for joy-centered tonal framing. Evaluates paragraphs on a joy-grievance spectrum, flags defensive, accusatory, victimhood, or bitter framing, and suggests reframes. Use when user says "joy check", "check framing", "tone check", "negative framing", "is this too negative", or "reframe this positively". Use for any content where positive, curious, generous framing matters. Do NOT use for voice validation (use voice-validator), AI pattern detection (use anti-ai-editor), or grammar and style editing.
Interactive guide to repository workflow system: agents, skills, routing, and execution patterns. Use when user asks how the system works, what commands are available, or how to use brainstorm/plan/execute phases. Use for "how does this work", "what can you do", "explain workflow", "help me understand", or "show me the process". Do NOT use for actually executing workflows (use workflow-orchestrator) or debugging (use systematic-debugging).
Zero-ceremony inline execution for tasks completable in 3 or fewer file edits. No plan, no subagent, no research — just understand, do, commit, log. Use for "quick fix", "typo fix", "one-line change", "trivial fix", "rename this variable", "update this value", "fix this import". Do NOT use for tasks requiring research, planning, new dependencies, or more than 3 file edits — redirect to /quick instead.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Generate blog post topic ideas through problem mining, gap analysis, and technology expansion. Use when user needs content ideas, wants to brainstorm articles, asks "what should I write about", or needs to fill content gaps. Use for "brainstorm", "topic ideas", "what to write", "content gaps", or "blog ideas". Do NOT use for writing posts, creating outlines, or SEO optimization without a specific ideation need.
Create a new voice profile from writing samples. 7-phase pipeline: Collect, Extract, Pattern, Rule, Generate, Validate, Iterate. Wabi-sabi (natural imperfections as features) is the core principle. Use when creating a new voice, starting voice calibration, or building a voice profile from scratch. Use for "create voice", "new voice", "build voice", "voice from samples", "calibrate voice". Do NOT use for generating content in an existing voice (use voice-orchestrator), editing content (use anti-ai-editor), or comparing voices (use voice-calibrator compare mode).
Defense-in-depth verification before declaring any task complete. Run tests, check build, validate changed files, verify no regressions. Applies 4-level adversarial artifact verification (EXISTS > SUBSTANTIVE > WIRED > DATA FLOWS) with goal-backward framing. Use before saying "done", "fixed", or "complete" on any code change. Use for "verify", "make sure it works", "check before committing", or "validate changes". Do NOT use for debugging (use systematic-debugging) or code review (use systematic-code-review).