agentic-mobile-kit 0.7.3 → 0.7.4
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 +1 -1
- package/stacks/react-native/expo/docs/amk/expo.md +1 -0
- package/stacks/react-native/template/.agents/skills/m-learn/SKILL.md +1 -1
- package/stacks/react-native/template/.agents/skills/m-review/SKILL.md +1 -0
- package/stacks/react-native/template/docs/amk/react-native.md +1 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agentic-mobile-kit",
|
|
3
|
-
"version": "0.7.
|
|
3
|
+
"version": "0.7.4",
|
|
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",
|
|
@@ -28,6 +28,7 @@ Rules for things AI agents commonly get wrong in Expo apps. Each one comes from
|
|
|
28
28
|
- For apps targeting Android 16 (API 36), `onBackPressed` is no longer called. Handle back with `BackHandler` in JS.
|
|
29
29
|
- Check every UI change on both iOS and Android; behavior differs (keyboard, insets, fonts, permissions).
|
|
30
30
|
- Give every interactive element a `testID` (kebab-case, for example `dark-mode-switch`). End-to-end tools tap by `testID`. On iOS, React Native exposes a label and its control as duplicate accessibility elements, so tapping by text can hit the label: nothing happens, yet the tool reports success.
|
|
31
|
+
- Give every interactive element an `accessibilityLabel` that says what it does and an `accessibilityRole` (`button`, `link`, `switch`, …), so screen readers can use it. Icon-only buttons need it most; screen readers don't read `testID`.
|
|
31
32
|
|
|
32
33
|
## Performance and libraries
|
|
33
34
|
|
|
@@ -24,5 +24,5 @@ Input: $ARGUMENTS (what went wrong or what the user had to correct; the error te
|
|
|
24
24
|
5. **Show that it works.**
|
|
25
25
|
- For a check: show it failing on the old mistake and passing on the fixed code.
|
|
26
26
|
- For docs or a skill: show the diff, and name the task that would have gone differently.
|
|
27
|
-
6. **This project or every project?** If the lesson applies to any React Native app, say so and draft an issue for the agentic-mobile-kit
|
|
27
|
+
6. **This project or every project?** If the lesson applies to any React Native app, say so and draft an issue for the kit at https://github.com/prakashpro3/agentic-mobile-kit/issues, so every project gets the fix. Include what happened, the fix you made here, and the kit version from the `KIT:START` line in `AGENTS.md`. Issues there are public, so leave out this app's name, code, URLs and data. Ask before opening it, for example with `gh issue create --repo prakashpro3/agentic-mobile-kit`; without `gh`, give the user the text and the link.
|
|
28
28
|
7. **Commit** with a message that starts with `chore(learn):`. That prefix keeps it out of the changelog and easy to find with `git log --grep 'chore(learn)'` in the monthly review. Ask before pushing.
|
|
@@ -21,6 +21,7 @@ If your tool has subagents, hand the review to the `m-reviewer` subagent, so it
|
|
|
21
21
|
- **No spec:** does the diff do what was asked, and nothing unrelated?
|
|
22
22
|
- **Tests:** were tests added for new logic? Were any tests deleted, skipped or weakened?
|
|
23
23
|
- **Both platforms:** anything iOS-only or Android-only (insets, back button, permissions, keyboard)?
|
|
24
|
+
- **Accessibility:** does every new button or other touchable have an `accessibilityLabel` and an `accessibilityRole`?
|
|
24
25
|
- **Errors and states:** offline, server errors, empty and loading states.
|
|
25
26
|
- **Security:** secrets, tokens, `.env` contents, logging of personal data.
|
|
26
27
|
- **Native:** `project.pbxproj`, `Podfile`, Gradle or manifest changes, and whether pods and builds were re-run.
|
|
@@ -15,6 +15,7 @@ Rules for things AI agents commonly get wrong in current React Native. Each one
|
|
|
15
15
|
- For apps targeting Android 16 (API 36), `onBackPressed` is no longer called. Handle back with `BackHandler` in JS, or `OnBackPressedDispatcher` in native code.
|
|
16
16
|
- Check every UI change on both iOS and Android; behavior differs (keyboard, insets, fonts, permissions).
|
|
17
17
|
- Give every interactive element a `testID` (kebab-case, for example `dark-mode-switch`). End-to-end tools tap by `testID`. On iOS, React Native exposes a label and its control as duplicate accessibility elements, so tapping by text can hit the label: nothing happens, yet the tool reports success.
|
|
18
|
+
- Give every interactive element an `accessibilityLabel` that says what it does and an `accessibilityRole` (`button`, `link`, `switch`, …), so screen readers can use it. Icon-only buttons need it most; screen readers don't read `testID`.
|
|
18
19
|
|
|
19
20
|
## Native changes
|
|
20
21
|
|