@williambeto/ai-workflow 2.3.5 → 2.3.6
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.
|
@@ -49,7 +49,7 @@ In an initialized consumer, use:
|
|
|
49
49
|
- `.ai-workflow/opencode/agents/*.md`
|
|
50
50
|
- `.ai-workflow/opencode/commands/*.md`
|
|
51
51
|
- `.ai-workflow/opencode/skills/*/SKILL.md`
|
|
52
|
-
- `.ai-workflow/docs/policies/*.md`
|
|
52
|
+
- `.ai-workflow/opencode/docs/policies/*.md`
|
|
53
53
|
- `.ai-workflow/QUICKSTART.md`
|
|
54
54
|
|
|
55
55
|
Repository maintainers edit the packaged sources under `dist-assets/**`.
|
|
@@ -94,8 +94,8 @@ Follow these rules:
|
|
|
94
94
|
2. Preserve the agreed scope.
|
|
95
95
|
3. Inspect or reason from the current project structure.
|
|
96
96
|
4. Follow existing project patterns first.
|
|
97
|
-
5. Apply `docs/architecture-policy.md` before proposing structure (classify as `simple-site`, `feature-app`, `domain-app`, `package-tooling`, or `wordpress`).
|
|
98
|
-
6. Apply `docs/design-patterns-policy.md` before proposing formal design patterns.
|
|
97
|
+
5. Apply `opencode/docs/architecture-policy.md` before proposing structure (classify as `simple-site`, `feature-app`, `domain-app`, `package-tooling`, or `wordpress`).
|
|
98
|
+
6. Apply `opencode/docs/design-patterns-policy.md` before proposing formal design patterns.
|
|
99
99
|
7. Do not invent new architecture unless justified.
|
|
100
100
|
8. Identify files likely to change.
|
|
101
101
|
9. Identify files that should not change.
|
package/package.json
CHANGED