Modules

This page lists every module the kit has, and what each one needs before it is useful. The values come from the module files in app/src/modules/ and the kit's lists in kit/.

All modules

ModuleidBlockViewData fileOrderIconComes with
Taskstasksdatatabletaskapp/data/tasks.json10layersEvery app (starter)
Peoplepeopledatatabletableapp/data/people.json20usersEvery app (starter)
Goalsgoalsdatatablegoalapp/data/goals.json35targetEvery app (starter)
Wikiwikipages—app/wiki/ (the pages)60bookEvery app (starter)
Aboutaboutprofile—app/data/about.md70compassEvery app (starter)

The sidebar lists modules by order, lowest first. About is always last.

What each module needs

ModulePurpose (as Settings shows it)NeedsOn screen you can
TasksWhat you have to do, and when each of it is dueNothing moreAdd, edit, delete and tick rows
PeopleWho you work with, and what to know about each of themNothing moreAdd, edit and delete rows
GoalsWhat you are aiming for this year, and whether each is on trackNothing moreAdd, edit and delete goals
WikiWhat you learn: how your work works, kept as pagesNothing moreRead, search and download pages
AboutWho you are at work: your roleAn interview with ClaudeRead it

Everything that is read-only on screen is written by Claude: you ask, and Claude changes the data file. About is filled only by interviewing you.

How a module arrives

HowModulesWhat you say to Claude
Starter, at setupAbout, Goals, Tasks, People, WikiPart of setting up the app
Your own, on an installed blockAccounts, Projects, or anything else"Add an Accounts module on the datatable block, with these columns: …"

The fields of Tasks, People and Goals

All three are datatable modules, so their rows are defined by fields in the module file. Fields on the first tab (Details) are the table's columns; the Note tab shows in the row's sheet.

Tasks (tasks.json)

KeyLabelKindTabHint
nameNamelineDetails—
categoryTypecategoryDetails—
statusStatusstatusDetails—
personPersonpersonDetailsWhose it is, or who it is waiting on
dueDuedateDetails—
noteNotetextNoteWhat it is, and what it is waiting for

People (people.json)

KeyLabelKindTabHint
nameNamelineDetails—
roleRolelineDetails—
organisationOrganisationlineDetails—
contextHow you know themtextDetailsWhere you met, what you work on together
lastContactLast contactdateDetails—
noteNotestextNoteWorking notes: anything worth knowing before the next meeting

Goals (goals.json, in the goal view, with no tabs)

KeyLabelKindTabHint
nameNameline——
ownerOwnerowner——
startStartnumber—Where it stood at the start of the period
valueValuenumber—Where it stands now
targetTargetnumber——
unitUnitline—%, days, or blank for a count
directionDirectiondirection——
dueTarget dateperiod—A day, a month or a quarter
descriptionDescriptiontext—How it is counted

A goal with a start value shows On track or Off track: it is on track when it is at or ahead of an even pace from start to target over the period of its target date. A goal with no start value shows no badge until it is met or the period ends. See Blocks.

The organisation is plain text for now. Links between tables come later.

Modules you build yourself

Any new module on a block your app already has is one module file and one data file, with no new code. The common first builds:

ModuleBlockViewNeeds
AccountsdatatabletableNothing more. The first build in Learn
ProjectsdatatabletaskNothing more
Models, Experiments, InsightsdatatabletableNothing more

For Sam, an Accounts module is the obvious next step: one row per customer account, such as Tallow & Co and Harbourline Logistics, with the columns they name. The file format is on The module file, and the blocks are on Blocks.

Removing a module

Ask: "Remove the Goals module." Claude runs starta remove goals for a kit module, or deletes the module file for one of your own. The data file stays in app/data/, so nothing you wrote is lost. See Manage modules.