Job Search Runs today
New jobs from LinkedIn's public search, twice a day, scored against your CV.
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.
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 keyEach 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"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 apartA 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 wordsdata.yamlWhat it keeps, with migrationsskills/Prompts on your AI; sealed codetriggers.yamlWhat runs on its ownscreens/How it looks, from the kitapp.yamlWhat it may use, and why# 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.
New jobs from LinkedIn's public search, twice a day, scored against your CV.
Photograph a mahjong hand; it counts every 番 and who pays.
Keeps one short list of the email that needs you, and why.
Tells you when a fare on your route is cheap.
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.”
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.
Each app gets one narrow use you allowed, taken back in one tap.
Settings shows what each app read, fetched and ran, and when.
No internet, no files, and a time limit.
An advert or email is judged, never obeyed; answers must fit a fixed shape.
Your AI's change must use the app's real fields and parts. After three failed tries you're told what failed. Whether it shows what you wanted is yours to judge in the preview.
A screen change can't add a button that runs or writes anything new.
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
templates/engine/web/src/theme.cssweb/src/view.tsxdocs/tend evalThe 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.
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.
Themes and connectors from the community; sharing with family or a group; paid templates with makers paid directly; hosted Tendkit.
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.
Claude today, on your subscription through the claude command or with your own API key. Other models are welcome.
It stays in files on your machine. Only what an app sends to your own AI, and the pages it may read, leave it.
It will be chosen before the repository opens, and stated here. The two official templates are MIT.