ComputerConnection/poc

Rapid POC Generator

Build a quick proof of concept for: $ARGUMENTS

---

Philosophy

• Speed over polish - Get something working in minutes
• Validate the core idea - One thing, working
• Throw-away code is fine - This isn't production
• Learn fast, fail fast - Quick feedback loop

---

Phase 1: Clarify the Core (30 seconds)

Answer these before writing any code:

1. What's the ONE thing this POC proves?

   • Not three things. One thing.

2. What does "working" look like?

   • Concrete success criteria
   • "I'll know it works when ___"

3. What's the simplest version?

   • Strip away everything non-essential
   • What's the "hello world" of this idea?

---

Phase 2: Pick the Stack (30 seconds)

Based on Zach's environment and the POC needs:

| POC Type | Recommended Stack | |----------|-------------------| | Web UI | Next.js (already in pc-builder) or Vite + React | | Desktop App | Tauri + React (already in NEXUS) | | API/Backend | Python + FastAPI or Node + Express | | CLI Tool | Python or Node | | AI Integration | Python + Ollama | | Data Processing | Python script | | Hardware/Local | Python or Rust |

Default: Use whatever's already set up in an existing project if possible. Don't create new boilerplate.

---

Phase 3: Scaffold (2-5 minutes)

Directory Structure

~/poc-[name]/
├── README.md          # What this proves, how to run
├── main.[ext]         # Single entry point
├── .gitignore
└── [minimal deps]

README Template

# POC: [Name]

## What This Proves
[One sentence]

## Success Criteria
- [ ] [Concrete checkpoint]

## Run It
\`\`\`bash
[single command to run]
\`\`\`

## Result
[Fill in after testing]

## Next Steps (if it works)
- [ ] [What to build next]

## Killed (if it doesn't work)
- Reason: [why it failed]
- Learning: [what we learned]

---

Phase 4: Build the Core (5-15 minutes)

Rules:

1. No abstractions - Inline everything
2. No error handling - Happy path only
3. No tests - Visual verification
4. No config - Hardcode everything
5. No comments - Code should be obvious
6. Console.log everything - See what's happening

Just make it work.

---

Phase 5: Validate (2 minutes)

Run it. Does it work?

If YES:

• Record result in README
• Decide: expand POC or graduate to real project?
• If graduating, create ORIGINAL_BRIEF.md with learnings

If NO:

• Record why it failed
• Decide: pivot approach or kill the idea?
• Either way, learning captured

---

Phase 6: Decision Point

Ask Zach:

POC Complete: [name]
Result: [worked / didn't work]

Options:
1. Graduate to real project (create in ~/nexus/projects/)
2. Expand POC (add next feature)
3. Pivot (try different approach)
4. Kill (idea doesn't work, move on)

Which one?

---

Anti-Patterns (Don't Do These)

• ❌ "Let me add proper error handling first"
• ❌ "We should set up the project structure properly"
• ❌ "I'll add types to make this cleaner"
• ❌ "Let me refactor this before we continue"
• ❌ "We need tests before we know if this works"

These kill POC momentum. Save them for real projects.

---

Output

1. Scaffold the POC directory
2. Write the minimal code
3. Show how to run it
4. Run it and report result
5. Present decision options