@pikku/skills 0.12.26 → 0.12.28
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/CHANGELOG.md +41 -0
- package/dist/skills.gen.js +1 -1
- package/package.json +1 -1
- package/skills/pikku-admin-to-fabric/SKILL.md +212 -0
- package/skills/pikku-blueprint-to-fabric/SKILL.md +377 -0
- package/skills/pikku-blueprint-to-fabric/scripts/inventory.mjs +367 -0
- package/skills/pikku-knowledge/SKILL.md +28 -1
- package/skills/pikku-kysely/SKILL.md +107 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,46 @@
|
|
|
1
1
|
# @pikku/skills
|
|
2
2
|
|
|
3
|
+
## 0.12.28
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 591593a: Document `pikku knowledge next` in the `pikku-knowledge` skill: what the six actions mean,
|
|
8
|
+
that `reason` is machine wording never to be repeated to a person, and that `ask-user`
|
|
9
|
+
carries a separate `question` whose empty `options` list means offer free text rather than
|
|
10
|
+
invent choices.
|
|
11
|
+
- 591593a: Document the two frontmatter keys a driving loop writes, in `pikku-knowledge`.
|
|
12
|
+
|
|
13
|
+
`statusAt:` and `attempts:` are bookkeeping rather than content, and an agent
|
|
14
|
+
that rewrites a note has to know not to hand-edit them — clearing `attempts:`
|
|
15
|
+
hands back a budget that exists to stop a note nothing can satisfy being
|
|
16
|
+
rewritten forever.
|
|
17
|
+
|
|
18
|
+
Also corrects the status vocabulary: it is `designing` → `proposed` →
|
|
19
|
+
`dispatched` → `built`. The skill said `proposed` → `dispatched` → `built`,
|
|
20
|
+
"nothing else", while `validate` has always accepted `designing`.
|
|
21
|
+
|
|
22
|
+
- f5a8ee4: Teach `pikku-kysely` to count round trips.
|
|
23
|
+
|
|
24
|
+
The skill documented the query builder API but said nothing about how many times
|
|
25
|
+
a function body crosses the wire, so generated functions routinely awaited four
|
|
26
|
+
or five queries in series — invisible locally, a stacked latency in a deployed
|
|
27
|
+
stage. Adds the four shapes that collapse: independent reads into `Promise.all`,
|
|
28
|
+
parent-then-children into the `jsonArrayFrom` helpers already documented below
|
|
29
|
+
it, read-then-write into one `returning()`/`onConflict` statement that also
|
|
30
|
+
closes the race, and a read that only feeds the next `where` into a subquery or
|
|
31
|
+
CTE. Plus the correction that a transaction adds round trips rather than
|
|
32
|
+
removing them.
|
|
33
|
+
|
|
34
|
+
## 0.12.27
|
|
35
|
+
|
|
36
|
+
### Patch Changes
|
|
37
|
+
|
|
38
|
+
- 28f39f2: Add the `pikku-blueprint-to-fabric` and `pikku-admin-to-fabric` skills, which rebuild a legacy app (and its generated back-office admin) as a Fabric app from a `.knowledge/` Product Blueprint.
|
|
39
|
+
|
|
40
|
+
Both skills were written against an older corpus, so every cross-reference is repointed at the skill that owns the material today: `pikku-queue`/`pikku-cron`/`pikku-http` to `pikku-wiring`, `pikku-better-auth` to `pikku-auth`, `pikku-react-query` to `pikku-react`, `pikku-feature` to `pikku-build`. Four steps named skills that no longer exist at all and are rewritten rather than repointed — the post-clone cleanup, the AOP verification loop, versioning, and the Stage 9 parity check. The stale `wireVariable`/`wireSecret` names are corrected to `defineVariable`/`defineSecret`.
|
|
41
|
+
|
|
42
|
+
`scripts/inventory.mjs` now exits non-zero with the reason when the blueprint directory is missing, a required file is absent, a file is unparseable, or an expected array has the wrong shape. It previously swallowed all of those and printed a table of zeros, which reads as a small app rather than an unusable blueprint.
|
|
43
|
+
|
|
3
44
|
## 0.12.26
|
|
4
45
|
|
|
5
46
|
### Patch Changes
|