# Input Foundry — AI context

Service: https://typing.mayphus.org
Purpose: build, test, and customize Rime/Yuanshu schemes and keyboard layouts.

## Public workbench

- `/`: choose a supported method/layout, try real browser Rime, and build a package.
- `/api/schemas`: JSON catalog. Each item has `id`, `config`, `slug`, and supported `artifacts`.
- `/typing/engine-package.json?schema=<id>`: exact engine configuration and resources.
- `/typing/keyboard-pages.json?schema=<id>&artifact=<target>`: generated keyboard pages.
- `POST /typing/build`: URL-encoded `artifact=rime` or `artifact=yuanshu`, plus one to eight repeated `schemas=<id>` fields; returns an installable ZIP. Use only targets listed by the catalog. Builds are rate limited. Browser cross-origin builds are rejected.
- `/customize`: compose and download a custom-work brief. This is a local form, not an AI chat or arbitrary custom compiler.
- `/guide`: installation and device-check guidance.

## Custom work with an AI assistant

Open the owner's private `mayphus/input-foundry` repository in your authorized coding workspace. Use its `.agents/skills/customize-input-method/SKILL.md` and `docs/custom-work.md`. Repository access is required for compiler source changes; public users can still use the preset builder and download briefs.

A brief should specify device/app, base schema, requested changes, behavior to preserve and concrete input/output test cases. The assistant edits source, validates dependencies and composition, and delivers a preview plus package. Preview and export use the same renderer. Custom work is not automatically added to the public catalog.

Keep personal dictionaries and unpublished customer work private. Browser typing stays in the browser; no AI service receives it. A successful browser test does not prove installation or native gestures on a phone.
