We analyzed 30+ viral dev tools, scored 15 candidates, and found the one with universal pain × instant wow × zero friction — buildable in a single work week.
Across 30+ breakout tools (uv, ruff, textual, gitingest, htop, bat, fzf) the same equation appears. Miss one ingredient and you stall.
peek . works in 5 seconds — no API key, no config, no setup. Heuristics offline. 80% of triers bounce if first success takes longer than 30 seconds.
Rich + Textual beauty. Every output is a screenshot people want to share. Before/after GIF stops scrolling.
peek: 10/10"What does this repo do? Where to start?" — every dev, every week. Onboarding, OSS eval, AI context packing. 30M+ TAM.
peek: 10/10pip install peek — under 10 seconds, pure Python, no Rust, no binary. Zero friction = zero excuse not to try.
Generated from 3 lenses (AI-augmented, DX/Joy, Universal Pain) and scored on Viral × Feasible × TAM × Novelty.
Runners-up become peek features: peek --pack (packit) · peek --find (findit) · peek --explain (wtf) — platform, not just a tool.
~46 hours total, ~1k lines Python, Rich + Textual + AST. Strict P0/P1/P2 — cut P2 ruthlessly.
File walk respecting .gitignore, LOC + language stats, tech stack & entry point detection.
9h · peek scan .AST import extraction, directed graph, centrality + PageRank-lite, heuristic summary, "Start Here" ranking.
10h · peek analyze .Rich static panels + Textual TUI with nav, drill-in, key bindings. The wow day.
10h · peek . ✨--html export, --pack (ranked LLM pack), --find, optional LLM summary, tests & edge cases.
9h · --pack --htmlPyPI publish, README + GIF, GitHub polish, launch posts drafted. Launch next morning.
8h · pip install peek 🚀Every peek output is a shareable screenshot. Every repo is a new demo. That's a viral loop, not a moment.
Peek on django vs requests vs your side project — every map is unique and interesting. Users generate marketing.
"Context engineering" is the 2026 buzzword. Peek's ranking IS context selection — feeds Claude/Cursor the right files.
No beautiful local codebase map exists. Sourcegraph is heavy/enterprise; tree/grep are dumb. First polished tool owns the category.
"Show HN: peek — htop for codebases (understand any repo in 5 seconds)" — Python + beautiful TUI + "I built this for myself" story = front page.
500 stars in 24h → GitHub trending → flywheel. The first 48 hours are everything.
08:00 UTC, Tue–Thu
200–800 ★20-sec demo, pin it
50–200 ★10:00 UTC same day
100–300 ★~500 ★ triggers algo
500–1500 ★PyCoder's Weekly, TLDR
300–800 ★Day 2–3
100–300 ★Conservative with HN front page held 4h: 1,500–3,000 stars week 1 · Without HN: 300–800 → trending in Python → 2k month 1
Everything you need to decide, build, and launch. Read 01 → 05 → 04 → 06 for the critical path (30 min).
Summary, methodology, document map
30+ tools, Python gaps, AI-era pain, distribution
15 ideas scored V×F×T×N, ranked, runners-up as features
Problem, solution, architecture, MVP, repo structure
Standalone thesis — 7 reasons + math + objections
Hour-by-hour, code sketches, EOD checks, scope cuts
Moat, positioning, comparison table
Hour-by-hour HN/Twitter/Reddit/PH checklist + templates
peek tomorrow?Open 04_project_details__peek.md + 06_five_day_build_plan.md Day 1 and start with scanner.py. The best launch day is Tuesday — if you finish Friday, wait until Tuesday 08:00 UTC.