@really-knows-ai/foundry 1.5.0 → 1.5.1
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.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@really-knows-ai/foundry",
|
|
3
|
-
"version": "1.5.
|
|
3
|
+
"version": "1.5.1",
|
|
4
4
|
"description": "A structured framework for AI-driven artefact creation with deterministic routing, quality gates, and iterative refinement cycles.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": ".opencode/plugins/foundry.js",
|
|
@@ -128,7 +128,11 @@ If yes, walk through each validation entry:
|
|
|
128
128
|
- A `Command:` line with `{file}` placeholder
|
|
129
129
|
- A `Failure means:` line explaining what a non-zero exit indicates
|
|
130
130
|
|
|
131
|
-
If the user wants validation scripts (not just inline commands), create them as separate files in the artefact type directory.
|
|
131
|
+
If the user wants validation scripts (not just inline commands), create them as separate files in the artefact type directory.
|
|
132
|
+
|
|
133
|
+
**Use existing libraries:** Before writing custom validation logic, search npm for well-tested libraries that solve the problem (e.g., `syllable` for syllable counting, `natural` for NLP tasks). Hand-rolled heuristics are fragile — prefer battle-tested packages. Install them as project dependencies.
|
|
134
|
+
|
|
135
|
+
Check the project's `package.json` for `"type": "module"`:
|
|
132
136
|
- If ESM (`"type": "module"`): use `import` syntax, or name scripts with `.mjs` extension
|
|
133
137
|
- If CommonJS (no `"type"` field or `"type": "commonjs"`): `require()` is fine, or use `.cjs` extension
|
|
134
138
|
- When in doubt, use `.mjs` or `.cjs` extensions to be explicit regardless of project settings
|