create-foldkit-app 0.23.2 → 0.24.0

package/dist/examples.js

@@ -12,6 +12,7 @@ export const EXAMPLE_VALUES = [
     'charting',
     'routing',
     'route-transitions',
+    'view-transitions',
     'interrupting-commands',
     'query-sync',
     'snake',
@@ -95,6 +96,11 @@ export const examples = [
         title: 'route-transitions',
         description: 'Live transition log with entry, exit, and stayed navigation policies',
     },
+    {
+        value: 'view-transitions',
+        title: 'view-transitions',
+        description: 'Shared-element morphs and direction-aware route animations via the View Transitions API',
+    },
     {
         value: 'interrupting-commands',
         title: 'interrupting-commands',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-foldkit-app",
-  "version": "0.23.2",
+  "version": "0.24.0",
   "description": "Create Foldkit applications",
   "type": "module",
   "main": "./dist/index.js",

package/templates/base/AGENTS.md

@@ -56,6 +56,8 @@ Every view receives `h`, the typed Html builder, as its last parameter (`view: (
 
 Keys are for mapped list items only: key each row by a stable Model identifier (`h.keyed('li')(item.id, [], [...])`), never by array position, and never derive a key from displayed data. Never key branches; the build gives each view function's output its own identity, so branch switches replace DOM automatically. When switching an inline same-tag ternary must reset DOM state, extract each arm into its own named view function.
 
+Omit the children argument when an element has none: `h.div([h.Class('divider')])`, never `h.div([h.Class('divider')], [])`. The same holds for `keyed`: `h.keyed('li')(key, [attrs])`, never `h.keyed('li')(key, [attrs], [])`. Attributes stay required on element builders, so `h.div([])` is an element with neither. Sibling elements that end up at different arities are expected and fine; void elements like `h.img` have always read that way.
+
 ### Commands
 
 Define a Command with `Command.define(name, { args, messages, execute })`; omit `args` when the Command takes none. Assign definitions to PascalCase constants. Never inline in pipe chains. Name the effect `execute` performs, not the later Model transition caused when update handles its result: a timer that only waits before update starts a dismissal is `WaitBeforeDismissal`, not `DismissAfter`. Commands catch all errors via `Effect.catch(() => Effect.succeed(FailedX(...)))` so side effects never crash the app. Definitions live colocated with the update function that returns them.