agentic-mobile-kit 0.7.1 → 0.7.3
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/README.md +2 -0
- package/package.json +1 -1
- package/stacks/react-native/template/.agents/skills/m-change/SKILL.md +48 -0
- package/stacks/react-native/template/.agents/skills/m-explore/SKILL.md +1 -1
- package/stacks/react-native/template/.agents/skills/m-feature/SKILL.md +5 -3
- package/stacks/react-native/template/.agents/skills/m-prototype/SKILL.md +54 -0
package/README.md
CHANGED
|
@@ -28,7 +28,9 @@ Each choice prints the command it runs, for scripts and CI: `init` (with `--ci g
|
|
|
28
28
|
|---|---|---|
|
|
29
29
|
| Describe the app for agents | `m-onboard` | Reads the whole project, drafts the product, tech, structure and conventions files in `docs/amk/`, asks what the code can't show, and writes them once you approve. Run it after installing, and again after big changes. |
|
|
30
30
|
| Think a problem through | `m-explore` | The agent reads the code, explains how it works today and lays out options with trade-offs. It never edits code. |
|
|
31
|
+
| Agree on an idea before building it | `m-prototype` | Concepts as clickable HTML mocks when how it should work is still open, then real screens with mock data on a throwaway branch, with screenshots and a video for the demo. The agreed requirements go to `m-feature` |
|
|
31
32
|
| Build a feature | `m-feature` | Requirements → you approve → design and tasks → you approve → one task at a time with tests → device checks with screenshots → living spec updated → review → PR |
|
|
33
|
+
| Make a small change | `m-change` | Checks it's small, then shows the code, living-spec and docs changes for one approval, makes them together and runs the checks |
|
|
32
34
|
| Fix a bug | `m-bugfix` | Reproduces the bug, proves it with a failing test, finds the root cause, then makes the smallest fix |
|
|
33
35
|
| Stop, or switch tool or machine | `m-pause` | Writes a handoff in the spec, commits and pushes |
|
|
34
36
|
| Carry on anywhere | `m-continue` | Reads the spec and handoff, then picks up at the next step |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agentic-mobile-kit",
|
|
3
|
-
"version": "0.7.
|
|
3
|
+
"version": "0.7.3",
|
|
4
4
|
"description": "One setup for AI-assisted development of React Native apps, bare or Expo: shared rules and workflows for Claude Code, Codex and Antigravity, git hooks, device checks with screenshots, and release tooling for the App Store and Google Play.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "prakashpro1",
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: m-change
|
|
3
|
+
description: Make a small change to behavior the app already has - a text, a limit, a validation rule, a style, a small UX tweak - and update the living spec and docs/amk with it, after one approval. Run only when the user explicitly invokes m-change.
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# m-change
|
|
8
|
+
|
|
9
|
+
The user chose this workflow: follow its steps for this task, even where other workflow instructions in this project (Superpowers, BMAD, proAgents or similar) say otherwise.
|
|
10
|
+
|
|
11
|
+
Input: $ARGUMENTS (the change in a sentence or two, or a task link plus pasted details).
|
|
12
|
+
|
|
13
|
+
## 1. Check that it's small
|
|
14
|
+
|
|
15
|
+
A small change adjusts behavior the app already has, in a few files: a text, a limit, a validation rule, a style, a small UX tweak. It's too big for this workflow if it needs a new screen, a new dependency, a new API call, a data migration or native files (`Info.plist`, `AndroidManifest.xml`, `build.gradle`, `Podfile`): then suggest `m-feature` and stop. If the app doesn't do what it should, it's a bug: suggest `m-bugfix`. If the change is unclear, ask one question at a time.
|
|
16
|
+
|
|
17
|
+
## 2. Find everything it touches
|
|
18
|
+
|
|
19
|
+
- **Code:** every place the behavior lives, on both platforms, including shared constants, translations and tests.
|
|
20
|
+
- **Living spec:** the requirement in `specs/current/<area>.md` that describes this behavior today. Behavior the living spec doesn't cover yet becomes a new requirement there.
|
|
21
|
+
- **Docs:** lines in `docs/amk/` that the change makes untrue.
|
|
22
|
+
|
|
23
|
+
## 3. One approval
|
|
24
|
+
|
|
25
|
+
Show in one message:
|
|
26
|
+
- each file to change, and how;
|
|
27
|
+
- the requirement as it is and as it will be, or the new one;
|
|
28
|
+
- the doc lines that change;
|
|
29
|
+
- how it will be checked: a test where logic changes, and the screens on both platforms for anything visible.
|
|
30
|
+
|
|
31
|
+
**Stop until the user approves.** On the main branch, suggest a new branch first.
|
|
32
|
+
|
|
33
|
+
## 4. Make it
|
|
34
|
+
|
|
35
|
+
If no requirement changes, as with a pure style change, skip the spec files (steps 1, 5 and 6 below).
|
|
36
|
+
|
|
37
|
+
1. Pick an ID: the task's ID if it has one, otherwise `YYYYMMDD-<slug>`. Write `specs/<id>/requirements.md` with a title, a one-line goal and only the requirements that change, under `## MODIFIED Requirements: <area>` (or ADDED or REMOVED; the format is in `specs/current/README.md`). Run `node scripts/amk/specs.js check specs/<id>/requirements.md`.
|
|
38
|
+
2. Change the code, and add or update a test where logic changed.
|
|
39
|
+
3. Run `sh scripts/amk/verify.sh quick` and show its output.
|
|
40
|
+
4. For a visible change, write `.maestro/<id>.yaml` from `specs/_templates/flow.yaml`: open the changed screen and take a screenshot. Run `sh scripts/amk/verify.sh all --spec <id>` and open the screenshots in `.amk/evidence/<id>/`. Off a Mac it checks Android only: say that iOS still needs checking on a Mac.
|
|
41
|
+
5. Run `node scripts/amk/specs.js merge <id>` to update the living spec, and change the doc lines from step 3.
|
|
42
|
+
6. Copy `specs/_templates/progress.md` to `specs/<id>/progress.md`, set `Status: done`, and write down the checks and their results.
|
|
43
|
+
|
|
44
|
+
If the change turns out bigger than it looked, stop and suggest `m-feature`, carrying over what you found.
|
|
45
|
+
|
|
46
|
+
## 5. Commit
|
|
47
|
+
|
|
48
|
+
Commit the code, `specs/<id>/`, `specs/current/` and the docs together, with a clear message ending in `Spec: specs/<id>`. Ask before pushing. Then open a pull request that starts with the requirement change and shows the evidence.
|
|
@@ -14,4 +14,4 @@ Input: $ARGUMENTS (a problem, a question about how something works, or an idea t
|
|
|
14
14
|
2. **Explain what's there today:** the screens, state, API calls and native parts involved, and where iOS and Android differ.
|
|
15
15
|
3. **When there's a choice, lay out options:** two or three, each with its trade-offs (effort, risk, both platforms, native changes, store review, what it leaves unsolved). Say which one you'd pick and why. Diagrams help when the flow is complicated.
|
|
16
16
|
4. **Change nothing.** Exploring never edits code, config or project files. Write notes only when the user asks: a draft in `specs/<id>/requirements.md` for `m-feature`, or a decision in `docs/amk/decisions.md`.
|
|
17
|
-
5. **Hand off when it's clear.** Suggest the next step: `m-feature <one-line summary>` or `m-bugfix <one-line summary>`, carrying over what you found. If the idea turns out not to be worth doing, say so; learning that cheaply is a good outcome.
|
|
17
|
+
5. **Hand off when it's clear.** Suggest the next step: `m-feature <one-line summary>`, `m-change <one-line summary>` for a small change, `m-prototype <one-line summary>` when it needs a demo or a design before it's built, or `m-bugfix <one-line summary>`, carrying over what you found. If the idea turns out not to be worth doing, say so; learning that cheaply is a good outcome.
|
|
@@ -12,13 +12,13 @@ Input: $ARGUMENTS (the requirement text, a file path, or a task link plus pasted
|
|
|
12
12
|
|
|
13
13
|
## 1. Always use the full flow
|
|
14
14
|
|
|
15
|
-
The user chose `m-feature`, so follow every step below, however small the change looks. Never skip the spec or the approval stops on your own judgment. (
|
|
15
|
+
The user chose `m-feature`, so follow every step below, however small the change looks. Never skip the spec or the approval stops on your own judgment. (For a small change to behavior the app already has, suggest `m-change`. A change with nothing to record, such as fixing a typo, can just be asked for directly.)
|
|
16
16
|
|
|
17
17
|
If the input describes a bug rather than new behavior, suggest `m-bugfix` and stop. If it's still a vague problem ("the checkout feels slow") or an area you'd have to learn first, suggest `m-explore` first.
|
|
18
18
|
|
|
19
19
|
## 2. Requirements (then stop for approval)
|
|
20
20
|
|
|
21
|
-
1. Pick an ID: the task's ID if it has one, otherwise `YYYYMMDD-<slug>`. Copy `specs/_templates/` to `specs/<id>/`.
|
|
21
|
+
1. Pick an ID: the task's ID if it has one, otherwise `YYYYMMDD-<slug>`. Copy `specs/_templates/` to `specs/<id>/`. If `specs/<id>/` already has a draft from `m-explore` or `m-prototype`, keep it and copy only the missing files.
|
|
22
22
|
2. Read `specs/current/<area>.md` for each area this touches: it says what the app does now. In an area with no living spec yet, read the code that implements it.
|
|
23
23
|
3. **One intent.** The feature should be one thing you can say in a sentence. If it needs "and also", suggest splitting it into separate features, and ask.
|
|
24
24
|
4. Fill `requirements.md`: the goal; the requirements under `## ADDED`, `## MODIFIED` and `## REMOVED Requirements: <area>` (the format is in `specs/current/README.md`), with one SHALL per requirement and scenarios for the cases that matter; every edge-case line (or "n/a"); out of scope; open questions. Then run `node scripts/amk/specs.js check specs/<id>/requirements.md`.
|
|
@@ -53,10 +53,12 @@ When all tasks are done:
|
|
|
53
53
|
1. Run `sh scripts/amk/verify.sh all --spec <id>`. Off a Mac it checks Android only: record in `progress.md` that iOS still needs `verify.sh ios --spec <id>` on a Mac, and say so in the PR. Then **open the screenshots** in `.amk/evidence/<id>/` and check each one against its scenario. Maestro can report a tap as passed when nothing happened, so the screenshots are the evidence, not the log.
|
|
54
54
|
2. Go through every scenario and note its evidence: a test name, command output, or the screen checked. Where the code and the spec disagree, fix whichever is wrong, asking first if it's the spec. The spec must describe what ships.
|
|
55
55
|
|
|
56
|
-
## 6. Update the living spec
|
|
56
|
+
## 6. Update the living spec and the docs
|
|
57
57
|
|
|
58
58
|
Run `node scripts/amk/specs.js merge <id>`. It applies the ADDED, MODIFIED and REMOVED requirements to `specs/current/` and notes the source of each. If it refuses, the reason is usually that a requirement listed as ADDED already exists, or one listed as MODIFIED doesn't. Fix `requirements.md` and run it again. Commit `specs/current/` with the feature, so reviewers see the change in behavior.
|
|
59
59
|
|
|
60
|
+
Then update the `docs/amk/` files the feature made untrue: a new key journey in `product.md`, a new library or service in `tech.md`, a new folder or shared component in `structure.md`, a new pattern in `conventions.md`. Commit them with the feature too.
|
|
61
|
+
|
|
60
62
|
## 7. Review and pull request
|
|
61
63
|
|
|
62
64
|
1. Run `m-review` (or ask the `m-reviewer` subagent, if your tool has subagents). Fix real problems only; skip style nits.
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: m-prototype
|
|
3
|
+
description: Turn a rough requirement into something to demo before it's built - two or three concepts as clickable HTML mocks when how it should work is still open, then real screens with mock data on a throwaway branch, with screenshots and a video - and into requirements ready for m-feature. Run only when the user explicitly invokes m-prototype.
|
|
4
|
+
disable-model-invocation: true
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# m-prototype
|
|
8
|
+
|
|
9
|
+
The user chose this workflow: follow its steps for this task, even where other workflow instructions in this project (Superpowers, BMAD, proAgents or similar) say otherwise.
|
|
10
|
+
|
|
11
|
+
Input: $ARGUMENTS (the rough requirement, notes from `m-explore`, or a task link plus pasted details).
|
|
12
|
+
|
|
13
|
+
A prototype answers questions before the real build: what the client wants, how it should work and how it should look. It's thrown away afterwards, and `m-feature` builds the real thing from the requirements it settled.
|
|
14
|
+
|
|
15
|
+
## 1. Understand
|
|
16
|
+
|
|
17
|
+
1. Read the requirement, `docs/amk/product.md`, `structure.md` and `conventions.md`, the living spec for the area in `specs/current/`, and the screens around where this would live: their components, theme and navigation.
|
|
18
|
+
2. Ask who the demo is for (the client or the team) and what it must show, one question at a time.
|
|
19
|
+
3. Pick an ID: the task's ID if it has one, otherwise `YYYYMMDD-<slug>`. Create the branch `prototype/<id>` from the main branch; this workflow commits everything there.
|
|
20
|
+
4. Write `specs/<id>/requirements.md` from `specs/_templates/requirements.md`: the goal, what's known so far, and the open questions the prototype should answer. Add a `## Decisions` section for what gets settled along the way.
|
|
21
|
+
5. Decide which case this is:
|
|
22
|
+
- **What to show is clear** (the screens and the flow are known): go to step 3.
|
|
23
|
+
- **How it should work or look is still open:** go to step 2.
|
|
24
|
+
|
|
25
|
+
## 2. Concepts
|
|
26
|
+
|
|
27
|
+
1. Work out two or three genuinely different ways it could work: different flows or layouts, not colour variants. For each, note the user flow step by step, the key screens, and the trade-offs: effort, iOS and Android differences, native or backend work.
|
|
28
|
+
2. Make one HTML file per concept in `specs/<id>/concepts/`: the key screens as phone-sized frames side by side, with the app's colours, fonts and spacing taken from its theme, real texts where they're known, and links between the frames so it can be clicked through. Each is a single file of plain HTML and CSS, with nothing to install or build and nothing loaded from the internet, so it opens in any browser.
|
|
29
|
+
3. Show the concepts with your recommendation. **Stop until the user picks one or combines them.** Write the choice and why under `## Decisions`, and commit.
|
|
30
|
+
|
|
31
|
+
## 3. Build the prototype in the app
|
|
32
|
+
|
|
33
|
+
1. Build the screens with the app's own components, theme and navigation, so it looks and feels like the app. Keep the mock data in one file next to the screens.
|
|
34
|
+
2. No API calls, no native files and no new dependencies. If one seems unavoidable, ask.
|
|
35
|
+
3. Make it easy to reach in a demo: a temporary entry where the feature would live, or the app's first screen when that's simpler.
|
|
36
|
+
4. Skip tests: the prototype is thrown away. It only has to build and run.
|
|
37
|
+
5. Commit on `prototype/<id>`. This branch is never merged.
|
|
38
|
+
|
|
39
|
+
## 4. Make the demo material
|
|
40
|
+
|
|
41
|
+
1. Write `.maestro/<id>-prototype.yaml` from `specs/_templates/flow.yaml`: walk through the prototype the way the demo would, with a `takeScreenshot` on every screen, and `startRecording: <id>-prototype` after the launch and `stopRecording` at the end for a video.
|
|
42
|
+
2. Run `sh scripts/amk/verify.sh all --flow .maestro/<id>-prototype.yaml --label <id>-prototype`. Off a Mac it covers Android only.
|
|
43
|
+
3. Open every screenshot and check that it shows what the demo needs. Give the user the folder `.amk/evidence/<id>-prototype/`, which has the screenshots and a video per platform, and the concept files if there are any. For a live demo, run the app from this branch on a phone or simulator.
|
|
44
|
+
|
|
45
|
+
## 5. Take in the feedback
|
|
46
|
+
|
|
47
|
+
After the demo, write what was settled into `requirements.md`: answered questions become requirements and scenarios, and the choices go under `## Decisions`. If the client asked for changes, change the prototype and run step 4 again. Repeat until the user approves the requirements.
|
|
48
|
+
|
|
49
|
+
## 6. Hand off to m-feature
|
|
50
|
+
|
|
51
|
+
1. Create the feature branch from the main branch and bring the spec over: `git checkout prototype/<id> -- specs/<id>`. Leave the prototype code behind.
|
|
52
|
+
2. Add the decisions from `## Decisions` to `docs/amk/decisions.md`, with the date. Run `node scripts/amk/specs.js check specs/<id>/requirements.md`, and commit.
|
|
53
|
+
3. Suggest `m-feature specs/<id>/requirements.md`. In `design.md` it names the `prototype/<id>` branch as the agreed flow and look, and it builds the real screens properly: real data, error, loading and empty states, and tests, on both platforms.
|
|
54
|
+
4. Delete the `prototype/<id>` branch once the feature has shipped.
|