Feature request: CLI + TUI for browsing prompts and running PageLens from the terminal

[ralyodio]

Hey — love what vibeprompt is doing. The 52-prompt library + 9-step workflow is exactly the curated thing I keep wishing I had bookmarked, and PageLens is a clean audit surface.

The ask: a CLI (and ideally a TUI) so the same workflows are reachable without leaving the terminal. Vibe coders mostly live in terminals — opening a browser to copy a prompt is a real context switch, and not all of us want a paste buffer between us and our AI tool of choice.

Concrete surface I'd find immediately useful:

# Library
vibeprompt browse                          # list categories
vibeprompt browse "Architecture Stack"     # list prompts in a category
vibeprompt search "tdd"                    # full-text search
vibeprompt show <slug>                     # print a prompt to stdout
vibeprompt copy <slug>                     # copy to clipboard (xclip / pbcopy)
vibeprompt show <slug> | claude            # pipe directly into a coding agent

# Workflow
vibeprompt workflow                        # show the 9-step playbook
vibeprompt workflow 3                      # detail on step 3

# PageLens
vibeprompt scan https://example.com        # audit, exit non-zero on findings
vibeprompt scan https://example.com --json # machine-readable for CI

# Articles / awesome
vibeprompt articles                        # list
vibeprompt awesome                         # curated tools

TUI (vibeprompt tui or vibeprompt --interactive):

• Left pane: categories (arrow keys)
• Middle pane: prompts in selected category
• Right pane: prompt body preview
• c to copy, enter to print to stdout on quit, / to search, q to quit
• vibeprompt scan results rendered in a similar split view

Built with Ink (modern React-in-terminal, supports React 19) it's about a weekend's work for the MVP. I've been building similar TUIs for @infernetprotocol and would be happy to take a first crack at this if you'd accept a PR.

Why this is worth doing:

• vibeprompt's data is already file-based (prompt-library/<category>/<slug>.md), so a CLI doesn't need a network round-trip — it can read the same source the site does at build time.
• Distribution: npm install -g vibeprompt and brew install vibeprompt. PageLens-as-a-CLI also slots cleanly into CI (vibeprompt scan ${PR_URL} --threshold 80).
• It widens the surface of who'll use it — terminal-first developers who'd never bookmark a site but happily install a CLI.

Open questions you'd want to weigh in on:

• Naming: vibeprompt or shorter (vibe, vp)?
• Should the CLI run fully offline (bundling the prompt library at install time) or fetch from the live site?
• PageLens-as-CLI: ship as a subcommand of vibeprompt or as a separate pagelens binary?

Happy to discuss before writing any code.

[dotsystemsdevs]

Solid feature request. We're not going to build this ourselves in the immediate roadmap — vibeprompt's current focus is the web-based vibe coding playbook (workflow + prompts library + PageLens auditor) and a CLI/TUI is a separate product surface.

BUT — this would be a great community contribution. Marking as good first issue and help wanted. If you (or anyone) wants to build it:

• A CLI that wraps the /api/audit endpoint for PageLens is straightforward (single fetch + pretty-print)
• Prompts can be loaded directly from prompt-library/ markdown files
• Output the prompt to stdout / clipboard would be the killer UX
• Could even live in a separate repo and just be linked from our README/awesome list

Happy to review a PR, give feedback on architecture decisions, and link it prominently from vibeprompt.tech if someone ships it.

[dotsystemsdevs]

Appreciate the offer, but I'm not commissioning paid work on this. The issue is community OSS — happy to review + link prominently if anyone ships a PR.