@fro.bot/systematic 3.13.0 → 3.13.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
|
@@ -16,7 +16,14 @@ The `problem_type` determines which **track** applies. Each track has different
|
|
|
16
16
|
| Track | problem_types | Description |
|
|
17
17
|
|-------|--------------|-------------|
|
|
18
18
|
| **Bug** | `build_error`, `test_failure`, `runtime_error`, `performance_issue`, `database_issue`, `security_issue`, `ui_bug`, `integration_issue`, `logic_error` | Defects and failures that were diagnosed and fixed |
|
|
19
|
-
| **Knowledge** | `best_practice`, `documentation_gap`, `workflow_issue`, `developer_experience` | Practices, patterns, workflow improvements, and documentation |
|
|
19
|
+
| **Knowledge** | `best_practice`, `documentation_gap`, `workflow_issue`, `developer_experience`, `architecture_pattern`, `design_pattern`, `tooling_decision`, `convention` | Practices, patterns, workflow improvements, and documentation |
|
|
20
|
+
|
|
21
|
+
Prefer the narrowest applicable value. `best_practice` is the fallback when no narrower knowledge-track value fits.
|
|
22
|
+
|
|
23
|
+
- `architecture_pattern` — structural decisions about how components relate
|
|
24
|
+
- `design_pattern` — reusable solutions to recurring design problems
|
|
25
|
+
- `tooling_decision` — choices about tools, libraries, or build infrastructure
|
|
26
|
+
- `convention` — agreed-upon naming, formatting, or style rules
|
|
20
27
|
|
|
21
28
|
## Required Fields (both tracks)
|
|
22
29
|
|
|
@@ -35,6 +42,8 @@ Required:
|
|
|
35
42
|
|
|
36
43
|
## Knowledge Track Fields
|
|
37
44
|
|
|
45
|
+
Applies to every knowledge-track `problem_type` listed in the Tracks table above.
|
|
46
|
+
|
|
38
47
|
No additional required fields beyond the shared ones. All fields below are optional:
|
|
39
48
|
|
|
40
49
|
- **applies_when**: Conditions or situations where this guidance applies
|
|
@@ -73,6 +82,14 @@ Docs created before the track system may have `symptoms`/`root_cause`/`resolutio
|
|
|
73
82
|
- `workflow_issue` -> `docs/solutions/workflow-issues/`
|
|
74
83
|
- `best_practice` -> `docs/solutions/best-practices/`
|
|
75
84
|
- `documentation_gap` -> `docs/solutions/documentation-gaps/`
|
|
85
|
+
- `architecture_pattern` -> `docs/solutions/best-practices/`
|
|
86
|
+
- `design_pattern` -> `docs/solutions/best-practices/`
|
|
87
|
+
- `tooling_decision` -> `docs/solutions/best-practices/`
|
|
88
|
+
- `convention` -> `docs/solutions/best-practices/`
|
|
89
|
+
|
|
90
|
+
The four narrower knowledge-track types share the `best-practices/` directory rather than each
|
|
91
|
+
getting their own. That matches where such docs are already filed, and avoids single-document
|
|
92
|
+
directories that fragment search.
|
|
76
93
|
|
|
77
94
|
## Validation Rules
|
|
78
95
|
|