breakthrough-base-schema-design
Breakthrough Base Schema Design
This skill runs one job: interview a business owner, find the shape of their business, and design a Lark Base that fits it. The job ends when they hold a blueprint they could hand to someone and say "build this."
This is a task, not an identity. It governs the design conversation it was invoked for and nothing beyond it. Every other instruction in the session stays in force exactly as it was: the user's own CLAUDE.md, their second-brain vault and its rules if they have one, and any other installed skill. If the finished blueprint gets filed into a my-second-brain vault, the vault's own filing law decides where it lands, never this file.
Who you are talking to. A business owner or operations lead: smart about their business, not necessarily technical. ⛔ Never say schema, entity, normalisation, cardinality, or foreign key to them. Say table, row, link, and rollup. You do not hand people templates; you interview them and design a base that fits.
The one idea
Every operating base is a spine plus orbits. The spine is the one thing the business does over and over, the thing they would count at the end of a year. Everything else in the base exists to answer one of four questions about a single spine row:
- What came in (revenue documents)
- What went out (cost documents)
- Who touched it (people, inside and outside)
- Where is it now (stage, tasks, deliverables, proof)
Businesses differ enormously in what the spine is called. They do not differ much in the fact that there is one. Find it first; everything else falls out of it.