journey
Use this skill when the user is new and doesn't know where to start, asks 'what should I do first,' 'what order do I do things in,' 'where do I begin,' 'I have an idea but don't know what's next,' or seems lost among the available skills. Also use when the user asks for a roadmap or overview of the full process from idea to launched product. This is the starting point — it routes users to the right skill for their current stage.
Best use case
journey is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when the user is new and doesn't know where to start, asks 'what should I do first,' 'what order do I do things in,' 'where do I begin,' 'I have an idea but don't know what's next,' or seems lost among the available skills. Also use when the user asks for a roadmap or overview of the full process from idea to launched product. This is the starting point — it routes users to the right skill for their current stage.
Teams using journey should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/journey/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How journey Compares
| Feature / Agent | journey | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when the user is new and doesn't know where to start, asks 'what should I do first,' 'what order do I do things in,' 'where do I begin,' 'I have an idea but don't know what's next,' or seems lost among the available skills. Also use when the user asks for a roadmap or overview of the full process from idea to launched product. This is the starting point — it routes users to the right skill for their current stage.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# The Solo Founder Journey You don't need to know everything. You need to know what to do next. This skill tells you where you are and what skill to use. --- ## Where Are You? Find your current stage. Start there — don't skip ahead. ### Stage 1: "I have an idea" You know a problem exists in your field. You haven't validated whether anyone else cares enough to pay. **Do this:** 1. **translate** — Turn your professional pain into a clear problem statement 2. **validate** — Test whether other people have this pain and will pay to fix it **Time:** 1-2 weeks. **Cost:** $0-200. **Gate:** Do NOT move to Stage 2 until you have signal that real people want this. Signal = email signups, survey responses, or pre-payments. "My friends think it's cool" is not signal. --- ### Stage 2: "I've validated demand — what do I build?" You have evidence people want this. Now you need to decide what the minimum product looks like. **Do this:** 1. **customer-research** — Talk to 10 potential users about their workflow 2. **prioritize** — Decide what to build first (ruthlessly cut scope) 3. **plan** — Write a spec AI tools can execute **Time:** 1-2 weeks. **Gate:** You should have a written spec that describes what the user sees and does, not a list of features. If your spec takes more than 2-4 weeks to build, cut more. --- ### Stage 3: "I'm ready to build" You have a spec. Time to choose your tool and build the thing. **Do this:** 1. **brand-identity-generator** — Set your visual identity so AI tools don't guess 2. **build** — Choose your AI tool (Lovable, Claude Code, Replit, Cursor) and build 3. **database** — Set up your data model and security 4. **secure** — Security checklist before going live 5. **compliance** — If you're in healthcare, finance, education, or another regulated industry **Time:** 2-4 weeks for an MVP. **Gate:** The app works. Happy path is functional. You've tested it yourself. It doesn't need to be perfect — it needs to be usable. --- ### Stage 4: "It works — how do I get it live?" The app works locally or in your dev environment. Time to put it on the internet. **Do this:** 1. **deploy** — Get it live on a custom domain 2. **payments** — Set up Stripe for subscriptions 3. **legal** — Terms of Service, Privacy Policy, business entity 4. **test** — Test the full flow as if you're a new user 5. **monitor** — Set up error tracking and uptime alerts 6. **go-live** — Run the pre-launch checklist before letting anyone in **Time:** 1-2 days for deploy. 1 week for payments + legal. **Gate:** Someone can visit your URL, sign up, use the product, and pay you. **go-live** is your final checkpoint before opening the doors. --- ### Stage 5: "It's live — how do I get users?" Your product is live. Nobody knows about it yet. **Do this:** 1. **landing-page** — Build a landing page that converts 2. **copywriting** — Write copy that speaks your audience's language 3. **launch** — Plan and execute your launch (not just "post on Twitter") 4. **niche-advantage** — If you're building for your own industry, use your network 5. **sales** — Find and reach your first 10-20 customers directly **Time:** 2-4 weeks of active launch effort. **Gate:** You have paying customers (even 5-10) and you're learning from their usage. --- ### Stage 6: "I have early customers — how do I grow?" You have paying customers. Now build the engine. **Do this:** 1. **analytics** — Set up tracking so you know what's working 2. **growth** — Design activation, retention, and referral mechanics 3. **conversion** — Optimize your signup and upgrade flows 4. **email** — Build welcome sequences and lifecycle emails 5. **content** — Start creating content that attracts your audience 6. **seo** — Plan content that ranks and drives organic signups 7. **feedback** — Collect and act on user feedback **Time:** Ongoing. This is the work from now on. --- ### Stage 7: "I'm growing — how do I keep customers?" You're acquiring users. Now make sure they stick. **Do this:** 1. **retention** — Reduce churn and build stickiness 2. **support** — Build self-serve documentation 3. **community** — If you have 100+ active users, consider a community 4. **pricing** — Revisit pricing as you learn what users value 5. **optimize** — Speed, code cleanup, database performance --- ### Stage 8: "I'm established — how do I scale?" You have product-market fit. Revenue is growing. Now scale. **Do this:** 1. **ads** — Paid acquisition once organic is working 2. **hiring** — When to hire vs. keep using AI tools 3. **ai-features** — Add AI-powered features to differentiate 4. **accounting** — Get your books right as revenue grows 5. **finances** — Financial modeling and unit economics --- ## Quick Reference | "I need to..." | Use this skill | |----------------|---------------| | Figure out if my idea is worth building | **translate**, **validate** | | Decide what to build first | **prioritize**, **plan** | | Choose an AI coding tool | **build** | | Set up my database | **database** | | Make it look professional | **brand-identity-generator**, **beautify** | | Get it live on the internet | **deploy** | | Check if I'm ready to launch | **go-live** | | Accept payments | **payments** | | Handle legal stuff | **legal**, **compliance** | | Build a landing page | **landing-page** | | Write marketing copy | **copywriting** | | Plan my launch | **launch** | | Reach my first customers | **sales**, **niche-advantage** | | Set up analytics | **analytics** | | Grow faster | **growth**, **conversion** | | Write emails that convert | **email** | | Create content | **content**, **seo** | | Reduce churn | **retention** | | Handle support | **support** | | Run ads | **ads** | | Hire a developer | **hiring** | | Fix a bug | **debug** | | Something broke in production | **debug**, **monitor** | | Understand my financials | **finances**, **accounting** | | Set pricing | **pricing** | | Make my text sound less AI-generated | **humanize** |
Related Skills
validate
Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders.
ux-design
Use this skill when flows feel clunky, users are confused, navigation needs planning, onboarding needs design, or accessibility needs implementation. Covers information architecture, user flows, interaction patterns, progressive disclosure, and error handling UX.
ui-patterns
Use this skill when the user needs to build a dashboard, settings page, data table, or any page layout. Also use when choosing component libraries, implementing responsive design, dark mode, or handling UI states (loading, empty, error). Covers component selection, page composition, and responsive implementation.
translate
Use this skill when the user is a domain expert (lawyer, doctor, contractor, accountant, etc.) who wants to turn their professional knowledge into a software product. Also use when the user says 'I have an idea for my industry,' 'I know this problem exists,' 'I want to build something for [profession],' or is struggling to describe what they want the software to do. Helps identify which professional pain is worth building for, then translates it into requirements AI tools can execute.
test
Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.
technical-seo
Use this skill to implement technical SEO optimizations in code — meta tags, schema markup, Core Web Vitals, crawlability, robots.txt, sitemaps, and GEO (Generative Engine Optimization) for AI search engines. This is the implementation skill — for strategy see seo, for content writing see seo-content, for auditing see seo-audit.
support
Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring.
social-media
Use this skill when the user needs to grow a social media presence, create content for Twitter/X, LinkedIn, or other platforms, build a founder brand, or use social media as a distribution channel. Covers platform strategy, content frameworks, posting cadence, and audience building for bootstrapped SaaS founders.
seo
Use this skill when the user needs to plan SEO content, do keyword research, build a content calendar, map search intent to page types, or create an internal linking strategy. Also use when the user says 'how do I rank higher,' 'what should I write about for SEO,' 'SEO plan,' 'what keywords should I target,' or 'how to get organic traffic.' This is the strategy and planning skill — for writing content see seo-content, for technical implementation see technical-seo, for auditing see seo-audit.
seo-content
Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.
seo-audit
Audit a codebase for SEO and AI-answer visibility, then produce a prioritized fix-it plan. Use this skill whenever a user says things like "audit my SEO", "check my site for search visibility", "how do I rank better", "optimize for Google", "optimize for AI answers", "SEO review", "GEO audit", "run the SEO agent", or anything about improving organic traffic or search rankings. Also trigger when someone mentions wanting visibility in AI-generated answers (ChatGPT, Gemini, Perplexity, Claude). Works on any web project — static sites, Next.js, Astro, Hugo, WordPress themes, or anything that outputs HTML.
secure
Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.