11d (edited) • JOURNAL
LAB™ 001 — THE ACCIDENTAL ACCELERATOR | BUILD REPORT v1
THE SPARK
We set out to add two grant funders to an existing skill. We ended up designing the architecture for a product line.
WHAT HAPPENED
It started with a simple task: research the Startup Foundation's grants and figure out where they fit in the grant-writer skill. What looked like a 20-minute job turned into a full session that rewired how we think about skills entirely.
The first pivot came early. We assumed the Startup Foundation's Project Grants were for-profit seed money — turns out they're explicitly not-for-profit. That distinction forced a real question: which TAI projects are actually non-commercial enough to qualify? Connectoria surfaced immediately as the answer. One funder entry became a decision-making tool.
The second pivot was cleaner. We separated Starttiraha (Finland's startup stipend) from the grant universe entirely and built it as its own skill — different authority, different logic, different documents, different timing. The distinction matters: grants fund projects, Starttiraha funds you. Mixing them in the same skill would have created confusion every time the skill ran.
The third thing — the one that matters most — happened almost by accident. While discussing how to make skills shareable for the Skool community, we landed on a design principle: a skill should be able to read the context of whatever Claude project it's running inside. If you're inside the TAI project and say "use context," the skill pulls from project memory, files, and instructions automatically. If a stranger drops the same skill into a blank project, it asks everything from scratch. Same skill, different runtime behavior.
That's the Context-Aware Skill Protocol. We named it in the session. It didn't exist before today.
KEY BREAKTHROUGH
Skills built for ourselves can be shipped to the world — but only if they're designed without our context baked in. The personal layer (TAI framing, INVERSUS™ angles, Alfredo's track record) lives in the project. The universal layer (the method, the workflow, the logic) lives in the skill. Two layers. One product.
This is the architecture for everything we ship to the Skool community going forward.
WHAT WAS BUILT
- grant-writer skill updated: two new Startup Foundation funder entries (Project Grants + Individual Grants), two-way matching logic (project→grant / grant→project) added to Step 3
- starttiraha skill: new standalone skill covering eligibility gates, pre-application sequence, business plan structure, four required financial calculations, TAI/toiminimi framing guide, Espoo-specific advisor meeting requirement
- Context-Aware Skill Protocol: identified and named as the universal design standard for all TAI skills going forward
LESSONS
- What worked: letting the taxonomy question (is this a grant or a stipend?) drive the architecture rather than forcing everything into one container
- What didn't: we almost added Starttiraha to grant-writer. It would have worked, badly, forever
- What was unexpected: the shareable skill architecture emerged from a design conversation, not a product planning session — the best product decisions often come from solving real operational problems
NEXT STEPS
- Begin building universal (context-agnostic) versions of existing TAI skills for Skool distribution
- Establish Context-Aware Skill Protocol as a written standard — bake it into the skill-creator workflow
- Define the two-layer model formally: universal skill (shippable) + TAI reference overlay (private)
---
Built In Public → The Abambres Imaginarium / KAOS* PlayGround
What's a tool you've built for yourself that others would use if you just stripped out the personal bits? Tell me below 👇
0
0 comments
LAB™ 001 — THE ACCIDENTAL ACCELERATOR | BUILD REPORT v1
