SYS.01 / PROJECT INTELLIGENCE
Your projectAI’s newest expertise
ProjectSkills analyzes your codebase, architecture and product context to build specialized AI Skills designed specifically for your project.
$npm install -g projectskillsPulls your Skills and Constitution into the repository, so the agent in your editor reads them from disk.
STAGE 01 / 06
RAW PROJECT
Files without meaning
SYS.02 / PRODUCT DEMONSTRATION
Watch a project become expertise
TaskFlow is a sample project. Run the pipeline to see what ProjectSkills builds from it.
TaskFlow is a fictional repository. Every figure below is a fixed sample, replayed at the speed the real pipeline runs — nothing here is being analysed live. Your own project produces its own numbers, its own architecture, and its own Skills.
2 files classified SECRET — excluded from analysis and never sent to any AI provider.
React 19 · 42 components
Express · 18 routes
9 domain services
PostgreSQL · 11 tables
- 01Reading repository
- 02Mapping structure
- 03Detecting technology
- 04Understanding architecture
- 05Mapping dependencies
- 06Building intelligence
- 07Creating constitution
- 08Generating Skills
- 09Reviewing Skills
Runs a fixed sample — 4 seconds, nothing is uploaded.
The other half of a project’s life.
A staged interview that ends in a plan, a file scaffold and an MVP you can start on Monday. Where you have a codebase it reads what the code actually says rather than what you remember about it.
All four end in the same three documents. What differs is where the evidence comes from — and every line of the plan says which, so a greenfield plan reads mostly blue and orange and a plan about your own repository reads mostly green.
- KEEL.MD
The build plan. An MVP slice where every item has a test you can run, a Beta slice that is explicitly not now, and the gaps nobody settled.
- SCAFFOLD.ZIP
Real folders and files with a one-line purpose each. Structure, never working code — and the files you already have are marked as changes, not replacements.
- SESSION.MD
Every stage: what was decided, where it came from, and what was left open. A document you can hand to a colleague.
And one more: a scaffold can become a real ProjectSkills project, which is then analysed, gets a Constitution and gets Skills.
A hosted checkout that takes crypto payments and calls a webhook, for solo founders shipping a first paid product. It exists because the alternative is writing and operating webhook infrastructure before earning a pound.
- Who the first user isSTATED
A solo founder with a working product and no payment flow yet
- The one thing they must be able to doSTATED
Take a payment without writing or operating webhook code
- What is deliberately outSTATED
Subscriptions, invoicing, multi-currency settlement, and any fiat rail. Naming them is what stops them arriving in the MVP.
- What constrains itSTATED
One developer, six weeks, and no appetite for holding customer funds
- The overall shapeINFERRED
A stateless checkout page in front of a ledger, with one signed callback out. Worked out from the constraints rather than stated — check it.
Checkout
INFERREDRenders the payment page and watches one address for one payment
Separate because: Holds no keys and no balances, so a bug here cannot move money — it can only fail to notice it arriving
Ledger
STATEDThe only place a balance changes; every credit has a matching debit
Separate because: Separate from Checkout so a payment can be re-observed without a second credit ever being possible
Callback
INFERREDSigns and delivers one webhook per settled payment, with retries
Separate because: Separate from Ledger because delivery can fail for days without that meaning the payment did
The whole of scope. Every item serves the one job this session named.
- 01
Generate a payment address and a checkout page for an amount
STATEDDONE WHENA GET of the checkout URL shows an address and the exact amount owed
- 02
Credit the ledger once when a payment confirms
STATEDDONE WHENReplaying the same confirmation twice leaves exactly one credit on the ledger
- 03
Deliver one signed webhook per settled payment
INFERREDDONE WHENA receiver that returns 500 four times and then 200 receives the callback exactly once
Explicitly not now. Naming it is what stops it leaking into the MVP.
- 01
Refunds
INFERREDDONE WHENA refunded payment reverses its ledger entry and fires a second callback
- 02
A dashboard showing settled and pending payments
INFERREDDONE WHENEvery payment in the ledger appears with its state and its callback history
Nobody settled these. They are listed because a plan that hides its gaps is worse than a short one.
- Pricing model — asked twice, deferred by the user
- Which chains to support at launch — never settled
- SHAPE ran out of turns with questions still open
Your project is waiting.
Read-only access. Secrets are never read, stored, or sent to any AI provider.