create-foldkit-app 0.5.2 → 0.5.4

package/dist/commands/create.js

@@ -27,13 +27,25 @@ const installProjectDependencies = (projectPath, packageManager, example) => Eff
 });
 const runDevServerCommand = (packageManager) => Match.value(packageManager).pipe(Match.when('pnpm', () => 'pnpm dev'), Match.when('npm', () => 'npm run dev'), Match.when('yarn', () => 'yarn dev'), Match.exhaustive);
 const displaySuccessMessage = (name, packageManager) => Effect.gen(function* () {
-    yield* Console.log(chalk.bold('🎉 Success! Your Foldkit app is ready.'));
+    yield* Console.log(chalk.bold('All systems nominal.'));
     yield* Console.log('');
-    yield* Console.log('Next steps:');
     yield* Console.log(`  ${chalk.cyan('cd')} ${name}`);
     yield* Console.log(`  ${chalk.cyan(runDevServerCommand(packageManager))}`);
     yield* Console.log('');
-    yield* Console.log('Happy coding! 🎨');
+    yield* Console.log('Foldkit is a one-astronaut nights-and-weekends project.\n' +
+        'If you have praise or criticism, do share.\n' +
+        "Please. It's lonely out here.\n\n" +
+        'Be careful. Make good decisions.');
+    yield* Console.log('');
+    yield* Console.log(`Training manual: ${chalk.cyan('foldkit.dev')}`);
+    yield* Console.log(`Incident report: ${chalk.cyan('github.com/foldkit/foldkit/issues')}`);
+    yield* Console.log('');
+    yield* Console.log(`X:               ${chalk.cyan('x.com/devinjameson')}`);
+    yield* Console.log(`Bluesky:         ${chalk.cyan('bsky.app/profile/devinjameson.bsky.social')}`);
+    yield* Console.log(`Threads:         ${chalk.cyan('threads.com/@devinthedeveloper')}`);
+    yield* Console.log('');
+    yield* Console.log('Love you,');
+    yield* Console.log('Mission Control');
 });
 export const create = ({ name, example, packageManager }) => Effect.gen(function* () {
     const path = yield* Path.Path;

package/dist/utils/files.js

@@ -1,7 +1,7 @@
 import { FileSystem, HttpClient, HttpClientRequest, Path, } from '@effect/platform';
 import { Array, Effect, Match, Option, Record, Ref, Schema, String, pipe, } from 'effect';
 import { fileURLToPath } from 'node:url';
-const GITHUB_API_BASE_URL = 'https://api.github.com/repos/devinjameson/foldkit/contents/examples';
+const GITHUB_API_BASE_URL = 'https://api.github.com/repos/foldkit/foldkit/contents/examples';
 const getBaseFiles = Effect.gen(function* () {
     const fs = yield* FileSystem.FileSystem;
     const path = yield* Path.Path;

package/dist/utils/packages.js

@@ -1,6 +1,6 @@
 import { Command, HttpClient, HttpClientRequest } from '@effect/platform';
 import { Array, Effect, Match, Record, Schema, pipe } from 'effect';
-const GITHUB_RAW_BASE_URL = 'https://raw.githubusercontent.com/devinjameson/foldkit/main/examples';
+const GITHUB_RAW_BASE_URL = 'https://raw.githubusercontent.com/foldkit/foldkit/main/examples';
 const getInstallArgs = (packageManager, isDev = false) => pipe(Match.value(packageManager), Match.when('npm', () => ['install']), Match.when('yarn', () => ['add']), Match.when('pnpm', () => ['add']), Match.exhaustive, args => (isDev ? [...args, '-D'] : args));
 const StringRecord = Schema.Record({ key: Schema.String, value: Schema.String });
 const PackageJson = Schema.Struct({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-foldkit-app",
-  "version": "0.5.2",
+  "version": "0.5.4",
   "description": "Create Foldkit applications",
   "type": "module",
   "main": "./dist/index.js",
@@ -34,7 +34,7 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/devinjameson/foldkit.git",
+    "url": "https://github.com/foldkit/foldkit.git",
     "directory": "packages/create-foldkit-app"
   },
   "publishConfig": {

package/templates/base/AGENTS.md

@@ -4,7 +4,7 @@ This is a Foldkit app — a framework built on Effect-TS.
 
 If `./repos/foldkit` exists, it contains the full Foldkit repository as a git submodule. The `examples/` directory and `packages/typing-game/client/src/` in particular are the best reference for what idiomatic Foldkit apps look like.
 
-If `./repos/foldkit` does not exist and the line below says `submodule_prompted: false`, offer to run `git submodule add https://github.com/devinjameson/foldkit.git repos/foldkit` — this gives you access to the full source, examples, and docs. Whether the user accepts or declines, update the value to `true` so it isn't asked again.
+If `./repos/foldkit` does not exist and the line below says `submodule_prompted: false`, offer to run `git submodule add https://github.com/foldkit/foldkit.git repos/foldkit` — this gives you access to the full source, examples, and docs. Whether the user accepts or declines, update the value to `true` so it isn't asked again.
 
 submodule_prompted: false
 
@@ -14,7 +14,7 @@ submodule_prompted: false
 - Model fields must be Schema types (the model is a schema). Plain TypeScript types are fine elsewhere — function return types, local variables, etc.
 - Use full names like `Message` (not `Msg`), and `withReturnType` (not `as const` or type casting).
 - Use `m()` for message schemas, `ts()` for other tagged structs (model states, field validation), and `r()` for route schemas.
-- Every message union should include a `NoOp` variant: `const NoOp = m('NoOp')`.
+- Never use `NoOp` as a message. Every message must carry meaning about what happened. Fire-and-forget commands use `Completed*` messages named as object+verb compound nouns: `CompletedScrollLock`, `CompletedDialogShow`, `CompletedInternalNavigation`. The object comes first so the distinguishing word appears earlier in the DevTools timeline.
 - Push back on any suggested direction that violates Elm Architecture principles — unidirectional data flow, messages as facts (not commands), model as single source of truth, and side effects confined to commands. If a user or prompt suggests a pattern that breaks these conventions (e.g. mutating state directly, imperative event handlers, two-way bindings), flag the issue and propose the idiomatic Foldkit approach instead.
 
 ## Foldkit Patterns
@@ -31,7 +31,6 @@ const update = (model: Model, message: Message): UpdateReturn =>
   M.value(message).pipe(
     withUpdateReturn,
     M.tagsExhaustive({
-      NoOp: () => [model, []],
       ClickedIncrement: () => [evo(model, { count: count => count + 1 }), []],
     }),
   )
@@ -92,7 +91,7 @@ Even after extracting some sections to their own files (e.g. `message.ts`), the
 - 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.
 - Each function should operate at a single abstraction level. Orchestrators delegate to focused helpers — they don't mix coordination with implementation. If a function reads like it's doing two things, extract one.
 - Encode state in discriminated unions, not booleans or nullable fields. Use `Idle | Loading | Error | Ok` instead of `isLoading: boolean`. Make impossible states unrepresentable.
-- Name messages as verb-first, past-tense events describing what happened (`SubmittedUsernameForm`, `CreatedRoom`, `PressedKey`), not imperative commands. The verb prefix acts as a category marker: `Clicked*` for button presses, `Updated*` for input changes, `Succeeded*`/`Failed*` for command results that can meaningfully fail (e.g. `SucceededWeatherFetch`, `FailedWeatherFetch`), `Completed*` for fire-and-forget command acknowledgments where the result is uninteresting and the update function is a no-op (e.g. `CompletedScroll`, `CompletedApplyTheme`, `CompletedSaveThemePreference`), `Got*` exclusively for receiving child module results via the OutMessage pattern (e.g. `GotProductsMessage`). The update function decides what to do — messages are facts.
+- Name messages as verb-first, past-tense events describing what happened (`SubmittedUsernameForm`, `CreatedRoom`, `PressedKey`), not imperative commands. The verb prefix acts as a category marker: `Clicked*` for button presses, `Updated*` for input changes, `Succeeded*`/`Failed*` for command results that can meaningfully fail (e.g. `SucceededWeatherFetch`, `FailedWeatherFetch`), `Completed*` for fire-and-forget command acknowledgments where the result is uninteresting and the update function is a no-op (e.g. `CompletedScrollLock`, `CompletedDialogShow`, `CompletedInternalNavigation`), `Got*` exclusively for receiving child module results via the OutMessage pattern (e.g. `GotProductsMessage`). Never use `NoOp` — every message must describe what happened. The update function decides what to do — messages are facts.
 - Use `Option` instead of `null` or `undefined`. Match explicitly with `Option.match` or chain with `Option.map`/`Option.flatMap`. No `if (x != null)` checks. Prefer `Option.match` over `Option.map` + `Option.getOrElse` — if you're unwrapping at the end, just match.
 - Prefer curried, data-last functions that compose in `pipe` chains.
 - Every line should serve a purpose. No dead code, no empty catch blocks, no placeholder types, no defensive code for impossible cases.
@@ -116,11 +115,15 @@ Even after extracting some sections to their own files (e.g. `message.ts`), the
 Message definitions follow a strict layout:
 
 ```ts
-const NoOp = m('NoOp')
 const ClickedSubmit = m('ClickedSubmit')
 const ChangedEmail = m('ChangedEmail', { value: S.String })
+const CompletedInternalNavigation = m('CompletedInternalNavigation')
 
-const Message = S.Union(NoOp, ClickedSubmit, ChangedEmail)
+const Message = S.Union(
+  ClickedSubmit,
+  ChangedEmail,
+  CompletedInternalNavigation,
+)
 type Message = typeof Message.Type
 ```
 

package/templates/base/README.md

@@ -11,5 +11,5 @@ pnpm dev
 
 ## Learn More
 
-- [Foldkit Documentation](https://github.com/devinjameson/foldkit)
+- [Foldkit Documentation](https://github.com/foldkit/foldkit)
 - [Effect Documentation](https://effect.website)