[verdict][generated prompt][source: claude.ai]
Can I vibecode Claude?
// the value is the network, the data or the infrastructure
A Claude-like UI is trivial; the model, safety/reliability layer, long-context performance, artifacts/projects, and platform distribution are not.
confidence: high
what it is: AI assistant for writing, reasoning, coding, and document work
Buildability index · an editorial game
- Price 20 $/month weight: plus 2
- Time not realistically solo weight: minus 3
- Category ai assistants no weight
- Moat proprietary models · infrastructure scale weight: minus 4
- Confidence high weight: plus 1
- What you lose 6 items weight: minus 3
- Site claude.ai (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Build a chat app using Anthropic API, with document upload, conversation storage, and optional project contexts.
what you need
- Anthropic API key
- hosted app
- file parsing
- storage
- optional vector search
Good no that still points technical readers to usable wrappers.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me a personal chat client on the Anthropic API to replace my Claude Pro
subscription with per-token billing. Requirements:
- A local web app: Node + Express + better-sqlite3, streaming replies over SSE,
a conversation sidebar, Markdown rendering with marked.
- Anthropic API key in .env; model picker with Sonnet as the default and Opus
on demand; system prompt editable and saved per project.
- Projects: a project groups conversations and holds a few reference docs
(plain text or PDF via pdf-parse) prepended as context for every chat inside
it.
- Use prompt caching on the project docs to cut token costs, the API supports
it directly.
- SQLite FTS5 search across all conversations; export any thread to Markdown.
- A cost meter per conversation plus a monthly total from the API usage fields,
so the keep-paying-or-not decision is a number, not a feeling.
- Localhost only, no accounts, no telemetry.
- Out of scope: artifacts, mobile apps, and agent features. If the cost meter
shows heavy use, flat-rate Pro or Max wins; include that comparison logic in
the README.
- README: key setup, a link to current per-token prices, and state that the
model is the product; this wrapper only changes how I pay for it. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- frontier model
- long-context quality
- product surface
- mobile apps
- reliability
- continuous model upgrades
Why people still pay
They pay because the quality sits in the model and product platform, not the wrapper.
moat: Proprietary models Infrastructure scale what a moat is
frontier model/platform
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- Msty (si apre in una nuova scheda) — The desktop core is $0, but the terms limit it to private non-commercial use; paid work needs a license.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- LibreChat (opens in a new tab) — Open-source multi-model AI chat platform for self-hosting API-based assistants. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.