create-foldkit-app 0.6.1 → 0.6.2
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/templates/base/AGENTS.md +6 -0
package/package.json
CHANGED
package/templates/base/AGENTS.md
CHANGED
|
@@ -101,6 +101,12 @@ Use `Story.story` to chain steps into a readable narrative: set initial Model
|
|
|
101
101
|
|
|
102
102
|
If the `repos/foldkit` submodule is available, study the `.test.ts` files in `repos/foldkit/examples/` for patterns — they cover simple Command resolution, multi-step interactions, and Submodel OutMessage assertions.
|
|
103
103
|
|
|
104
|
+
## Debugging with Foldkit DevTools
|
|
105
|
+
|
|
106
|
+
This project ships with `@foldkit/devtools-mcp` pre-wired. When the dev server is running and the app is open in a browser tab, `foldkit_*` MCP tools are available for inspecting Model, Message history, and time-travel. Reach for them before adding `console.log` whenever the question is about state or Message flow.
|
|
107
|
+
|
|
108
|
+
If the `foldkit_*` tools aren't visible, see `@foldkit/devtools-mcp` on npm for setup.
|
|
109
|
+
|
|
104
110
|
## Code Quality Standards
|
|
105
111
|
|
|
106
112
|
- Every name should eliminate ambiguity. Prefix Option-typed values with `maybe` (e.g. `maybeSession`). Name functions by their precise effect (e.g. `enqueueMessage` not `addMessage`). A reader should never need to check a type signature to understand what a name refers to.
|