CLI Tools (Beginner-Friendly)
1. File organizer: Sort downloads folder by file type automatically. 2. Git stats CLI: Show commit frequency, top contributors, code churn per file. 3. Markdown link checker: Scan markdown files for broken links. 4. Environment variable manager: Switch between.env profiles for different projects. 5. Code snippet manager: Save and search code snippets from the terminal. CLI tools teach file I/O, argument parsing, and packaging — skills that transfer to any project.
Web Applications (Intermediate)
6. Bookmark manager: Save URLs with tags, full-text search, and reading list. 7. Habit tracker: Daily streaks with GitHub-style contribution graph. 8. Recipe app: Store recipes, generate shopping lists, meal planning. 9. Personal finance dashboard: Track expenses, visualize spending categories. 10. Link shortener: Custom short URLs with click analytics. These projects teach full CRUD, authentication, and database design. Deploy on Vercel or Railway.
SaaS Ideas (Advanced)
11. Status page: Monitor uptime, incident management, subscriber notifications. 12. Feedback widget: Embeddable widget for collecting user feedback on any website. 13. Invoice generator: Create, send, and track invoices with payment integration. 14. Email template builder: Drag-and-drop email builder with HTML export. 15. API monitoring: Health checks, response time tracking, alert notifications. SaaS projects demonstrate business thinking alongside technical skills — invaluable for senior roles and startups.
AI-Powered Projects
16. AI study buddy: Upload notes, ask questions, generate flashcards. 17. Code review bot: GitHub bot that reviews PRs using LLMs. 18. Meeting summarizer: Transcribe and summarize audio recordings. 19. Personal knowledge base: RAG-powered search over your notes and documents. 20. AI writing assistant: Grammar, tone, and style suggestions. AI projects are highly impressive in 2026 portfolios — they show you can integrate modern tools. Learn from our LLM app tutorial.
Open Source Contributions
21. Documentation improvements: Fix typos, add examples, improve readability. 22. Bug fixes: Find "good first issue" labels on GitHub. 23. Feature implementations: Contribute new features to tools you use daily. 24. Create a library: Solve a common problem and publish to npm/PyPI. 25. DevTool extension: Browser extension or VS Code extension. Open source builds your public profile, teaches collaboration, and connects you with the community. See our contribution guide.
How to Choose Your Project
Ask: (1) Does this solve a real problem I have? (2) Can I ship a v1 in 2-4 weeks? (3) Does it teach skills I want to develop? (4) Can I show it to employers? Avoid: projects with unclear scope, technologies you've never touched, and ideas that need thousands of users to be useful. Start small, ship fast, iterate based on feedback. A finished project with 10 users beats a grand vision that never launches.
Tips for Actually Finishing
Set a deadline: 2-4 weeks for v1. Define "done" upfront — what features make it shippable? Use tools you know for the core; experiment with one new technology at most. Deploy early — even a landing page with "coming soon" creates accountability. Tell someone about your project — social pressure helps. Build in public: share progress on Twitter/LinkedIn. Most side projects fail because they never ship. Lower your standards and deploy.