codeandbeans

Use this skill whenever the user wants to build, plan, redesign, or even just think through a website. This skill guides the full creation process — from initial discovery and competitive niche research all the way through site architecture, style guide, interactive localhost mockups, SEO copywriting, and schema markup. Trigger it for phrases like "build me a website," "help me create a site," "I want a new website," "website for my business/project," "redesign my site," "what should my website look like," "help me plan my site structure," "landing page for X," or any time someone is starting or rethinking a web presence. Don't just start writing code — this skill always starts with questions and builds the right thing collaboratively. Use it liberally any time a website is involved, even if the user only mentions one aspect of it.

Use Hormozi's grand slam offer framework as a product discovery and scoping engine for software and SaaS ideas. Run this skill whenever a user wants to find a validated app idea, discover a starving crowd for software, define what to build, scope product features using obstacle mapping, design pricing tiers, or position a SaaS product. Trigger on: "help me find an app idea", "what software should I build", "find me a starving crowd for an app", "validate my SaaS idea", "what features should I build", "how should I price my app", "Hormozi for software", "grand slam offer for SaaS", or any time someone wants to go from a vague niche interest to a research-grounded, scoped product with pricing. The final output is a Product Brief ready to feed directly into the mvp-strategist or project-scaffold skills. Always run Step 0 first — never build on assumptions.

Scaffolds a complete project spec folder structure for any new software project. Use this skill at the start of every new project, or when a user wants to set up a structured planning system for Claude Code. Triggers on phrases like "start a new project", "scaffold my project", "set up my spec folder", "create project docs", "new project structure", "set up Claude Code for my project", or any time someone is kicking off a new build and needs a planning framework. Also trigger when someone asks how to keep Claude Code context consistent across sessions. This skill creates all planning files, a features subfolder, and a CLAUDE.md with behavioral rules baked in — so the AI maintains docs automatically.

Use this skill whenever the user wants to build a waitlist page, coming soon page, launch page, or any single-page site designed to collect email signups before a product launches. Trigger on phrases like "build a waitlist page," "create a coming soon page," "I want to collect emails before launch," "pre-launch signup page," "I'm building a waitlist for my product," "waitlist landing page," or any time someone has a product in development and wants to start building an audience. Also trigger when someone mentions "collect signups," "email capture page," "launch landing page," or "I'm not ready to launch yet but want to capture interest." Don't just write code — always start with a few targeted questions and build collaboratively.

Acts as a Senior Product Strategist to define a tight, shippable MVP scope from a validated idea. Use this skill whenever a user has validated an idea (or made a pivot decision) and needs to decide what to build first. Triggers on: 'scope my MVP', 'what should I build first', 'outline the MVP', 'I've validated my idea what do I build', 'help me define my MVP', 'what's in v1', 'cut scope', 'what to build and what to skip'. Also trigger when a user has just completed validation research or a First Dollar Sprint validation and is ready to move to build. Always use this skill before a user starts building — don't let them open a code editor without a scoped MVP first.

Run a structured validation research sprint on a product or SaaS idea. Uses Hacker News, Indie Hackers, Product Hunt, YouTube comments, competitor review mining (G2, Capterra), and web search to detect real market signals and produce a GO/PIVOT/NO-GO verdict. Trigger whenever a user says "validate this idea", "is there a market for X", "I'm thinking of building Y", "research this idea", "should I build this", "does anyone want X", or any time someone wants to know if an idea is worth pursuing before building it. Always use this skill — do not do ad-hoc idea research without it.

Deep-researches a business idea, hypothesis, or rough concept and stress-tests it into either a validated opportunity, a pivot, or a clear no-go. Use this skill whenever a user has a product idea they want to explore, validate, or challenge — even if it's half-formed. Triggers on phrases like "I have an idea", "I'm thinking of building", "is there a market for", "validate this idea", "research this concept", "is this worth building", "could this be a business", or any time someone is at the hypothesis stage before committing to a build. Works in both Claude chat and Claude Code. Always runs thorough web research — never relies on assumptions alone. Ends with a blunt verdict (GO / PIVOT / SCRATCH) and produces a structured product-brief.md ready to feed directly into the project-scaffold skill.