Built By A Developer.
For Developers.

Where the name came from

There's actually a story behind it.

SIMURAI comes from three things that are all true at once, not one clever pun. It's three layers, stacked on purpose.

1. 01 — SIMSIM

   A personal tribute.

   SIMSIM is my father's name. This part isn't a naming exercise — it's how I carry something of his into what I build.

2. 02 — AI

   The technology.

   This whole platform exists to create, organize, share, and master AI Skills. AI isn't a theme here — it's literally part of the name.

3. 03 — Samurai

   The philosophy.

   Discipline. Precision. Craftsmanship. Practice, until it becomes instinct. That's how I want AI skills built — not random prompts, not shortcuts, not just asking AI to handle everything. Learn the skill. Practice the skill. Refine the skill. Master the skill.

My father's legacy, the technology I build with, and the discipline of mastery — that's what gives the name SIMURAI its meaning.

SIMURAI isn't just a name. It's a reminder of where we come from, what we build with, and how we build it.

AI Skills. Mastered.

The code of useful intelligence

Four rules, no exceptions.

1. 01

   Discipline

   A skill isn't done when it works once. It's done when it works the same way every time, under pressure, without babysitting.

2. 02

   Precision

   Vague guidance produces vague output. Every skill here is built from specific, repeatable judgment calls — not generic advice.

3. 03

   Craftsmanship

   Built the way a tool should be built: sharpened through real use, not shipped and forgotten.

4. 04

   Mastery

   Mastery isn't a claim. It's a track record — measured, versioned, and improved on every release.

Bishoy Bishai

Tired of repeating myself.

I'm a software engineer who got tired of re-explaining the same review comments, the same test coverage gaps, and the same architectural tradeoffs to every new AI tool I tried. SIMURAI started as a personal toolkit — skills I built so an AI assistant would work the way I actually work, instead of the way a generic prompt guesses I might work.