Hacker Newsnew | past | comments | ask | show | jobs | submit | comchangs's commentslogin

This is the kind of thing that's completely useless and I absolutely love it. Bookmarked.

The persistent memory at ~/.nanopm/memory/ is clever. Having context survive across sessions is what makes this actually usable vs a one-shot prompt.

We did something similar with deployment presets in our CLI — saving frequently used server/module combinations so you don't re-specify them every time. The "memory layer" pattern seems to be emerging across all dev tooling.


Thanks, agree. Without persistent context, users end up rebuilding state every time. Feels like memory is becoming a core abstraction (like env vars), not just an add-on.

Tried it on a few repos — the file-tier prioritization is a nice touch. Skipping lockfiles and generated code saves a lot of noise.

Would be interesting to see this integrated into CI — auto-generate updated diagrams on each PR so architecture docs never go stale.


Thanks for trying it out! CI integration is definitely on the roadmap. The idea is a GitHub Action that runs the analysis on each PR and comments with an architecture diff showing what changed. Would be great for catching accidental coupling or layer violations before they get merged. Haven't started building it yet but it's on the plan.

Nice. The LLM authoring angle is underappreciated — getting an AI to write valid MJML is painful, but Markdown is trivial.

One thing I'd love: a CLI mode so I can pipe it into deployment notification hooks. Something like `echo "Deploy succeeded" | emailmd | sendmail` would be killer for DevOps workflows.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: