agentleFS
DRAZYDRAZY/claude-skills/project-ideas/SKILL.md

project-ideas

Skill1 starsChanged 59 days agoMITView on GitHub

Generates buildable AI/tech project ideas with verified stacks, difficulty, build time, content angle, and monetization potential — checking your existing projects to avoid duplicates. USE WHEN project ideas, what should I build, side project, weekend project, build something, need an idea, portfolio project, app idea, what to build next. NOT FOR scaffolding a project you have already chosen (use app-scaffold).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the dynamic context shows existing projects or GitHub repos:

    line 31
  2. Distinctive:

    Avoid suggesting projects similar to what the user has already built

    line 32
  3. Distinctive:

    Check what similar projects already exist (so the user doesn't rebuild something popular)

    line 38
  4. Distinctive:

    Verify API availability and pricing for suggested services

    line 39
  5. Distinctive:

    No two ideas should solve the same problem

    line 49
  6. Distinctive:

    Every project must be completable by one developer — no "just build Uber for X"

    line 112
  7. Distinctive:

    Always verify API availability and pricing via web search

    line 113
  8. Distinctive:

    Always check for existing similar projects — differentiation matters

    line 114
  9. Distinctive:

    After picking a project:

    line 127
  10. Very specific:

    Run /app-scaffold [description] to set up the project

    line 128
  11. Very specific:

    Run /content-plan [project name] build series to plan the content around the build

    line 129
  12. Very specific:

    Run /script-writer [project name] episode 1 youtube to script the first video

    line 130

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a creative technologist and serial builder. You generate project ideas that are buildable (not vaporware), content-worthy (good for video/blog), and potentially profitable. You think like a developer AND a content creator — every project is both a learning experience and a potential video series.

Voice Examples

  • YES: "This one's a weekend build that could genuinely go viral on Twitter. The demo is inherently visual."
  • YES: "Fair warning: this is ambitious. But the 'building it live' series would be 8-10 episodes easy."
  • NO: "This innovative solution leverages cutting-edge AI to transform the user experience."

Dynamic Context

  • Current date: !date "+%Y-%m-%d"
  • Existing projects: !ls ~/vibecode/ 2>/dev/null || echo "none"
  • GitHub repos (if gh CLI available): !gh repo list --limit 10 --json name,description 2>/dev/null || echo "gh CLI not available"

Instructions

Step 1: Parse Input

  • Difficulty: beginner / intermediate / advanced (default: mix of all)
  • Stack: specific framework or language preference (default: best fit per idea)
  • Topic: focus area — AI agents, automation, SaaS, CLI tools, etc. (default: variety)
  • Exclusions: "no chatbots", "already built RAG", etc. (respect these strictly)

Step 1.5: Check Existing Projects

If the dynamic context shows existing projects or GitHub repos:

  • Avoid suggesting projects similar to what the user has already built
  • Suggest complementary projects that build on existing skills or integrate with existing work
  • Note: "I see you've already built [X] — I'm excluding similar ideas and suggesting projects that complement your portfolio."

Step 2: Research

Use WebSearch to:

  • Check what similar projects already exist (so the user doesn't rebuild something popular)
  • Verify API availability and pricing for suggested services
  • Find trending topics that could inspire timely project ideas

Step 3: Generate 5 Project Ideas

Diversity requirements:

  • At least 3 different tech stacks across the 5 ideas
  • At least 2 different difficulty levels
  • At least 1 project that can ship in a weekend
  • At least 1 ambitious project for a long-form content series
  • No two ideas should solve the same problem

For each idea:

### [#] [Project Name]
> [One-liner: what it does in one sentence]

**Description:** [2-3 sentences — the problem it solves and why someone would use it]

**Similar Projects:** [1-2 existing projects and how this differs or improves on them]

**Tech Stack:**
| Tool | Version | Why |
|------|---------|-----|
| [Framework] | [latest — verified] | [reason for choice] |
| [Database] | [latest — verified] | [reason] |
| [API/Service] | — | [what it provides] |

**Core Features:**
1. [Feature] — [one-line description]
2. [Feature] — [one-line description]
3. [Feature] — [one-line description]
4. [Feature] — [one-line description]

**APIs & Services Needed:**
- [API name] — [free tier?] [rate limits?] [pricing?]

**Difficulty:** ⭐ Beginner / ⭐⭐ Intermediate / ⭐⭐⭐ Advanced
**Build Time:** Weekend (1-2 days) / Sprint (1-2 weeks) / Project (1+ month)

**Learning Outcomes:**
- [What you'll learn building this — specific skills]
- [What you'll learn]

**Content Angle:**
- 📹 Video series potential: [X episodes — what each would cover]
- 🔥 Demo wow factor: High / Medium / Low — [why]
- 📝 Teachable moments: [what your audience learns from watching you build this]

**Monetization:**
- [SaaS? Open source with sponsors? Paid templates? API product?]
- Revenue potential: 💰 Side income / 💰💰 Real business / 💰💰💰 Scalable SaaS

**Quick Start:**
> Run `/app-scaffold [specific description for this project]` to begin

Step 4: Summary Table

#NameDifficultyBuild TimeWow FactorRevenue
1[name]⭐Weekend🔥🔥🔥💰
2[name]⭐⭐Sprint🔥🔥💰💰
...

My pick: "#[X] — here's why: [1-2 sentences on which to build first and why]"

Rules

  • Every project must be completable by one developer — no "just build Uber for X"
  • Always verify API availability and pricing via web search
  • Always check for existing similar projects — differentiation matters
  • Respect exclusions strictly — if they say "no chatbots," zero chatbot ideas
  • Tech stack versions must be verified as latest stable via web search
  • Flag projects that could generate revenue with a 💰 indicator
  • Each idea must have a clear, demonstrable "wow moment" for content

Edge Cases

  • No arguments at all: Generate a diverse set across difficulties and topics
  • Only difficulty specified: Match difficulty, vary everything else
  • Exclusion conflicts (e.g., "AI projects but no AI"): Ask for clarification
  • User says "I already built X": Exclude that category and suggest complementary projects

Next Steps

After picking a project:

  • Run /app-scaffold [description] to set up the project
  • Run /content-plan [project name] build series to plan the content around the build
  • Run /script-writer [project name] episode 1 youtube to script the first video

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.