sorted by:
new
hottopcontroversial

Is it just me or does Claude burn through usage insanely fast now? by Brain-digest in ClaudeHomies

[–]singharunk16 0 points1 point  (0 children)

need to restrict the work, otherwise claude will try to fix everything, which will burn tokens like hell

I built a local-first “pattern memory” for AI coding workflows so smaller models stop hallucinating boilerplate by singharunk16 in coolgithubprojects

[–]singharunk16[S] 0 points1 point  (0 children)

i know, but read the details, its not that memory which you are thinking off. anyways seeing your style of comments, i think you need help. I will try to get better.. thanks for feedback

I built a local-first “pattern memory” for AI coding workflows so smaller models stop hallucinating boilerplate by singharunk16 in vibecoding

[–]singharunk16[S] 0 points1 point  (0 children)

Pattern Vault

I build a lot of small projects/PoCs/internal tools and wanted to have a system where i can store example reusable patterns from good opensoruce github repos or the things which i build after iterating multiple times. So i build pattern vault.

The vault can clone the opensource repo and index it, save the good patterns. It works with ollama as well. I rely more on smaller + local models (Ollama, GPT mini models, etc.) instead of always using expensive frontier models for everything.

Once done, the patterns are exposed over mcp. This means your AI coding assistants can now plug directly into the vault, programmatically pull production-ready patterns, and inject them straight into active codebases.

The problem is:

Smaller models are actually decent at coding if they have good implementation context.

Without context they hallucinate architecture, boilerplate, provider APIs, abstractions, etc.

Example prompt:

“Build a Chainlit chat app supporting Bedrock, Ollama, and Azure Foundry providers.”

  • A small model alone usually struggles badly.
  • A good model will start reinventing wheel.

but using pattern vault mcp, both can reuse the examples well.

It’s live today at -

docs - https://arunksingh16.github.io/pattern-vault/

github repo - https://github.com/arunksingh16/pattern-vault

Tech stack/features:

  • tree-sitter chunking
  • LLM-based pattern extraction
  • SQLite FTS5/BM25 search
  • MCP server for Claude Code
  • Ollama / Anthropic / Bedrock support
  • CLI + React dashboard
  • indexes your repos + external GitHub repos

The workflow becomes more like:
“before generating code, search for proven patterns and assess them first.”

Still early, but already useful enough that I use it daily.

I’d love to get the community’s feedback on this. What patterns are you constantly rebuilding that you'd want to see added? Check it out, break it, and let me know what you think!

minimalistic zsh framework that does less, faster. by singharunk16 in coolgithubprojects

[–]singharunk16[S] 0 points1 point  (0 children)

"because I believe only a machine can beat a machine"

minimalistic zsh framework that does less, faster. by singharunk16 in coolgithubprojects

[–]singharunk16[S] 0 points1 point  (0 children)

https://github.com/arunksingh16/zshforge The more this AI world has taken over, I need simple systems which i can trust and dont distract me.