Start From Open Source

Note: The shortcut: don't build from scratch. Find an open-source project that already does the hard part, fork it, add one meaningful thing, and ship. Here's how to do it without getting burned.

1. Find a project worth forking

• Search GitHub for your idea ("world cup app," "habit tracker," etc.)
• Pick the repo with the most stars — stars mean it works and people actually use it
• Skim the README and run the live demo to confirm it does what you need
• Check it's alive: recent commits, not abandoned

2. Check the license before you commit

• Open the repo's LICENSE file first
• MIT / Apache 2.0 / BSD = permissive: fork, change, and ship freely (with credit)
• GPL / AGPL = copyleft: you may have to open-source your version too — know this going in
• No license = all rights reserved by default. Don't ship it; ask the author or move on
• Check names and logos for trademarks before reusing them (see Don't Get Sued: App Pre-Launch Checklist)

3. Fork it and make it yours

• Fork the repo so you've got your own copy
• Add one meaningful thing — a feature, a reskin — don't just re-upload it
• Paste the GitHub link into your AI and tell it exactly what to build
• Strip trademarked terms, make it mobile-friendly, add your logo, then launch

📄 The exact prompt I used to build The PickPick → The PickPick World Cup — Build Prompts

4. Credit the original — it's the rule, not a courtesy

• Keep the original LICENSE file and copyright notice in your repo
• Credit the author somewhere visible: README, footer, or an about page
• This is the condition that makes your use legal — skip it and you've broken the license

Note: General info, not legal advice. Licenses vary — always read the actual LICENSE file of any repo you use.

The PickPick World Cup — Build Prompts