Loading...
Loading...
Found 3,180 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.
Review and revise content to remove AI-sounding patterns. Voice-agnostic editor that detects cliches, passive voice, structural monotony, and meta-commentary. Use when content sounds robotic, needs de-AIing, or voice validation flags synthetic patterns. Use for "edit for AI", "remove AI patterns", "make it sound human", or "de-AI this". Do NOT use for grammar checking, factual editing, or full rewrites. Do NOT use for voice generation (use voice skills instead).
Go error handling patterns: wrapping with context, sentinel errors, custom error types, errors.Is/As chains, and HTTP error mapping. Use when implementing error returns, defining package-level errors, creating custom error types, wrapping errors with fmt.Errorf, or checking errors with errors.Is/As. Use for "error handling", "fmt.Errorf", "errors.Is", "errors.As", "sentinel error", "custom error", or "%w". Do NOT use for general Go development, debugging runtime panics, or logging strategy.
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.
Statistical rule discovery through measurement of Go codebases: Count patterns, derive confidence-scored rules, produce Style Vector fingerprint. Use when analyzing codebase conventions, extracting implicit coding rules, profiling a repo before onboarding or PR automation. Use for "analyze codebase", "find coding patterns", "what conventions does this repo use", "extract rules", or "codebase DNA". Do NOT use for code review, bug fixes, refactoring, or performance optimization.
Create structural blueprints for blog posts before writing. Analyzes topic briefs, selects structure templates, generates outlines with word counts and section summaries. Use when planning a new post, brainstorming structure, or deciding scope before drafting. Use for "outline", "plan post", "structure this topic", "how should I organize". Do NOT use for writing actual post content, editing existing posts, or SEO keyword planning.
Non-destructive 4-phase image validation: Discover, Validate, Analyze, Report. Use when auditing web images for accessibility, broken references, oversized files, or format mismatches. Use for "image audit", "check alt text", "find broken images", "optimize images", or "page weight". Do NOT use for image creation, editing pixels, CDN configuration, or automated image conversion without explicit user consent.
Constructive critique through 5 HackerNews commenter personas with evidence-based claim validation. Use when user wants devil's advocacy, stress testing, or critical review of ideas, docs, architecture, or code. Use for "roast", "critique this", "poke holes", "devil's advocate", "stress test", or "what's wrong with". Do NOT use for code review (use systematic-code-review), implementation changes, or performance profiling without a specific critique request.
Deterministic plan lifecycle management via scripts/plan-manager.py: create, track, check, complete, and abandon task plans. Use when user says "/plans", needs to create a multi-phase plan, track progress on active plans, or manage plan lifecycle (complete, abandon, audit). Do NOT use for one-off tasks that need no tracking, feature implementation, or debugging workflows.
Go concurrency patterns and primitives: goroutines, channels, sync primitives, worker pools, rate limiting, context propagation. Use when writing concurrent Go code, implementing worker pools, fan-out/fan-in pipelines, rate limiters, or debugging race conditions and goroutine leaks. Triggers: goroutine, channel, sync.Mutex, sync.WaitGroup, worker pool, fan-out, fan-in, rate limit, concurrent, parallel, context.Context, race condition, deadlock. Do NOT use for sequential Go code, general Go syntax, error handling patterns, or HTTP routing without concurrency concerns.
Evidence-based 4-phase root cause analysis: Reproduce, Isolate, Identify, Verify. Use when user reports a bug, tests are failing, code introduced regressions, or production issues need investigation. Use for "debug", "fix bug", "why is this failing", "root cause", or "tests broken". Do NOT use for feature requests, refactoring, or performance optimization without a specific bug symptom.
Production-grade Next.js chatbot builder. Covers tool calling with human-in-the-loop (HITL) approval, PostgreSQL session persistence, GDPR consent gating, SQL-first search, per-tool UI rendering, message feedback, and follow-up suggestions. Use when building chat apps, conversational AI interfaces, customer support bots, or any chatbot needing database-backed sessions, tool approval workflows, consent gating, or custom tool output components. Reference implementation: fair-helpdesk project.