Live data from Hacker News

Show HN: SpecMind – AI architecture tool for vibe coding

github.com

11–18 of 18 posts

Re: Show HN: SpecMind – AI architecture tool for vibe coding

#11

Curious how it works with AI tools like Claude or Cursor in practice. Does it stay lightweight?

Integration with AI tools like Claude and Cursor is core to how SpecMind works. It runs as slash commands inside those tools, so you can analyze, design, and implement features directly through your AI coding assistant without any heavy setup. Everything stays lightweight since the logic runs through the CLI, and the AI just triggers those commands.

Re: Show HN: SpecMind – AI architecture tool for vibe coding

#15
post #14

Checked the repo. How hard is it to plug this into an existing project?

It is straightforward. You run npx specmind setup in your project so the slash commands are added, then open your AI assistant and run the /analyze command. The CLI parses the entire codebase with Tree-sitter and generates the system.sm file from what already exists. No code changes or prep work needed.

Re: Show HN: SpecMind – AI architecture tool for vibe coding

#16
post #15
post #14

Checked the repo. How hard is it to plug this into an existing project?

It is straightforward. You run npx specmind setup in your project so the slash commands are added, then open your AI assistant and run the /analyze command. The CLI parses the entire codebase with Tree-sitter and generates the system.sm file from what already exists. No code changes or prep work needed.

Cool! Thank you! Will try it out today.

Re: Show HN: SpecMind – AI architecture tool for vibe coding

#17
As someone who has worked on long-lived enterprise codebases, I can confirm that architecture drift is a silent killer. Having a tool that continuously generates specs and diagrams from actual code is extremely useful. The Mermaid diagrams in plain text are a big plus. Excited to see Go and Rust support.

Re: Show HN: SpecMind – AI architecture tool for vibe coding

#18
post #17

As someone who has worked on long-lived enterprise codebases, I can confirm that architecture drift is a silent killer. Having a tool that continuously generates specs and diagrams from actual code is extremely useful. The Mermaid diagrams in plain text are a big plus. Excited to see Go and Rust support.

Thanks for this. Architecture drift was exactly what pushed me to build it. I wanted a way to keep the system picture accurate without anyone needing to manually update diagrams. Keeping everything in plain text with Mermaid felt like the simplest way to make it fit naturally into long-lived projects. Go and Rust support are high on the list.
Post reply on HN