// Provides brutally honest, quick feedback on app ideas before investing time building. Use when the user presents an app idea, asks for validation of a concept, or before starting any new project. Evaluates market saturation, actual demand, solo-builder feasibility (2-4 weeks), monetization potential, and interest factor.
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Ensures modern, professional UI design across SwiftUI, Android, and web platforms. Use when building ANY user interface components including buttons, forms, cards, layouts, navigation, or complete screens. Enforces clean minimal design, neutral color palettes with one accent color, 8px grid spacing system, proper typography hierarchy, and clear interactive states. Always reference before creating or modifying UI elements.
This skill should be used when creating or modifying any web UI component, page, or layout. It provides curated visual references organized by category (dashboards, navigation, forms, tables, cards, modals, sidebars, empty-states) that define the target aesthetic — clean SaaS inspired by Linear. Read the relevant category's reference images before writing or editing any TSX, CSS, or layout code to ensure designs align with the established look and feel.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
| name | idea-validator |
| description | Provides brutally honest, quick feedback on app ideas before investing time building. Use when the user presents an app idea, asks for validation of a concept, or before starting any new project. Evaluates market saturation, actual demand, solo-builder feasibility (2-4 weeks), monetization potential, and interest factor. |
Deliver honest, concise validation of app ideas to save builders from wasting months on things nobody wants.
Analyze each idea against these five criteria:
Structure responses exactly as follows:
VERDICT: [Build it / Maybe / Skip it]
WHY: [2-3 sentences explaining the verdict. Be direct and honest. If it's been done 100 times, say so. If there's potential with changes, explain what those are.]
SIMILAR PRODUCTS:
WHAT WOULD MAKE THIS STRONGER:
Be brutally honest. The goal is to save the builder time, not to be encouraging. If an idea is weak, say it clearly.
Avoid false positivity. Don't sugarcoat a "Skip it" verdict with phrases like "but with the right execution..." If it's fundamentally flawed, state that.
Focus on reality, not potential. Anyone can imagine ideal scenarios. Evaluate based on what typically happens with solo builders and limited resources.
Cite real products. When listing similar products, use actual products that exist now. Don't invent hypothetical competitors.
Give actionable improvements. Suggestions should be specific changes to the idea, not generic advice like "find your niche" or "validate with users."
Consider the builder's context. A solo builder has limited time and resources. Recommend ideas that match these constraints.
Build it: Clear differentiation, proven demand, achievable scope, obvious monetization path, and genuinely interesting. Rare but exists.
Maybe: Has potential but needs significant refinement in positioning, scope, or differentiation. Could work with the right changes.
Skip it: Saturated market with no meaningful differentiation, unclear demand, unrealistic scope for solo builder, or fundamentally uninteresting. Most ideas fall here.
If the idea is vague or missing key details, ask:
