Live data from Hacker News

Ask HN: What is your (AI) dev tech stack / workflow?

news.ycombinator.com

31–40 of 187 posts

Re: Ask HN: What is your (AI) dev tech stack / workflow?

#31
Self made TUI that just lists LXC containers.

I have a base container.

"A" to make a new instance.

Pi.dev when I hit enter on any container. Hot swap anthropic enterprise and openai and openrouter as needed.

Every container has the dev env already running for my current projects. Iterate, rarely use vim when needed, spec driven and have llm draft prs for me then I review.

I know the codebase in and out so what I want done is on bypass mode and then I review closer at the draft PR step before marking ready for the team.

Re: Ask HN: What is your (AI) dev tech stack / workflow?

#32

I am using Spec Driven Development approach implemented as a Claude Code plugin since Feb for all mid + size tasks. The idea is to write detailed specs first using agent help doing research and interviewing, decompose the task into smaller subtasks, write detailed spec for each task, implement each task separately. You can restart the session after every step in the workflow and after each subtask implementation sinc…

Similar with a todo.md in the project which outlines work to be done.. this gets combined with developer and/or user documentation which outlines features and how they're expected to work. I'll iterate with the agent on the planning and documentation through several times until the documentation and plan look good. The only gotcha I've had a couple times is I'll have the testing and spec before implementation and som…

One additional benefit that we get from the sddw is that agent drives the spec creation using scenario we put into command/skill. It does the research local/web, it asks operator questions and later confirmations about each block in the spec.

Re: Ask HN: What is your (AI) dev tech stack / workflow?

#34
My setup has settled into three layers. Cursor for code, a persistent-memory agent for async ops (email triage, calendar prep, recurring context), and the Claude API for one-off heavy reasoning.

The persistent layer is the real unlock. Once the agent knows your open threads, recurring contacts, and meeting cadence, the per-session context tax mostly disappears. Most days I'm reviewing the agent's drafts rather than retyping the situation from scratch.

Still working out whether to consolidate providers or keep the layers purpose-separated. Consolidation simplifies billing but tends to optimize for the average use case rather than the one you actually have.

Re: Ask HN: What is your (AI) dev tech stack / workflow?

#38
DeepSeek and Mecha-AI as CLI coding agent for general architecture [1]

Sublime Text and a DeepSeek plugin for file by file cosmetic fixes

Nothing else. With these tools I am building apps like never before in minutes instead of months

[1] https://www.npmjs.com/package/mecha-ai

Re: Ask HN: What is your (AI) dev tech stack / workflow?

#40
post #35

MacOS, Ghostty, Tmux, Neovim, Workmux[1], OpenCode/Claude Code, and lots of markdowns. 1 - https://github.com/raine/workmux

Throw tmux in and this is my exact setup as well. I'm looking into finding ways to orchestrate entire workflows across multiple agents in a harness-agnostic way (locally at first).
Post reply on HN