TTendkit GitHub
Open source · early days

Apps you tend.

Small apps for your own life. They run on your machine and your own AI, keep your data at home, and change how they look when you ask.

Two apps run every day today: a job hunter and a mahjong scorer. The rest of this page says what's built and what isn't.

templates/job-search/
intent.mdwhat it's for
data.yamljobs, companies, replies
skills/score_job.mda prompt, on your AI
skills/read_cards.jscode, sealed
triggers.yamlsearch at 06:00, 18:00
screens/jobs.yamlhow it looks
app.yamlGmail, read only
Good eveningyour box
JJob SearchBest fit: 82%, Wise10
番fansnapLast night: 6 hands6
You asked“Show the Glassdoor rating next to the match.” Done, on your copy only.
Your AI

It thinks on your subscription

Apps run on the Claude subscription or API key you already have. Nobody else pays for every user's AI, so apps can be free to share.

claude -p on your box, or your own key
Your data

It stays in one file at home

Each app keeps its records in SQLite on your machine. A new version of the app moves them forward, and won't drop any unless you agree.

apps/job_search/data.sqlite
Your look

It changes when you ask

"Show the pay on each job." Your AI rewrites your copy of the screen. Tendkit checks it uses only the app's real parts and data, and adds nothing the app can't already do. You judge the result in a preview with your own data, then keep it or undo it.

overlay/screens/jobs.yaml: your changes, kept apart
How it works

An app is a handful of plain files

A maker writes them once and shares them like a package. Tendkit runs them and holds what needs trust: your sign-ins, your data, and what each app may reach.

intent.mdWhat it's for, in plain words
data.yamlWhat it keeps, with migrations
skills/Prompts on your AI; sealed code
triggers.yamlWhat runs on its own
screens/How it looks, from the kit
app.yamlWhat it may use, and why
See part of Job Search's app.yaml
# templates/job-search/app.yaml (part)
permissions:
  - net:www.linkedin.com
needs:
  google:
    - use: gmail.read
      why: Spot replies from companies you applied to.
      only: {collection: jobs, where: {status: applied},
             field: company, days: 60}

Tendkit builds the Gmail search from your own applied jobs, so the app can narrow what it reads but never widen it. You allow it once, and every use is logged.

Apps

Made for one life, then shared

J

Job Search Runs today

New jobs from LinkedIn's public search, twice a day, scored against your CV.

番

fansnap Runs today

Photograph a mahjong hand; it counts every 番 and who pays.

!

Needs you Designed

Keeps one short list of the email that needs you, and why.

✈

Flight watch Idea

Tells you when a fare on your route is cheap.

Why it's built this way

Small apps, strict rules

The person using it

Makes it look their way

Rows, layouts, tabs, filters and theme, by asking or by hand. Every change is previewed on their own data, with undo. They never see prompts or data models, and their changes are kept apart so the maker's new versions can still reach them.

“Add a tab for jobs that fit 80 or more.”

The maker

Builds it and shares it

Writes what it's for, what it keeps, its skills and screens; checks it with tend validate and tests its skills with tend eval; says what it may use, and why. Tendkit makes sure a user's change can't alter what the app does.

Run it yourself

On a laptop or a small server

You need Python with uv, Node with pnpm, and your own AI: the claude command on your subscription, or an API key.

git clone https://github.com/calemor-group/tendkit
cd tendkit && uv sync
(cd web && pnpm install && pnpm build)
uv run tend models --provider claude-cli
uv run tend install templates/fansnap -a stake_per_point=1
uv run tend serve
Contribute

Where help counts most

  • Make an appbills, school emails, a reading listtemplates/
  • Write a connectorCalendar, Outlook, flight prices; reviewedengine/
  • Design a themetokens for light and darkweb/src/theme.css
  • Improve the kittimeline, calendar and gallery layoutsweb/src/view.tsx
  • Write the makers' guideintents, skills with evals, screensdocs/
  • Try other AIsrun the evals on other modelstend eval
Roadmap

Where it is, and where it's going

Built now

The app format with checks and evals; data with migrations; sealed code; your own AI; schedules, web reading and Google sign-in; the kit in light and dark; change a screen by asking; home, About pages and the editor.

Next

The catalogue, with your look kept through updates; describe an app and your AI drafts it; your corrections kept as tests; the makers' guide; more layouts.

Later

Themes and connectors from the community; sharing with family or a group; paid templates with makers paid directly; hosted Tendkit.

Free, always: the whole of Tendkit on your own machine, with your own AI and data.
Later, optional: hosted Tendkit, so apps keep running while your computer is off, on every device, shared with family, backed up. Not built, no prices set.
Do I need to code?

To use an app and make it look your way, no. To make a new app today, a little YAML and a prompt; making one by describing it is next.

Which AI does it use?

Claude today, on your subscription through the claude command or with your own API key. Other models are welcome.

Does anyone else see my data?

It stays in files on your machine. Only what an app sends to your own AI, and the pages it may read, leave it.

What's the licence?

It will be chosen before the repository opens, and stated here. The two official templates are MIT.