@metaobjectsdev/sdk 0.15.15 → 0.15.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,6 +1,9 @@
|
|
|
1
1
|
# Working with MetaObjects in this project
|
|
2
2
|
|
|
3
3
|
> {{stackLine}}
|
|
4
|
+
>
|
|
5
|
+
> Generated by MetaObjects (refresh: `meta init --refresh-docs`). Put project notes in your
|
|
6
|
+
> **root `CLAUDE.md`**, not here — this file is regenerated; see the note at the end before editing it.
|
|
4
7
|
|
|
5
8
|
MetaObjects is a metadata standard: typed metadata in `metaobjects/` is the durable
|
|
6
9
|
spine; generated code is the disposable artifact. Regenerate with `{{codegenCommand}}`.
|
|
@@ -27,6 +30,13 @@ For authoring, codegen, runtime/UI, prompts, verify, or adoption-audit work, use
|
|
|
27
30
|
matching `metaobjects-*` skill — its body links the `references/<lang>.md` fragment
|
|
28
31
|
installed for this project's stack.
|
|
29
32
|
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
+
## Refreshing / customizing this generated context
|
|
34
|
+
This file and the `metaobjects-*` skills are **generated** by MetaObjects for this project's
|
|
35
|
+
stack (plain Markdown, no tools/hooks) — refresh with `meta init --refresh-docs`. Don't hand-edit
|
|
36
|
+
them expecting the edit to survive: a refresh leaves a file you've edited intact and writes the
|
|
37
|
+
new copy to `<path>.new` (only `--force` overwrites in place — never `--force` a file with local
|
|
38
|
+
edits). For project-specific guidance, put it in your **root `CLAUDE.md`** (always-on concerns) or
|
|
39
|
+
copy a skill to a new name (skill-level overrides) — don't edit the generated originals in place.
|
|
40
|
+
|
|
41
|
+
After a refresh, for each `<path>.new`: diff it against `<path>`, **keep the hand-edits and take
|
|
42
|
+
the upstream changes**, write the merged result back to `<path>`, then delete `<path>.new`.
|