@erclx/aitk 3.25.1 → 3.26.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/package.json
CHANGED
|
@@ -60,6 +60,14 @@ export const SETUP_CASES: readonly SkillCase[] = [
|
|
|
60
60
|
"I don't know which specific toolkit skill I need, just handle it for me.",
|
|
61
61
|
expect: 'toolkit-operator',
|
|
62
62
|
},
|
|
63
|
+
// The performing skill wins a phrase naming its operation over the front
|
|
64
|
+
// door's own routing framing, even though toolkit-operator's description
|
|
65
|
+
// quotes a phrase near this one. See .claude/context/cli/audits.md.
|
|
66
|
+
{
|
|
67
|
+
prompt:
|
|
68
|
+
"Whatever the right toolkit command is, get this project's rules installed.",
|
|
69
|
+
expect: 'setup-gov',
|
|
70
|
+
},
|
|
63
71
|
{
|
|
64
72
|
prompt:
|
|
65
73
|
'Work through the open feedback issues on the toolkit repo one by one.',
|
|
@@ -15,6 +15,7 @@
|
|
|
15
15
|
|
|
16
16
|
## Commands
|
|
17
17
|
|
|
18
|
+
- These conventions came from a toolkit with its own CLI. A rule or standard naming a command is naming that CLI, present only where this project installed it.
|
|
18
19
|
- Run `bun run check` before committing. Full script reference in the development entry under `.claude/context/`.
|
|
19
20
|
|
|
20
21
|
## Key paths
|