@mr.dj2u/knowledge 0.1.4 → 0.1.5
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.
|
@@ -46,12 +46,12 @@ Two prompts and several callable MDS MCP tools ship with the server:
|
|
|
46
46
|
|
|
47
47
|
- `create_expo_super_stack` — invoke from a **parent folder** (e.g.
|
|
48
48
|
`F:\ReactNativeApps`) when the app folder does not exist yet. This is
|
|
49
|
-
now a thin orchestration prompt:
|
|
50
|
-
|
|
51
|
-
memory
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
`
|
|
49
|
+
now a thin orchestration prompt: `mds_runtime_versions` checks for
|
|
50
|
+
stale installs, `create_expo_super_stack_resolve_info` resolves
|
|
51
|
+
project memory in one call when `info.md` is available,
|
|
52
|
+
`create_expo_super_stack_intake_step` is only the manual fallback for
|
|
53
|
+
missing or ambiguous answers, and generation happens through
|
|
54
|
+
`create_expo_super_stack_generate`.
|
|
55
55
|
- `onboard_new_expo_app` — invoke from **inside an existing Expo app
|
|
56
56
|
folder** (a freshly generated one or a year-old project). Runs the
|
|
57
57
|
intake → normalize → plan → scaffold flow.
|
|
@@ -79,10 +79,11 @@ fills the section or deletes the marker line.
|
|
|
79
79
|
agent asks for clarification only when the file is silent or unclear.
|
|
80
80
|
A reference template URL is mentioned in the prompt; the agent can
|
|
81
81
|
also inline the template on request.
|
|
82
|
-
- **Shared
|
|
82
|
+
- **Shared resolver-first intake.** `create_expo_super_stack_resolve_info`
|
|
83
83
|
parses existing project memory up front, derives app naming details,
|
|
84
|
-
|
|
85
|
-
|
|
84
|
+
merges explicit overrides, returns missing or ambiguous fields, and
|
|
85
|
+
produces a ready-to-pass generate payload so the user is not forced
|
|
86
|
+
through redundant question-by-question discovery.
|
|
86
87
|
- **Android TV alongside Apple TV.** The platform multi-select now
|
|
87
88
|
includes Android TV. Android TV builds from the same Android target
|
|
88
89
|
with leanback config in `app.json`; Apple TV is a separate tvOS build
|
|
@@ -1,34 +1,59 @@
|
|
|
1
|
-
# /create-expo-super-stack
|
|
2
|
-
|
|
3
|
-
Create a new Expo app with the MDS Super Stack flow, using
|
|
4
|
-
|
|
5
|
-
## Arguments
|
|
6
|
-
|
|
7
|
-
- `parentDir`: folder where the new app directory should be created.
|
|
8
|
-
- `appName`: app folder name.
|
|
9
|
-
|
|
10
|
-
## Required MDS MCP Tool Flow
|
|
11
|
-
|
|
12
|
-
1.
|
|
13
|
-
2. If the user pasted or attached `info.md` / project memory, call `
|
|
14
|
-
3.
|
|
15
|
-
4. Ask exactly one question per turn
|
|
16
|
-
5.
|
|
17
|
-
6.
|
|
18
|
-
7.
|
|
19
|
-
8.
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
-
|
|
33
|
-
-
|
|
34
|
-
-
|
|
1
|
+
# /create-expo-super-stack
|
|
2
|
+
|
|
3
|
+
Create a new Expo app with the MDS Super Stack flow, using callable MDS MCP tools as the guided intake surface and the Super Stack generator as the scaffold source of truth.
|
|
4
|
+
|
|
5
|
+
## Arguments
|
|
6
|
+
|
|
7
|
+
- `parentDir`: folder where the new app directory should be created.
|
|
8
|
+
- `appName`: app folder name.
|
|
9
|
+
|
|
10
|
+
## Required MDS MCP Tool Flow
|
|
11
|
+
|
|
12
|
+
1. Call `mds_runtime_versions` first to inspect the active runtime and invocation path.
|
|
13
|
+
2. If the user pasted or attached `info.md` / project memory, call `create_expo_super_stack_resolve_info` once with `parentDir`, `appName`, `infoMarkdown`, optional `styleMarkdown`, and any explicit user overrides.
|
|
14
|
+
3. Treat the resolver `answers` object as the canonical accumulated answers object.
|
|
15
|
+
4. Ask exactly one question per turn only for `missingQuestionIds` or `ambiguousQuestionIds`.
|
|
16
|
+
5. Do not restart intake with one answer at a time after a successful resolve call.
|
|
17
|
+
6. If no `info.md` is available, fall back to `create_expo_super_stack_intake_step` and always pass the full accumulated `answers` object.
|
|
18
|
+
7. When the resolver returns `confirm`, summarize `summaryLines` and ask the user for one final confirmation.
|
|
19
|
+
8. After explicit confirmation, print the waiting message below, then call `create_expo_super_stack_generate` with the resolver `generateInput` and `confirmed: true`.
|
|
20
|
+
|
|
21
|
+
## Waiting Message Before Generate
|
|
22
|
+
|
|
23
|
+
After the user confirms, print this block before running the generator so they have something useful to read while scaffolding runs:
|
|
24
|
+
|
|
25
|
+
Generating now. This typically takes 2-5 minutes. While we wait, let's shout out and recognize how this is working.
|
|
26
|
+
|
|
27
|
+
create-expo-super-stack by Mr. DJ (who also built this agentic flow) wraps create-expo-stack by Roni OSS with major contributions by Dan Stepanov (NativeWind). Big thanks to them and to several other teams and individuals whose work and educational materials fill Mr. DJ's Dev Suite knowledge base:
|
|
28
|
+
|
|
29
|
+
- Expo team (Evan Bacon for Expo Router, Brent Vatne, Charlie Cheever, and the broader Expo crew)
|
|
30
|
+
- React and React Native core teams
|
|
31
|
+
- Software Mansion (Reanimated, Gesture Handler, Screens, Worklets; Krzysztof Magiera and team)
|
|
32
|
+
- Supabase, Drizzle, and Zustand teams
|
|
33
|
+
- Adam Wathan and the Tailwind CSS team (the foundation Uniwind and NativeWind build on)
|
|
34
|
+
- Janic Duplessis for "The real cost of React Native animations: benchmarking every approach"
|
|
35
|
+
- Simon Grimm of Galaxies.dev
|
|
36
|
+
- Beto Adrian Maldonado of codewithbeto.dev
|
|
37
|
+
- Vadim of notJust.dev
|
|
38
|
+
- William Candillon for the React Native animation deep-dive content
|
|
39
|
+
- Catalin Miron for the React Native animation tutorials
|
|
40
|
+
- Infinite Red / Jamon Holmgren for Ignite and the broader RN community
|
|
41
|
+
|
|
42
|
+
Their contributions to the software development community are what fill the pages of Mr. DJ's Dev Suite knowledge base, alongside contributions and organization by Mr. DJ. Please enjoy the experience of the Mr. DJ's Dev Suite plugin as you continue your development.
|
|
43
|
+
|
|
44
|
+
## Failure Behavior
|
|
45
|
+
|
|
46
|
+
1. If the guided intake or generate tools are unavailable, stop.
|
|
47
|
+
2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
|
|
48
|
+
3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
|
|
49
|
+
4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
|
|
50
|
+
|
|
51
|
+
Warn only when `mds_runtime_versions.warnings` is non-empty or when the user expected different versions than the runtime reports.
|
|
52
|
+
Do not describe the normal published install path as a fallback, and do not mention `npm exec` or `npx` to the user unless there is an actual runtime problem they need to act on.
|
|
53
|
+
|
|
54
|
+
## Verification And Output
|
|
55
|
+
|
|
56
|
+
- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
|
|
57
|
+
- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
|
|
58
|
+
- If those Super Stack artifacts are missing, treat generation as a failure or partial scaffold and say so clearly instead of presenting it as a normal success.
|
|
59
|
+
- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.
|