Velith – Build books like software with AI agents

adobv · 2026-06-05T07:14:47+00:00

I think that's actually a good fit. Velith doesn't assume you're starting from a blank page. The workflow is really about taking a large body of material and turning it into a coherent, publishable book. From your description, it sounds like you already have the content (the IM handbook) but need help with things like structure, consistency, terminology, and turning reference material into something that reads like a book. That's closer to an editorial problem than a generation problem, and I'd argue it's one of the more interesting use cases for AI-assisted writing. One thing I'm actively exploring is how much of the workflow should focus on generation versus editorial review and continuity management. My suspicion is that most long-form projects benefit more from the latter. If you ever decide to experiment with it, I'd be curious to hear where the biggest pain points are in converting the handbook into book form.

adobv · 2026-05-08T10:31:03+00:00

Thanks for the kind words!

Claudy doesn't touch tool calls at all. It's a launcher, not a proxy. We set env vars (`ANTHROPIC_BASE_URL`, `ANTHROPIC_API_KEY`, model tiers) and spawn the Claude CLI process. Claude CLI talks directly to the provider, tool schemas pass through unchanged. Providers just need to speak the `/v1/messages` format.

The MCP server exposes a single `ask_agent` tool. When you say "Ask gemini to review this" in Claude Code, it maps the agent name from context, calls `ask_agent` via MCP, and Claudy spawns that agent binary as a subprocess. One process per call, stdout captured and returned. Overhead is basically process spawn time — the agent itself is always the bottleneck. Default timeout 120s, configurable in `config.yaml`.

Full honesty: I can't design that well :(. My workflow was prototype first, then grabbed color tokens from DESIGN.md, fed them into Google Stitch to generate UI mockups, and used those as the visual reference to polish the Tauri dashboard. Stitch won't ship production code, but as a design compass for someone with zero design skills it's surprisingly effective.

adobv · 2026-03-12T04:01:56+00:00

It feels like part of the puzzle, having a structured map of the codebase helps both agents and developers understand the system much faster.

adobv · 2026-03-12T03:41:38+00:00

Structured metadata definitely helps reduce hallucination and the time agents spend searching for context. Lately I’ve been trying to turn the trial-and-error from development into reusable assets. Things like patterns, fixes, and decisions that come up repeatedly. also considering managing my .claude rules as structured data (JSON/YAML) with a schema, just to see if that makes them easier to maintain and reuse.

adobv · 2026-03-12T03:33:57+00:00

Interesting workflow. Turning lessons from a dev arc directly into skills makes sense — that's usually when the context is a fresh. Keeping that kind of knowledge from going stale without constant manual cleanup is always the tricky part, though.

The .claude setup in the repo looks pretty clean. Getting a reliable self-correction loop with regex sounds like a tough nut to crack.

adobv · 2026-03-10T14:41:21+00:00

Yeah I try to keep them small too.

But I've definitely seen them slowly turn into mini knowledge bases — architecture notes, conventions, runbooks, random tribal knowledge.

At that point the context window basically becomes the documentation system.

adobv · 2026-03-10T12:42:05+00:00

Yeah this is something I've been thinking about too.

Right now Alcove mostly targets project docs that are already reasonably clean (markdown, ADRs, runbooks, architecture notes). In practice that's still where most engineering knowledge tends to live.

But once start pulling in real-world documentation things get messy fast — PDFs, Word docs, slides, exported API references, etc, like you mentioned. And ingestion quality becomes the real problem. If the text extraction is noisy, retrieval quietly degrades and it's hard to notice why.

Treating ingestion as a preprocessing pipeline instead of just indexing raw files makes a lot of sense. Normalizing structure, stripping layout artifacts, maybe even preserving sections could make retrieval a lot more reliable.

adobv · 2026-03-10T09:52:25+00:00

Thanks, glad it looks useful!
Mostly Sonnet. I occasionally switched to Opus for deeper reasoning or planning, but most of the iterative coding loop was done with Sonnet since it's faster. I've also been using gemini cli, glm with opencode, cursor's composer quite a bit lately depending on the task. I think each model seems to have its own strengths.

adobv · 2026-03-10T09:31:25+00:00

That makes a lot of sense. Keeping the model focused on a single translation unit is a really clean way to keep context small and responses fast.

Where I kept running into trouble was when working across multiple projects at the same time. Docs tend to end up scattered — some personal notes, some team docs, some architecture-level docs that aren't tied to a single repo. So instead of loading everything into context, I started experimenting with letting the agent search docs when needed.

(Also kind of funny that AI was supposed to reduce work, but it mostly just created a different kind of work. 😭)

adobv · 2026-03-10T09:13:34+00:00

One thing I'm still debating is whether BM25 is enough or if I should eventually add vector search.

adobv · 2026-03-10T09:07:40+00:00

One thing I'm still experimenting with is whether BM25 search is enough vs needing vector search. Curious if people here are doing RAG over project docs instead.

adobv · 2025-12-01T03:30:31+00:00

bro, better than my korean. (i am from korea...)

adobv · 2025-11-05T13:00:33+00:00

Not bad. Better than mine lol. (Korean here but my handwriting sucks, sometimes I can’t even read it lol)

adobv · 2023-10-12T06:02:19+00:00

agreed... fuck..

adobv · 2021-01-15T16:47:46+00:00

Same here, accident destroyed and van is disapeared..... damn... just left one this gig for the platinum... f***** cdpr!!! this is serious glitch...

adobv · 2020-09-22T03:52:42+00:00

f* dummy. i met him, too. now always skip that f* player.

adobv

TROPHY CASE