u/shinobi_apps

▲ 16 r/CroIT

ai pretplate / pitanje za hrv developere

citam malo na drugim/engleskim subreditima gdje ljudi pisu kako imaju claude 20x pretplate i kako u par promptova dodju do 100%, na 5x claude govore da u jednom promptu dodju do 100%, treci govore da imaju racune za apije po par tisuca eura,

zanima me jedna stvar, vise od hrvatskih developera koji koriste ai za pomoc kod kodiranja/vibekodiranja, kako vi stojite sa potrosnjom?

razlog zasto to pitam je: radio sam prosle godine 2 posla tako da je bilo dosta hard core i tada sam imao 20x, ne sjecam se trenutaka kada bih u 5h prozoru uspio doci do 100%, mozda par puta, kako je doslo ljeto ostavio sam si jedan posao, sada imam 5x i dalje rijesavam sve, dolazim blizu 100% ali pricamo o 5x i to tek nakon cca 3h al u 99% posto slucajeva vec sam gotovo sa zadatkom.

imam par projekata sa zajedno cca 750k-1mil linija cistog koda

koji je to nacin rada gdje u jednom promptu uspjes nabit 100%....i cemu potrosnje tokena od par tisuca $ pogotovo za vibekodiranje saasa?

reddit.com
u/shinobi_apps — 18 hours ago
▲ 6 r/CroIT

Shinobi -> MCP server / "trajno pamćenje" za AI agente (+ plugin sustav, demo unutra)

Početkom godine napravio sam Shinobi -> MCP server koji rješava jedan

problem: AI coding agenti (Claude Code, Cursor, itd.) nemaju pojma

tko su bili jučer. Svaka nova sesija = sve ispočetka. Ako radiš nešto

malo veće (više dana, više uređaja, možda i nekakav tim), to postaje problem ->

agent zaboravi zašto je nešto odlučeno, ponovno pokuša pristup koji je već

propao jučer, i tako stalno u krug.

Shinobi je "shared brain" preko MCP-a: task spine, log odluka, dead endovi, approvals

i project context. Radi lokalno ili remote, tako da

isti "mozak" možeš gađati s laptopa, ili mobitela (s plaže) -> svugdje

vidiš isto stanje projekta, nema nagađanja i previše objašnjavanja, doslovno ga pitaš: gdje smo stali

ili izlistaj stanje, preuzmi projekt/task i kreni.

Zašto ovo nije "još jedan memory MCP":

- Većina memory MCP-ova je key-value spremište ili vector search nad

starim porukama. Shinobi ima strukturu: taskovi, odluke, dead endovi i

approvals su odvojeni entiteti s vlastitom logikom, ne blob teksta.

- Dead-endovi su po meni najbitniji dio: agent prije nego što pokuša neki

glup pristup, provjeri jesu li ga (on ili netko drugi) već

pokušali i zašto nije prošao. To je stvarno ono što štedi vrijeme.

- Ima plugin sustav - možeš dodati vlastite MCP alate koji rade nad

istim projektom/stanjem, bez da diraš Shinobi internals.

Napravio sam i referentni plugin: `shinobi-plugin-fitness` - plugin sa

svojim vlastitim, trajnim stanjem koje preživljava između sesija, uz

jasnu podjelu posla:

- plugin vraća čiste strukturirane podatke (ID treninga, ograničenja,

streakove), nikad tekst.

- LLM je jedini koji "priča" tj pretvara te podatke u rečenice.

Konkretno: 180-dnevna fitness misija koja prati treninge, bol, opremu i

težinu, s pravilima (npr. visoka bol u ramenu automatski

zamijeni "push" dan s "legs/core", bez da LLM to izmišlja). Znači primjer:

na mobitelu krenem sesiju/trening, sutra preko laptopa napišem da me boli rame,

preksutra preko mobitela kad krenem u novi trening on meni radi izmjene jer

zna da me boli rame.

Ovo je primjer korištenja, al realno može bit bilo koji treći plugin,

primjerice asistent, il psihijatar :)

Uglavnom, ova shema mi je za sad odlično radila - s njime sam napisao preko

30+ addona/modula, veće refaktoringe, sec audite i slično.

Naravno, ako radiš one-shot prompt, ovo ti realno ne treba.

Eto, ako nekom zatreba - meni je pomoglo, open source je.

https://preview.redd.it/zdo2lw1j38bh1.png?width=1865&format=png&auto=webp&s=414dd9b5515336d5bea5559662a8f17fcd07be3c

https://github.com/numbererikson/shinobi

reddit.com
u/shinobi_apps — 1 day ago
▲ 26 r/CroIT

Napisao sam PHP framework od nule — drugi put. Zanima me mišljenje.

  1. napisao sam prvi. Taj i dalje radi. 2023. krenuo drugi ispočetka na temlju iskustva prvog. Ovaj drugi je od tada u produkciji i aktivno se razvija.

Osnova: zero runtime dependencies. Nema vendor/ u produkciji, nema Composera na serveru. Sve što ide live — napisao sam sam.

S godinama su se nadodali addoni. Što ima:

  • WAF s per-tenant napadačkom atribucijom i self-tuning pravilima (lažni pozitiv → score automatski pada)
  • Proof-of-Work CAPTCHA bez reCAPTCHA/hCaptcha (zero vendor)
  • APM: N+1 detekcija, slow query profiling, memory leak detektor, frontend error capture
  • Cross-source incident correlator (svakih 5min križa security evente + APM + queue + frontend greške)
  • Statistička detekcija regresija: Mann-Kendall + Cohen's d na 7-dnevnim serijama
  • GDPR: manifesti, DSAR, DataAnonymizer, FieldEncryptor (OIB at-rest), retention jobs
  • NIS2 incident reporting: STIX 2.1 export, attack chain rekonstrukcija, CERT.hr integracija, tabletop mode
  • EU AI Act registar koji skenira codebase via PHP AST i auto-otkriva sve AI sustave
  • Self-healing: CRITICAL log → Telegram alert → GitHub issue → AI napiše PR → operator mergea → auto-deploy → health check → rollback ako ne prođe
  • Self-explaining: ERROR log → AI triage → 3 bullets u Telegramu za 30-60 sekundi, prije nego otvorim log
  • Multi-provider AI routing, 10 task rola svaka s vlastitim provider chain-om (Anthropic → Gemini → Groq failover)
  • Multi-tenant SaaS arhitektura s trial lifecycleom
  • Data table addon (server-side processing — bolji mi je nego AG Grid commercial za naše use-case)

~250k LOC. Solo build.

Razmišljam o releaseu pred kraj 2026. Ne prodajem ništa — zanima me ima li uopće smisla ili je "custom PHP framework" u 2026. kategorija za odmahivanje rukom.

edit: zaboravio sam 0 kod LOC:)

u/shinobi_apps — 4 days ago
▲ 1 r/mcp

I built an MCP server that gives my agent one shared brain across my laptop, phone, and cloud sessions

Two things kept biting me with AI coding agents:

  1. Every new session starts blank. My agent kept re-suggesting libraries and

    approaches I'd already ruled out days earlier — it had no memory we'd been

    there.

  2. I work across a laptop, a desktop, and Claude sessions on my phone. Each one

    was its own island — no shared state between them.

So I built Shinobi — an MCP server that's one shared brain for every agent AND

every device:

- One brain, every device — the default is a single hosted brain behind an HTTP

/mcp endpoint. My laptop, my phone, and any cloud Claude session all read and

write the same store, live. No sync step, no copy that drifts. I rule something

out on the laptop, and the session on my phone already knows.

- Dead ends, searched before you build — every failed approach gets logged, and

the moment an agent plans a similar one it's matched semantically and warned

before it wastes a session. This is the part I use most — I haven't seen

another tool do it.

- Plus: decisions that survive the session, a shared task list every agent

coordinates through, and approvals that push to my phone (the agent blocks

until I tap yes/no, wherever I am).

MIT and free. Runs as the hosted one-brain (Docker + Cloudflare tunnel on a GCP

free tier = $0/mo), or fully local on one box if you'd rather keep everything

offline.

Repo: https://github.com/numbererikson/shinobi

I built it for myself and use it every day to build itself. Genuinely curious

whether the "one brain across every device" thing resonates with anyone else, or

if I'm the only one working this scattered.

u/shinobi_apps — 8 days ago

Limalego – load your Lego sets on your phone

bought 20kg of second-hand LEGO for my kids and needed a way to actually build sets out of one big mixed pile.

the way i work: i first sort everything by the color. then i open the app on my phone and for every set i am building it shows me exactly which parts i need and in which color - so i just grab the right color pile and go. thats the main thing: all my sets loaded on my phone, everything broken down by color and i just crank through it.

theres also camera scan but its only for leftovers like "i have this one weird brick and i have no idea where it goes..." point the phone camera at it and it tells you which set it belongs to.

you dont need to read wall of setup docs, the only thing u need is to create Rebrickable API key (https://rebrickable.com/) takes 10 seconds.

stack: fastAPI+SQLlite, Vite/React front, Rebrikable for the parts data, Brickognize for the optional recognition

its an MVP but i use it even now as i type:) - my kids are at that age where i am basically playing LEGO with them so i made this for myself and incase someone else needs it (if u have similar situation like me, kids at 5 and 10:)), its MIT so do whatever u want with it, forks/PRs welcome.

repo: https://github.com/numbererikson/limalego

no agenda here, nothing to sell, nothing to gain - just putting it out there for the community and for some good time with your kids :) incase you like lego

reddit.com
u/shinobi_apps — 10 days ago