@naswerks/engineering-loop 0.2.1 → 0.4.0
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/.claude-plugin/marketplace.json +2 -6
- package/.claude-plugin/plugin.json +1 -1
- package/CHANGELOG.md +70 -0
- package/README.md +29 -4
- package/package.json +1 -1
- package/references/docs-workflow.md +103 -10
- package/references/engineering-loop.md +27 -2
- package/skills/docs-audit-feature/SKILL.md +24 -20
- package/skills/docs-audit-full/SKILL.md +13 -8
- package/skills/docs-backlog/SKILL.md +6 -3
- package/skills/docs-process/SKILL.md +62 -65
- package/skills/docs-status/SKILL.md +21 -15
- package/skills/docs-write/SKILL.md +9 -6
- package/skills/init/SKILL.md +74 -17
- package/skills/init/scripts/doctor.mjs +73 -11
- package/skills/init/scripts/owned.mjs +96 -0
- package/skills/init/scripts/refresh.mjs +129 -0
- package/skills/spec-child/SKILL.md +1 -1
- package/skills/spec-parent/SKILL.md +20 -9
- package/skills/spec-pipeline/SKILL.md +23 -13
- package/skills/spec-retro/SKILL.md +5 -2
- package/skills/spec-review/SKILL.md +10 -6
- package/skills/spec-seat/SKILL.md +10 -5
- package/templates/docs/_meta/doc-index.md +1 -1
- package/templates/docs/infrastructure/background-work.md +1 -1
- package/templates/docs/infrastructure/realtime-events.md +1 -1
- package/templates/docs/patterns/backend-patterns.md +1 -1
- package/templates/docs/patterns/code-organization.md +1 -1
- package/templates/docs/patterns/codegen.md +1 -1
- package/templates/docs/patterns/design-tokens.md +1 -1
- package/templates/docs/patterns/frontend-patterns.md +1 -1
- package/templates/docs/patterns/long-running-workflows.md +1 -1
- package/templates/docs/patterns/state-management.md +1 -1
- package/templates/docs/patterns/testing.md +1 -1
- package/templates/docs/patterns/ui-style-guide.md +1 -1
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Frontend Patterns
|
|
2
2
|
|
|
3
3
|
> Rules and conventions for the client side of this repository. Last verified {today}.
|
|
4
|
-
<!-- meta: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
4
|
+
<!-- init: write here the machine header docs/_meta/docs-workflow.md § Doc metadata (repository-owned) prescribes, at the word for draft; where that section keeps no date in the blockquote, drop the `Last verified {today}.` above. The loop's own header is the one-line meta comment: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
5
5
|
<!-- naswerks-loop: draft; scanned={files} -->
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
> How multi-stage work is orchestrated in this repository: the stages, per-item progress, exactly-once
|
|
4
4
|
> transitions, and how progress reaches the client. The transport it runs on is
|
|
5
5
|
> [background-work](../infrastructure/background-work.md). Last verified {today}.
|
|
6
|
-
<!-- meta: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
6
|
+
<!-- init: write here the machine header docs/_meta/docs-workflow.md § Doc metadata (repository-owned) prescribes, at the word for draft; where that section keeps no date in the blockquote, drop the `Last verified {today}.` above. The loop's own header is the one-line meta comment: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
7
7
|
<!-- naswerks-loop: draft; scanned={files} -->
|
|
8
8
|
|
|
9
9
|
---
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> The store convention for the client side of this repository: the files per store, how a store is
|
|
4
4
|
> registered, how a component consumes it. Last verified {today}.
|
|
5
|
-
<!-- meta: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
5
|
+
<!-- init: write here the machine header docs/_meta/docs-workflow.md § Doc metadata (repository-owned) prescribes, at the word for draft; where that section keeps no date in the blockquote, drop the `Last verified {today}.` above. The loop's own header is the one-line meta comment: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
6
6
|
<!-- naswerks-loop: draft; scanned={files} -->
|
|
7
7
|
|
|
8
8
|
---
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Testing Patterns
|
|
2
2
|
|
|
3
3
|
> How to write and run tests in this repository — every lane. Last verified {today}.
|
|
4
|
-
<!-- meta: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
4
|
+
<!-- init: write here the machine header docs/_meta/docs-workflow.md § Doc metadata (repository-owned) prescribes, at the word for draft; where that section keeps no date in the blockquote, drop the `Last verified {today}.` above. The loop's own header is the one-line meta comment: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
5
5
|
<!-- naswerks-loop: draft; scanned={files} -->
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> Which class or component to reach for, for which job, and the composition rules that keep screens
|
|
4
4
|
> consistent. The tokens themselves are the authority of [design-tokens](design-tokens.md). Last verified {today}.
|
|
5
|
-
<!-- meta: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
5
|
+
<!-- init: write here the machine header docs/_meta/docs-workflow.md § Doc metadata (repository-owned) prescribes, at the word for draft; where that section keeps no date in the blockquote, drop the `Last verified {today}.` above. The loop's own header is the one-line meta comment: type=pattern; status=draft; verified={today}; lineage=0 -->
|
|
6
6
|
<!-- naswerks-loop: draft; scanned={files} -->
|
|
7
7
|
|
|
8
8
|
---
|