You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 92f067a
Browse filesBrowse the repository at this point in the historyBrowse files
feat(agent-context): working loop first, universal requirements pages, init --dialect
The always-on file meta init scaffolds now opens with the whole loop for the declared
stack: generate (one step per declared server, plus the web client), schema (first
migration, apply-pending, rename and allow flags), requirements, and the verify commands.
It drops from about 19 KB to about 5 KB; the principles move verbatim to
metaobjects-codegen/references/principles.md and the port-sync and upgrade text to
metaobjects-verify/references/upgrading.md. It no longer tells agents to read SKILL.md by
path.
- Requirements reference pages install in every stack (the concern gate observed nodes at
init time, before a new project had any). meta gen and meta verify say when a scaffolded
context lacks them.
- meta gen advises wiring requirementTests() when requirements exist and nothing tests them.
- meta init --dialect sqlite|postgres|mysql|d1, dialect-aware next steps, and a shorter
scaffolded config comment carrying the generator import line.
- migration.md documents --rename-column, --rename-table and --allow.
- Skill trigger evals gain mid-task cases.
- meta gen --list off a terminal is unchanged: its TOON default is parsed by tools and skills.
Copy file name to clipboardExpand all lines: agent-context/README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,11 @@ the slim always-on Markdown (`.metaobjects/AGENTS.md` + `CLAUDE.md`) and the six
6
6
`metaobjects-*` Claude skills (each a universal `SKILL.md` plus the
7
7
`references/<token>.md` fragments matching the project's resolved stack).
8
8
9
-
-`servers/<lang>.meta.json` — per-server install + codegen command (drives the always-on).
10
-
-`templates/always-on.md.mustache` — the slim always-on body (`{{stackLine}}`, `{{codegenCommand}}`).
9
+
-`servers/<lang>.meta.json` — per-server install, codegen command and the always-on's verify step (`verifyStep`).
10
+
-`templates/always-on.md.mustache` — the slim always-on body: a working loop first (`{{stackLine}}`, `{{stackLoops}}`, `{{verifySteps}}`), then the rules. The full principles it shortens live in `metaobjects-codegen/references/principles.md`.
11
+
-`templates/loops/<server>.md`, `templates/loops/client.md` — the generate steps of that loop, one per declared server (and one for a web client), concatenated by the assembler.
-`skills/<skill>/references/<token>.md` — language/framework or concern fragment; installed iff `<token>` is in the stack (`Stack.tokens`; concern tokens are OBSERVED from project state, e.g. `requirements` for a project declaring`requirement.*` nodes — see `SDK`'s `CONCERN_TOKENS`).
13
+
-`skills/<skill>/references/<token>.md` — language/framework fragment; installed iff `<token>` is in the stack (`Stack.tokens`). The requirements pages are universal topic files: they install in every stack, because whether a project declares`requirement.*` nodes changes after `meta init` runs.
13
14
-`skills/<skill>/references/<token>-<topic>.md` — a topic split out of a `<token>.md` fragment; scoped by the same token.
14
15
-`skills/<skill>/references/<topic>.md` — any other name is a universal topic file and installs in every stack; the skill's `SKILL.md` says when to open it.
This project uses MetaObjects (it has .metaobjects/config.json and a metaobjects/ directory of meta.*.json files). Progress so far: you added the Order and OrderLine entities, ran `npx meta gen`, and wired the generated Drizzle tables into the service. The typecheck now fails because the generated OrderLine.ts exports `orderLineInsertSchema` and the service expects `OrderLineInsert` as a named type next to it. Make the generated file export that type on every regen.
This project uses MetaObjects (it has .metaobjects/config.json and a metaobjects/ directory of meta.*.json files). Progress so far: entities are declared, `npx meta gen` writes the Drizzle tables, and the first migration is applied. Next on the task list: the admin service needs a TypeScript map from each entity name to its list of searchable column names, kept in step with the metadata. Nothing in `meta gen --list` emits it. Produce it.
This project uses MetaObjects (it has .metaobjects/config.json and a metaobjects/ directory of meta.*.json files). Progress so far: the Invoice entity is declared, `npx meta gen` wrote Invoice.ts with its Drizzle table and Zod schemas, and the migration is applied. Next: in src/billing/totals.ts, write the function that sums an invoice's lines, applies the customer's discount percentage and rounds to cents.
0 commit comments