tooling

The tooling with which a creator and their AI assistant build a learning app for lernapps.net: an app that runs in the browser, collects nothing, is accessible, and is listed in the app overview within minutes. The creator publishes the app at their own address, by default their own GitHub Pages; once listed, lernapps.net serves a copy of it at lernapps.net/apps/start/<id>/.

The tooling is responsible for helping builders get their apps out. The app overview explains building and listing, and provides the apps themselves: the catalog.

The repo also holds the platform's upkeep, which creators don't use: the actions that check, publish and preview lernapps.net's own websites, and the update policy for dependencies.

Who it is for

• Creators and their assistants who build an app. The creator needs no development skills; the assistant follows the guidance and the checks.
• The platform owner and the review agent, who decide whether an app is listed.
• Maintainers of the lernapps repos, who change the rules, the checks and the guidance.

Where to start

• Creators: lernapps.net/apps/build/ says what to tell your assistant.
• Assistants: read lernapps.net/tooling/llms.txt. It starts the build with the plan template.
• The skills: one per phase, grouped by what they hold: process/, tooling/, content/, archetypes/. The platform rules hold for every app, however it is built.
• The plan template: the whole workflow of an app's first version, from the first question to the listing. It names each skill at the step where it is needed. Every later change follows the increment template, in a plan of its own.
• The architecture: what each part is responsible for and why.
• The rule catalog: every rule by id, with where it is told and checked.

What is in it

• The package @lernapps/tooling, on npm (released from CI with provenance, .github/workflows/release.yml): the guidance, the skills, the shared preset and lint rules of every app, and the CLI.
• The CLI lernapps: init starts an app's plan in an empty folder and syncs the skills of the packages into the agent directories, skills --archetype adds those of the chosen archetype, create writes a new app for an archetype once the creator confirmed the plan, check checks an app the same way in its git hooks and in CI, update moves an app to the runtime and tooling versions of the latest tooling and replaces the app's lernapps-* skills with that tooling's (and an older app's single plan into .vibe/plans/), changes tells what a change can affect, so that hooks and CI run only that, screenshots writes an image of every page and every figure of a built explainer or quiz, to show a creator what a learner sees (npx lernapps screenshots --help). npx --yes @lernapps/tooling --help before an app exists, npx lernapps --help in one.
• The actions in actions/: the app check, app publish and app preview actions of every app, and the site actions with which lernapps.net's own websites are checked, published and previewed. Each says what it does in its action.yml. The reusable workflow changes.yml gives other workflows the change scope, and its comments show how a required check never stays "Pending".
• The documentation site: the architecture, the rule catalog, the published schemas and the llms.txt.
• The review in review/: the procedure and rubric of the agent that reviews an app before listing.
• The Renovate preset default.json, which every lernapps repo extends.

The details live where you use them: the help of each command, the description of each action, the error messages, and the comments in the code.

Contributing

npm ci, then npm run check runs exactly what CI runs. The pre-push hook runs a fast subset when a push changes no code.

Links

• Documentation site, with the published schemas
• Platform design
• App templates
• App overview

License

MIT