Loading...
Loading...
What you direct
You are the executive. The system takes your ideas, plans the work, carries it out and checks it, then comes back to you with the decisions that are yours to make.
We run it too
We build everything at ByteDragon with this same system, including this website. We maintain it, upgrade it, and fold in what our community tells us, so what you get is a turn-key virtual company that is yours from your very first day.
What they carry
Building high-quality software is complex. Anyone who has done it knows that. What changes here is that you have an engineering team of specialists who turn your decisions into working software. The complexity is theirs to carry. The vision and the direction stay yours.
And they advise
They also tell you what they know before you commit. A specialist that judges a request risky says so, and brings the reason and an alternative with it. You decide, and the work goes ahead on your call. Judgment is the job you keep.
Your team
Senior Engineering Director sits at the center. Each specialist listed below connects to that center directly.
You, the executive
You bring the idea and make the calls
I'd like to build an application for…
Senior Engineering Director
Plans the work, delegates it, and verifies what comes back
pattern-scout
Finds existing patterns before new code is written
researcher
Gathers external information
architect
Designs the approach
design-specialist
Builds the product surface
graphics-specialist
Authors visual assets
brand-strategist
Owns positioning, copy and growth
implementer
Writes the production code
database-specialist
Owns schema, queries and migrations
deployment-specialist
Ships it to production
test-specialist
Writes and runs the tests
quality-auditor
Reviews for issues
Example decision, yours to make
Go live now, or take another look first?
How it divides
Discovery
Establish what already exists before anything is written.
Design
Decide the shape of the thing, inside and out.
Build
Turn the decided shape into running software.
Assurance
Prove it works, and prove it holds to the standards.
How it runs
01
Read
02
Think
03
Act
04
Check
05
Repeat
Memory: Carried into every session, and added to when something is worth remembering
How you use it
The system lives inside Claude Code, with no separate app to run. You ask for what you want in your own words. The planning, the checking and the record keeping around that work happen without you asking, and anything that needs your decision waits for you. When you want something specific, type a command: a word that starts with a slash.
Every command works typed on its own. Some also take optional details, like the idea you want to talk through, but none of them needs anything extra.
/bootstrap
The place to start in a project, new or existing. The team looks it over, then tells you what it found, including anything that needs attention and any work left unfinished.
/tour
A guided walk through how the system works, pitched at your level. Dig into any part that interests you, and come back any time you want a refresher.
/guide-me
Bring an idea, a new feature or a tricky fix, and it talks the work through with you, a question at a time. Starting something new without knowing what to build it with? It recommends a complete technology stack that fits your budget. Then it turns the work into plans sized to the job, ready to build once you agree.
/audit
Run it before you call your changes finished. It reviews them against the standards, for security and for code quality, runs the tests and checks your project already has if you say yes, and ends with a recommendation: ready, fix first, or talk it over.
/compact-prompt
Long conversations get condensed to free up room. Run this first for a note that tells Claude Code what to keep, so your work in progress carries over.
/field-report
For the moments the system itself trips you up. It writes up what happened, works out, where it can, whether the guidance needs fixing or the team strayed from it, and saves the report on your computer. Emailing it to us is up to you.
Asks first, then remembers
The first time, it asks how you like things explained and keeps your answer. The commands that get you started also offer optional settings, and remember if you say no.
Explained at your level
Everything it tells you is written for the level you chose, from never having written code to expert, and you can change it whenever you like. Only the wording changes. The information, the standards and the work stay the same for everyone.
A plan when the work calls for it
When a mistake would be costly to find or to undo, it writes a plan first and checks with you before any work starts. The plan is saved as a file, so it survives closing Claude Code or a crash, and the work can pick up at the step where it stopped. Everything else goes straight to the right specialist and is still checked.
Big jobs are built in stages
Work too big for a single plan is split into a series of plans, foundations first. Each is checked as it finishes, so an early result can change what comes next, and a problem late in the series leaves the finished plans standing.
Checked before it counts as done
Nothing a specialist hands back counts as done until the work itself has been checked, not just the report about it. Work that would be costly to get wrong also gets a full review from a separate specialist, and anything that review finds is fixed and checked again.
Decisions keep their reasons
When a decision is worth keeping and you agree, the team writes it down with the reasons behind it and the options turned down, so nobody has to argue it all over again.
Standards on every job
Every specialist works to the same engineering standards, from security to testing, without being told. They live in files you can open and read, and your project can add its own.
Postponed fixes come back
Problems you choose to leave for later are written down, and they come back at the next review instead of being forgotten.
Instructions keep up with the code
When a change affects how your software is installed, set up or used, the instructions are updated along with it, and you see every edit first.
The system is installed and running from your first session. The course is how you learn to direct it. Every improvement we make to the system is included at no extra cost, and course sales pay for that work.
