agentic-mobile-kit 0.7.17 → 0.7.19
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 +3 -3
- package/bin/cli.js +1 -1
- package/lib/init.js +62 -10
- package/package.json +1 -1
- package/stacks/react-native/expo/.rulesync/permissions.jsonc +6 -0
- package/stacks/react-native/expo/AGENTS.md +7 -3
- package/stacks/react-native/expo/docs/amk/expo.md +11 -0
- package/stacks/react-native/template/.agents/skills/m-bugfix/SKILL.md +10 -11
- package/stacks/react-native/template/.agents/skills/m-continue/SKILL.md +1 -1
- package/stacks/react-native/template/.agents/skills/m-explore/SKILL.md +1 -1
- package/stacks/react-native/template/.agents/skills/m-feature/SKILL.md +16 -11
- package/stacks/react-native/template/.agents/skills/m-onboard/SKILL.md +8 -5
- package/stacks/react-native/template/.agents/skills/m-prototype/SKILL.md +5 -5
- package/stacks/react-native/template/.agents/skills/m-review/SKILL.md +5 -2
- package/stacks/react-native/template/.github/pull_request_template.md +3 -1
- package/stacks/react-native/template/.github/workflows/e2e.yml +3 -0
- package/stacks/react-native/template/.rulesync/permissions.jsonc +6 -0
- package/stacks/react-native/template/.rulesync/subagents/m-design-reviewer.md +22 -0
- package/stacks/react-native/template/.rulesync/subagents/m-device-checker.md +2 -2
- package/stacks/react-native/template/.rulesync/subagents/m-reviewer.md +1 -1
- package/stacks/react-native/template/AGENTS.md +7 -3
- package/stacks/react-native/template/docs/amk/design-system.md +15 -0
- package/stacks/react-native/template/docs/amk/glossary.md +12 -0
- package/stacks/react-native/template/docs/amk/react-native.md +11 -0
- package/stacks/react-native/template/scripts/amk/a11y.js +78 -0
- package/stacks/react-native/template/scripts/amk/guard.js +22 -1
- package/stacks/react-native/template/scripts/amk/report.js +78 -0
- package/stacks/react-native/template/scripts/amk/rn-check.js +155 -17
- package/stacks/react-native/template/scripts/amk/verify.sh +134 -15
- package/stacks/react-native/template/specs/_templates/design.md +16 -0
- package/stacks/react-native/template/specs/_templates/flow.yaml +11 -0
- package/stacks/react-native/template/specs/_templates/questions.md +29 -0
- package/stacks/react-native/template/specs/_templates/subflow.yaml +36 -0
- package/stacks/react-native/template/specs/_templates/tasks.md +2 -2
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# <ID>: questions for <who>
|
|
2
|
+
|
|
3
|
+
**Why we ask:** <the decision these answers settle, and what waits on them>
|
|
4
|
+
**From:** <name>. **To:** <name and role>. **Answers by:** <date, if there is one>
|
|
5
|
+
|
|
6
|
+
## Context
|
|
7
|
+
|
|
8
|
+
<!-- One short paragraph for someone who wasn't in the conversation: enough to answer well, not the whole story. -->
|
|
9
|
+
|
|
10
|
+
## How to answer
|
|
11
|
+
|
|
12
|
+
Write your answer under each question. "I don't know" and partial answers help too: say what you're unsure of rather
|
|
13
|
+
than skipping it.
|
|
14
|
+
|
|
15
|
+
## <Theme>
|
|
16
|
+
|
|
17
|
+
<!-- The most important question first: there may be only one reply. One question each, never two in one. A "why it
|
|
18
|
+
matters" line only where the question could be misread or answered too lightly. Group them under themes once there are
|
|
19
|
+
more than a handful. -->
|
|
20
|
+
|
|
21
|
+
### 1. <Question>
|
|
22
|
+
|
|
23
|
+
_Why it matters: <what the answer decides>_
|
|
24
|
+
|
|
25
|
+
>
|
|
26
|
+
|
|
27
|
+
## Anything else we should know?
|
|
28
|
+
|
|
29
|
+
>
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
# Copy to .maestro/subflows/<name>.yaml for steps several flows share: logging in, skipping onboarding, answering a
|
|
2
|
+
# permission prompt. A flow runs it with "- runFlow: subflows/<name>.yaml". verify.sh runs only the flows directly in
|
|
3
|
+
# .maestro/, not the subflows below it. This one logs in with the test account from .maestro/.env.local (MAESTRO_EMAIL,
|
|
4
|
+
# MAESTRO_PASSWORD), which isn't committed.
|
|
5
|
+
appId: ${APP_ID}
|
|
6
|
+
---
|
|
7
|
+
- tapOn:
|
|
8
|
+
id: "login-email"
|
|
9
|
+
- inputText: ${MAESTRO_EMAIL}
|
|
10
|
+
- tapOn:
|
|
11
|
+
id: "login-password"
|
|
12
|
+
- inputText: ${MAESTRO_PASSWORD}
|
|
13
|
+
- tapOn:
|
|
14
|
+
id: "login-submit"
|
|
15
|
+
- extendedWaitUntil:
|
|
16
|
+
visible:
|
|
17
|
+
id: "home-screen"
|
|
18
|
+
timeout: 15000
|
|
19
|
+
|
|
20
|
+
# Test data: so a flow starts from the same data every run, reset it through the app's API first. Put a script like
|
|
21
|
+
# this in .maestro/subflows/reset-data.js, and run it at the start of the flow:
|
|
22
|
+
# - runScript:
|
|
23
|
+
# file: subflows/reset-data.js
|
|
24
|
+
# env:
|
|
25
|
+
# API_URL: ${MAESTRO_API_URL}
|
|
26
|
+
# TEST_TOKEN: ${MAESTRO_TEST_TOKEN}
|
|
27
|
+
# Maestro runs it with its own JavaScript, which has http (docs.maestro.dev: Make HTTP requests) and reads the env
|
|
28
|
+
# values as plain variables. MAESTRO_API_URL and MAESTRO_TEST_TOKEN go in .maestro/.env.local. Point it at the app's
|
|
29
|
+
# own test-only endpoint and test account, never at production data.
|
|
30
|
+
#
|
|
31
|
+
# /* global http, API_URL, TEST_TOKEN */
|
|
32
|
+
# const response = http.post(`${API_URL}/test/reset`, {
|
|
33
|
+
# headers: { Authorization: `Bearer ${TEST_TOKEN}`, 'Content-Type': 'application/json' },
|
|
34
|
+
# body: JSON.stringify({ account: 'e2e' }),
|
|
35
|
+
# });
|
|
36
|
+
# if (!response.ok) throw new Error(`resetting the test data failed: ${response.status} ${response.body}`);
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# <ID>: tasks
|
|
2
2
|
|
|
3
|
-
Each task: about an hour of work, under ~300 changed lines, one commit. Each one names the requirement it serves and how it's checked. Its tests are written in the same task, not in a catch-up task at the end.
|
|
3
|
+
Each task: about an hour of work, under ~300 changed lines, one commit. Each is a thin slice through every layer it needs (screen, state, API call, test) that works and can be checked on its own, not one layer at a time; moving or renaming code that's there, to make the feature easy to add, comes first. Each names the requirement it serves, the tasks it waits on, and how it's checked. Its tests are written in the same task, not in a catch-up task at the end.
|
|
4
4
|
|
|
5
|
-
- [ ] 1. <task> — for: <requirement name> — files: <paths> — check: <test, command or screen>
|
|
5
|
+
- [ ] 1. <task> — for: <requirement name> — after: <task numbers, or none> — files: <paths> — check: <test, command or screen>
|
|
6
6
|
- [ ] 2.
|