@1aboveio/app-dev-skills 0.1.16 → 0.1.17
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 +2 -2
- package/skills/airflow/SKILL.md +1 -1
- package/skills/android-development/SKILL.md +9 -7
- package/skills/android-development/references/feature-work.md +3 -2
- package/skills/android-development/references/gotchas.md +13 -0
- package/skills/android-development/references/setup.md +8 -5
- package/skills/android-development/references/ui-journeys.md +83 -11
- package/skills/app-debug/SKILL.md +1 -1
- package/skills/better-auth/SKILL.md +1 -1
- package/skills/data-catalog/SKILL.md +1 -1
- package/skills/data-quality/SKILL.md +1 -1
- package/skills/ios-foundation/SKILL.md +1 -1
- package/skills/monorepo/SKILL.md +1 -1
- package/skills/nextjs-fullstack/SKILL.md +1 -1
- package/skills/prisma-setup/SKILL.md +1 -1
- package/skills/pyspark/SKILL.md +1 -1
- package/skills/python-backend/SKILL.md +1 -1
- package/skills/shadcn/SKILL.md +1 -1
- package/skills/zod-v4/SKILL.md +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@1aboveio/app-dev-skills",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.17",
|
|
4
4
|
"description": "Next.js, React Native, auth, Prisma, shadcn, Python backends, Airflow and PySpark.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -27,7 +27,7 @@
|
|
|
27
27
|
"id": "app-dev",
|
|
28
28
|
"core": "@1aboveio/core-skills",
|
|
29
29
|
"coreSkills": [],
|
|
30
|
-
"digest": "
|
|
30
|
+
"digest": "6c6e892cdd7c997eba557667e3a0ac686062485776b1a0a45b7aa5abf8658d16"
|
|
31
31
|
},
|
|
32
32
|
"publishConfig": {
|
|
33
33
|
"registry": "https://registry.npmjs.org/",
|
package/skills/airflow/SKILL.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: airflow
|
|
3
3
|
description: Airflow DAG architecture and conventions. Use when designing, writing, reviewing, testing, or debugging Airflow DAGs and tasks, including TaskGroups, data intervals, timezone-aware date parameters, CLI validation, environment-based scheduling, and pytest integrity tests.
|
|
4
4
|
user-invocable: true
|
|
5
|
-
release-version: 0.48.
|
|
5
|
+
release-version: 0.48.1
|
|
6
6
|
---
|
|
7
7
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
8
8
|
# Airflow DAG Development Patterns
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: android-development
|
|
3
3
|
description: "Prove and debug Expo / React Native apps on an owned Android emulator. Use for Android startup/rendering failures, Metro or ADB problems, UiAutomator/harness failures, APK builds, SDK/NDK/JDK workspace setup, native journey validation, and choosing Kotlin/Compose versus React Native for Android flows. Reproduce failed Android CI checkpoints off CI before fixing and redispatching. Standalone invocation offers Project or Session; init persists repo conventions. NOT for workflow YAML, CI speed or runners (github-actions), browser tests (e2e-test), iOS (ios-foundation), plain Jest tests, or signing/store release."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Android development
|
|
@@ -60,13 +60,15 @@ The contract, other languages and the Maestro/Detox mapping are in
|
|
|
60
60
|
|
|
61
61
|
## UI journey tool
|
|
62
62
|
|
|
63
|
-
The skill references Maestro; it does not bundle or install it.
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
63
|
+
The skill references Maestro; it does not bundle or install it. Offer Maestro for new
|
|
64
|
+
single-device journeys when the repo has no journey tool. Keep an existing sufficient
|
|
65
|
+
harness; adding Maestro needs a concrete benefit and repo authorization, not just an
|
|
66
|
+
installed CLI. Maestro uses the same work loop and validation ladder. Run it on the
|
|
67
|
+
session's own emulator (`maestro --device <serial>`) and convert its output with
|
|
67
68
|
[maestro_failure.py](scripts/maestro_failure.py), which writes the record above. Read
|
|
68
|
-
[UI journeys](references/ui-journeys.md)
|
|
69
|
-
|
|
69
|
+
[UI journeys](references/ui-journeys.md) before selecting or running Maestro flows, for
|
|
70
|
+
starting state, permissions, device ownership, execution evidence and the cases that
|
|
71
|
+
stay custom.
|
|
70
72
|
|
|
71
73
|
## Validation ladder
|
|
72
74
|
|
|
@@ -173,8 +173,9 @@ at L2. Required CI and L3 obligations remain assigned, not silently waived or ma
|
|
|
173
173
|
rule for unreproduced or intermittent failures; report uncertainty until evidence
|
|
174
174
|
supports the cause.
|
|
175
175
|
- Report source SHA, commands, results and remaining gaps at review handoff. For device
|
|
176
|
-
checks, include the selected scenarios, `PASS` markers
|
|
177
|
-
|
|
176
|
+
checks, include the selected scenarios, per-scenario results (`PASS` markers or the
|
|
177
|
+
journey tool's report) and cleanup exit. For a failure, name the earliest failing
|
|
178
|
+
checkpoint and link retained evidence; preserve failed attempts.
|
|
178
179
|
Separate build duration, device-check duration and total worker time when discussing cost.
|
|
179
180
|
Reuse existing logs to distinguish cold/warm builds, build count, ABI, test packaging,
|
|
180
181
|
runtime startup and edit-to-feedback time. Do not infer a task's cost from total job time,
|
|
@@ -20,8 +20,10 @@ the product.
|
|
|
20
20
|
| Backend tool, CI only | a Backend-backed step gets a 5xx in CI only; the log names a missing program (`Browser was not found at the configured executablePath`) |
|
|
21
21
|
| adb transport, mid-journey | `connection terminated: read failed` in the adb trace after boot, then lost `adb reverse`: usually guest RAM |
|
|
22
22
|
| UiAutomator server | `RemoteDisconnected` while the adb transport stays up: the on-device server was relaunched |
|
|
23
|
+
| Maestro driver | driver readiness fails while a setup uiautomator2 process is still alive: see [device ownership](ui-journeys.md#device-ownership) |
|
|
23
24
|
| Journey harness | a wait right after a navigation times out while the destination is on screen |
|
|
24
25
|
| Journey harness, short screen | a wait for a label times out only on a short or landscape screen, which shows the content above it |
|
|
26
|
+
| Journey adapter | an offscreen target stays hidden while scrolls move away from it |
|
|
25
27
|
| Product assertion | a screen or state mismatch with a screenshot |
|
|
26
28
|
|
|
27
29
|
Then match the signal against [gotchas.md](gotchas.md). If nothing
|
|
@@ -143,6 +145,17 @@ matches, [confirm the suspected cause](#confirm-a-suspected-cause) before changi
|
|
|
143
145
|
|
|
144
146
|
## Journey harness
|
|
145
147
|
|
|
148
|
+
### A scroll adapter moves away from the target
|
|
149
|
+
|
|
150
|
+
- **Signal:** a custom comparison adapter times out on an offscreen target even though it
|
|
151
|
+
sends scroll gestures; a fake UI that exposes all targets can still pass.
|
|
152
|
+
- **Cause:** Maestro's requested scroll direction describes the content to reach, not the
|
|
153
|
+
finger movement. Mapping `DOWN` to a downward finger swipe reverses the intended scroll.
|
|
154
|
+
- **Fix:** for `DOWN` toward later content, swipe the finger up; for `UP` toward earlier
|
|
155
|
+
content, swipe the finger down. In the adapter test, keep the target offscreen until the
|
|
156
|
+
correct gesture moves it into view. Wrong-direction gestures must not reveal it merely
|
|
157
|
+
because a gesture count was reached. Check both directions where the adapter supports them.
|
|
158
|
+
|
|
146
159
|
### A navigation check passes on the previous screen
|
|
147
160
|
|
|
148
161
|
- **Signal:** intermittently, a wait right after the next tap times out even though the
|
|
@@ -228,9 +228,11 @@ does not stop that server: use a verified private endpoint on a shared host and
|
|
|
228
228
|
through the caller's owner. Capture the command's exit status, the final summary line and,
|
|
229
229
|
when the journey failed, the `NATIVE_FAILURE` line and its `failure.json`.
|
|
230
230
|
|
|
231
|
-
Expect every selected scenario's `PASS` marker
|
|
232
|
-
|
|
233
|
-
|
|
231
|
+
Expect every selected scenario's result (`PASS` marker or the journey tool's report),
|
|
232
|
+
required screenshots, and backend and Metro logs when the selected variant uses those
|
|
233
|
+
services. For Maestro's result and screenshot rules, read [UI journeys](ui-journeys.md#evidence).
|
|
234
|
+
Preserve the failed checkpoint's evidence before cleanup. A release build with embedded
|
|
235
|
+
assets does not require Metro by default.
|
|
234
236
|
|
|
235
237
|
## Owned development session
|
|
236
238
|
|
|
@@ -385,8 +387,9 @@ For setup proof only. Record:
|
|
|
385
387
|
- Each stage's exit status and duration.
|
|
386
388
|
- The APK's SHA-256 (`shasum -a 256` or `sha256sum`) and its per-ABI `lib/` entries
|
|
387
389
|
(`unzip -l`), checked on the APK itself rather than inferred from Gradle flags.
|
|
388
|
-
- The journey's `PASS` markers
|
|
389
|
-
|
|
390
|
+
- The journey's per-scenario results (`PASS` markers or the journey tool's report) and
|
|
391
|
+
cleanup results: database dropped, emulator exited, container removed, no listeners
|
|
392
|
+
left on the backend or Metro ports.
|
|
390
393
|
- Earlier failed or incomplete attempts. A later pass does not erase them.
|
|
391
394
|
|
|
392
395
|
State what the run does not prove: tablet, accessibility (TalkBack), physical devices,
|
|
@@ -8,47 +8,113 @@ skill references it; it does not bundle or install it, and adding it is the repo
|
|
|
8
8
|
| Situation | Recommendation |
|
|
9
9
|
| --- | --- |
|
|
10
10
|
| Repo has no UI journey tool | Offer Maestro for new single-device journeys. It replaces hand-written adb/UiAutomator launch, poll, capture and assertion code. |
|
|
11
|
-
| Repo has a working harness |
|
|
11
|
+
| Repo has a working harness | Reuse it when sufficient. Add Maestro only for a concrete benefit with repo authorization; an installed CLI alone is not a reason to add or migrate journeys. |
|
|
12
12
|
| Coordinated multi-device case | Keep the custom harness. Maestro sharding runs independent flows, and a shard cannot depend on another. |
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
Maestro changes the UI journey driver, not the [work loop or validation ladder](../SKILL.md#work-loop).
|
|
15
|
+
Use focused flows at the applicable L0/L1 check, candidate-APK journeys at L2, and assigned
|
|
16
|
+
acceptance journeys at L3. Source tests and required backend/native checks keep their roles.
|
|
15
17
|
|
|
16
|
-
|
|
17
|
-
own device:
|
|
18
|
+
## Starting state and permissions
|
|
18
19
|
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
20
|
+
Declare each flow's intended starting app state and permissions in its YAML or owned
|
|
21
|
+
fixture setup, and check included subflows and hooks for resets:
|
|
22
|
+
|
|
23
|
+
- For a warm-runtime check, keep the running app or use `launchApp: {stopApp: false}`
|
|
24
|
+
to foreground it. Plain `launchApp` stops and relaunches the app by default, so it
|
|
25
|
+
cannot preserve the process whose state the check needs.
|
|
26
|
+
- For restart, upgrade or fresh-install checks, use the checkpoint's required setup.
|
|
27
|
+
`clearState: true` and `clearState` clear Android app data; they do not install the
|
|
28
|
+
candidate APK or prove a fresh installation or upgrade. Clear only authorized disposable
|
|
29
|
+
state. If a reset removes debug endpoint preferences, restore them through the existing
|
|
30
|
+
owner and verify the app's actual code source before continuing.
|
|
31
|
+
- Set permissions for permission-sensitive journeys. `launchApp` allows all permissions
|
|
32
|
+
by default; use the required denied or unset state to exercise denial or prompts.
|
|
33
|
+
An auto-granted run does not prove the permission-request journey.
|
|
34
|
+
|
|
35
|
+
## Device ownership
|
|
36
|
+
|
|
37
|
+
Run against the emulator the session owns and name it with `maestro --device <serial>`.
|
|
38
|
+
Use the status handling under [Evidence](#evidence) inside the existing journey owner.
|
|
22
39
|
|
|
23
40
|
Each session installs and starts Maestro's driver packages (`dev.mobile.maestro`,
|
|
24
41
|
`dev.mobile.maestro.test`) through `am instrument`. That cost lands on the session's first
|
|
25
42
|
flow, not on every step, so run every flow of the case in one session instead of one session
|
|
26
43
|
per flow.
|
|
27
44
|
|
|
45
|
+
Keep mutating checks exclusive on that device, including existing harness and Maestro
|
|
46
|
+
runs. Reuse the existing runtime owner; Maestro is not a second emulator, backend or
|
|
47
|
+
cleanup owner.
|
|
48
|
+
|
|
49
|
+
If setup started a `setupUiAutomator` uiautomator2 process, have its owner verify ownership,
|
|
50
|
+
stop it and wait for it to exit before starting Maestro; a live setup driver can block
|
|
51
|
+
Maestro driver readiness. Restart that setup driver only after Maestro has fully exited,
|
|
52
|
+
if it is still needed. Never stop a peer's process; coordinate with its owner instead.
|
|
53
|
+
|
|
54
|
+
When comparing a custom journey adapter with Maestro, check scroll direction and prove
|
|
55
|
+
offscreen targets with the [scroll-direction gotcha](gotchas.md#a-scroll-adapter-moves-away-from-the-target).
|
|
56
|
+
|
|
28
57
|
## Evidence
|
|
29
58
|
|
|
59
|
+
Record the selected flows, executed assertions, run exit status, app/source identity and
|
|
60
|
+
cleanup outcome. Accept the harness's `PASS` markers or Maestro's per-flow results/JUnit
|
|
61
|
+
report as scenario results; a zero exit with no selected flows is not a pass. For JUnit,
|
|
62
|
+
use `--format junit --output <owned-report-path>`; the report is separate from
|
|
63
|
+
`--test-output-dir`. Capture successful checkpoints with `takeScreenshot` when the
|
|
64
|
+
assignment requires visual evidence; normal passing flows have no automatic screenshots.
|
|
65
|
+
|
|
30
66
|
`--test-output-dir` receives one session folder holding one self-contained folder per flow:
|
|
31
67
|
`manifest.json`, `commands.json` (one entry per executed step), the failing step's
|
|
32
68
|
`screenshots/` image and `screen-hierarchy/` JSON, and `logs/device-logcat.txt`. Convert that
|
|
33
69
|
into the [device failure record](diagnosis.md#record-the-failed-device-case) instead of
|
|
34
70
|
adding the journey helper:
|
|
35
71
|
|
|
72
|
+
Give each case/attempt a new owned `LOG_DIR`, shared with its existing launcher so its
|
|
73
|
+
partial-record fallback looks in the same directory. Retain earlier attempts separately;
|
|
74
|
+
reusing a runtime does not mean reusing a failure-record destination. Confirm the pinned
|
|
75
|
+
Maestro supports these flags and output layout before using the example.
|
|
76
|
+
|
|
77
|
+
Run this body as the existing owner's journey command. Guard both commands so `set -e`
|
|
78
|
+
cannot skip conversion or cleanup after a failure. The owner retains its bounded cleanup
|
|
79
|
+
after the journey exits; this is not a new launcher or an acceptance checker.
|
|
80
|
+
|
|
36
81
|
```bash
|
|
37
|
-
|
|
38
|
-
|
|
82
|
+
maestro_status=0
|
|
83
|
+
maestro --device "$ANDROID_SERIAL" test --test-output-dir "$LOG_DIR/maestro" \
|
|
84
|
+
--format junit --output "$LOG_DIR/report.xml" ./maestro-flows || maestro_status=$?
|
|
85
|
+
conversion_status=0
|
|
86
|
+
python3 <skill-base-dir>/scripts/maestro_failure.py --maestro-dir "$LOG_DIR/maestro" \
|
|
87
|
+
--evidence-dir "$LOG_DIR" --case "$DEVICE_CASE" || conversion_status=$?
|
|
88
|
+
printf 'maestro_exit=%s conversion_exit=%s\n' "$maestro_status" "$conversion_status"
|
|
89
|
+
if [ "$maestro_status" -ne 0 ]; then
|
|
90
|
+
exit "$maestro_status"
|
|
91
|
+
fi
|
|
92
|
+
exit "$conversion_status"
|
|
39
93
|
```
|
|
40
94
|
|
|
95
|
+
Convert this invocation's finalized output before teardown. If startup or driver failure
|
|
96
|
+
left no usable failed-step output, retain raw CLI logs and the original status and use
|
|
97
|
+
the existing owner's partial-record fallback before cleanup. Conversion errors are
|
|
98
|
+
evidence-processing failures, not replacements for the original test failure.
|
|
99
|
+
|
|
41
100
|
It takes the session folder or one flow folder, writes `failure.json` into `--evidence-dir`
|
|
42
101
|
(the flow folder by default) and prints the one `NATIVE_FAILURE` line for the first failed
|
|
43
102
|
step. A passing flow writes nothing, and an existing record is never replaced. The artifact
|
|
44
103
|
fields name the Maestro files (`screenshots/…`, `screen-hierarchy/…`, `logs/…`) rather than
|
|
45
104
|
copying them into the adb names, so the failing frame and its hierarchy stay paired.
|
|
46
105
|
|
|
106
|
+
Converter exit zero means processing completed, not that tests passed: a recorded failure
|
|
107
|
+
also returns zero, and empty or incomplete step output may produce no record. Establish
|
|
108
|
+
success from the executed assertions and per-flow results above, never from the converter
|
|
109
|
+
or absence of `NATIVE_FAILURE`.
|
|
110
|
+
|
|
47
111
|
## Agents
|
|
48
112
|
|
|
49
113
|
`maestro mcp` gives an agent `list_devices`, `inspect_screen`, `take_screenshot` and `run`.
|
|
50
|
-
Explore the screen and draft a flow with it
|
|
51
|
-
|
|
114
|
+
Explore the screen and draft a repeatable YAML flow with it. Proof comes from executing
|
|
115
|
+
the flow against the identified candidate with assertions that establish the claimed
|
|
116
|
+
behavior and retained results. Committing YAML or finding selectors in MCP does not prove
|
|
117
|
+
the journey passed.
|
|
52
118
|
|
|
53
119
|
## Limits
|
|
54
120
|
|
|
@@ -56,3 +122,9 @@ MCP session that found the selectors.
|
|
|
56
122
|
on custom harness code.
|
|
57
123
|
- Authentication codes still come from the harness's disposable database, passed into a flow
|
|
58
124
|
with `maestro test -e` or resolved by its `runScript`; do not add a second fixture path.
|
|
125
|
+
|
|
126
|
+
## Sources
|
|
127
|
+
|
|
128
|
+
- [Launch state and permissions](https://docs.maestro.dev/reference/commands-available/launchapp)
|
|
129
|
+
- [Android state clearing](https://docs.maestro.dev/reference/commands-available/clearstate)
|
|
130
|
+
- [Reports and artifacts](https://docs.maestro.dev/maestro-flows/workspace-management/test-reports-and-artifacts)
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: app-debug
|
|
3
3
|
description: "Diagnose runtime failures in deployed Cloud Run services — 5xx/422 errors, tracebacks, Next.js SSR/hydration or Server Action failures, DB/Secret Manager connection errors, cold-start timeouts, container OOM. NOT for build or deploy failures (cloud-debug)."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# App Debug
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: better-auth
|
|
3
3
|
description: "Add or debug Better Auth for Next.js App Router: login, sessions, protected routes, middleware, OAuth (including Feishu/Lark), cookies, Prisma, and Auth.js migration."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Better Auth for Next.js
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: data-catalog
|
|
3
3
|
description: "Column definitions for warehouse tables, written inside the Spark/PySpark or SQL script that builds each table (CATALOG_TABLE / CATALOG_FIELDS, or a `-- @field` comment block), with a generated markdown catalog in docs/catalog/ and a CI check that fails a PR whose catalog is stale. Use when writing or changing a table script that adds, renames, removes, or changes the meaning of an output column or feature; when asked what a warehouse column or feature means; to set a repo up ('init the data catalog', 'generate the data dictionary', '字段字典', 'add catalog CI'); or to audit existing SQL or Spark scripts for undocumented columns. NOT for implementing or tuning the Spark job itself (pyspark), DAG wiring (airflow), or general workflow YAML (github-actions)."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Data catalog
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: data-quality
|
|
3
3
|
description: "Check a published warehouse table's data against its data-catalog definitions with read-only SELECTs: columns never filled or stuck at one value, counts below zero, ratios outside 0–1, declared values that never appear and undeclared values that do. Then classify each finding as a wrong definition, wrong code, or wrong data. Use when asked whether a table's data is right, to profile or sanity-check a dwd/ads table, to find dead or constant columns, to check a column's values against its documented list, after a pipeline change ships, or when a data-catalog definition and the data might disagree. NOT for validating a Spark change before it ships (pyspark canary and reconciliation), writing definitions (data-catalog), or monitoring dashboards."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Data quality
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ios-foundation
|
|
3
3
|
description: "Set up and prove an Expo / React Native native iOS workspace from an assigned or fresh isolated workspace to a manual Login smoke on an owned iOS Simulator: isolated workspace and private caches, Xcode/runtime/CocoaPods preflight, frozen install with `pod install --deployment`, platform-scoped prebuild, an ad-hoc-signed Debug simulator build, a private simulator by exact UDID, Metro on a free port, a disposable PostgreSQL backend with owned cleanup, and the evidence record (setup proof only; feature work reports the smoke result). Use for 'set up iOS', 'build the iOS app', 'run the app on the iOS simulator', 'add iOS to the React Native app', 'prove the iOS build', or when a pod install, xcodebuild, simulator boot, Metro connection or Keychain session fails. NOT for Android (android-development), signing, TestFlight or App Store release, or general workflow YAML (github-actions)."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# iOS foundation
|
package/skills/monorepo/SKILL.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: monorepo
|
|
3
3
|
description: Turborepo architecture for shared packages, pnpm workspaces, DAL boundaries, and pipelines.
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Turborepo Monorepo Architecture
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: nextjs-fullstack
|
|
3
3
|
description: "Build or debug Next.js App Router features with React 19 — pages/layouts/route handlers, Server/Client Components, Server Actions, forms, middleware, DAL, strict TypeScript, Zod — plus our conventions: nuqs URL state, SWR cache, Skeleton/Progress + Sonner feedback, drag-and-drop upload, the portal app shell, list pages as filter/sort/paginate tables. shadcn component mechanics: see the shadcn skill."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Next.js 16 Fullstack Development
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: prisma-setup
|
|
3
3
|
description: Use when adding or debugging Prisma with PostgreSQL, Next.js, or Turborepo, including schema.prisma, prisma.config.ts, client generation, migrations, seeds, relations, adapters, and DAL/database-layer setup. Triggers on phrases like "Prisma schema", "prisma migrate", "schema.prisma", "seed the database", "PrismaClient error", "relation issue", or "database layer".
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Prisma v7 Setup Guide
|
package/skills/pyspark/SKILL.md
CHANGED
|
@@ -12,7 +12,7 @@ description: >
|
|
|
12
12
|
Connect, spark-submit, Hudi commits, backfills, validate-only canaries,
|
|
13
13
|
cluster reconciliation, or Spark event-log profiling — including warehouse
|
|
14
14
|
job timeouts, empty Hudi writes, or EMR/Dataproc performance regressions.
|
|
15
|
-
release-version: 0.48.
|
|
15
|
+
release-version: 0.48.1
|
|
16
16
|
---
|
|
17
17
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
18
18
|
# PySpark
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: python-backend
|
|
3
3
|
description: "Python backend architecture for FastAPI, Tortoise ORM, Pydantic Settings, loguru, and uv. Also: uv.lock installs in CI/Docker via a proxy or mirror (`uv sync --frozen` bypasses it), slow uv installs on runners, relocking."
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Python Backend Conventions
|
package/skills/shadcn/SKILL.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: shadcn
|
|
3
3
|
description: "Add or debug shadcn/ui in a React/Next.js project: components.json, shadcn init/add, presets, registries, Tailwind styling, base/radix/aria composition, component fixes, and list-index pages — where the default is the DiceUI data table with filter/sort/pagination in the URL via nuqs, not a bare shadcn Table."
|
|
4
4
|
allowed-tools: Bash(npx shadcn@latest *), Bash(pnpm dlx shadcn@latest *), Bash(bunx --bun shadcn@latest *)
|
|
5
|
-
release-version: 0.48.
|
|
5
|
+
release-version: 0.48.1
|
|
6
6
|
---
|
|
7
7
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
8
8
|
# shadcn/ui
|
package/skills/zod-v4/SKILL.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: zod-v4
|
|
3
3
|
description: Zod v4 schema conventions and v3 migration for errors, validators, objects, enums, records, and async parsing.
|
|
4
|
-
release-version: 0.48.
|
|
4
|
+
release-version: 0.48.1
|
|
5
5
|
---
|
|
6
6
|
**Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
|
|
7
7
|
# Zod v3 to v4 Migration
|