[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79J2B4K4AG4V08R6EEDVB0F":3,"skill-same:01M79J2B4K4AG4V08R6EEDVB0F":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79J2B4K4AG4V08R6EEDVB0F","webappwiz",null,"Check whether the webappwiz package already covers a piece of infrastructure before writing it by hand or adding a dependency for it. Read this before writing any of: time, clocks, durations or timers; logging; id generation; CLI argument parsing; background tasks or queues; web workers; markdown parsing; typed event emitters; 2D geometry or spatial indexes; filesystem, env or process access; API keys, tokens, secrets or credentials; AbortSignal plumbing; disposable resources; browser scroll, animation frames or visibility. Also use when a release publishes to npm through GitHub Actions (`via: githubActions()`), when asked to update or upgrade webappwiz in a project, and whenever the user says webappwiz.","jaredjj3\u002Fwebappwiz","jaredjj3","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19232300?v=4","01M79J1J9BQ995Z4VEJH66XX0D","Jared Johnson","01M79J1JA206AF35996PVPE1XE",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz\u002Fblob\u002Fmain\u002Fskills\u002Fwebappwiz\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: webappwiz\ndescription: \"Check whether the webappwiz package already covers a piece of infrastructure before writing it by hand or adding a dependency for it. Read this before writing any of: time, clocks, durations or timers; logging; id generation; CLI argument parsing; background tasks or queues; web workers; markdown parsing; typed event emitters; 2D geometry or spatial indexes; filesystem, env or process access; API keys, tokens, secrets or credentials; AbortSignal plumbing; disposable resources; browser scroll, animation frames or visibility. Also use when a release publishes to npm through GitHub Actions (`via: githubActions()`), when asked to update or upgrade webappwiz in a project, and whenever the user says webappwiz.\"\nversion: 0.0.59\n---\n\n# Using webappwiz\n\n`webappwiz` is the parts of a web app that get written again every time, behind\ninterfaces a test can replace. One package, one subpath per module. Before\nwriting any of that here, find out whether it already exists there.\n\nIts README carries the whole catalogue, a table of every subpath and what it is\nfor. Read it from `node_modules\u002Fwebappwiz\u002FREADME.md`, or, in a project that has\nnot installed it yet, from\n`https:\u002F\u002Fraw.githubusercontent.com\u002Fjaredjj3\u002Fwebappwiz\u002Fmain\u002Fpackages\u002Fwebappwiz\u002FREADME.md`.\n\nNothing in the table is close: say so in a line and write it here. Something is:\nread that module's own README and the exports of its `index.ts`, and judge\nagainst what is actually needed rather than the one-line blurb.\n\n## It fits\n\n`bun add webappwiz` and import the subpath. There is no package entry point, so\nimport `webappwiz\u002Ftime`, never `webappwiz`. Fakes live under `\u002Ftesting` beside\nwhat they replace.\n\n## It nearly fits\n\nDo not vendor it, fork it, or patch `node_modules`. Write what this project\nneeds here so nobody is blocked, leave a `TODO: webappwiz\u002F\u003Csubpath> once \u003Cgap>`\non it, and hand the gap over: print the block below and tell the user to give it\nto an agent working on the webappwiz repo.\n\n```markdown\nIn `packages\u002Fwebappwiz\u002F\u003Csubpath>`: \u003Cthe gap, in a sentence>.\n\nWanted by \u003Cthis project> for \u003Cthe usecase, concretely>.\n\nWhat is there now: \u003Cthe export that comes closest, and where it stops>.\nWhat is missing: \u003Cthe smallest change that closes the gap: one more method, a\nwidened parameter, another implementation of an interface>.\nCalled like: \u003Cthe call site, written the way the caller wants to write it>.\n```\n\nDescribe the gap and stop. Do not design the API in the handoff: that repo has a\nstyle guide and a review, and neither of them is here.\n\n## It does not fit\n\nOne line naming the subpath you read and why it is not the one, then write it\nhere. A wrong module taken up is worse than one written twice.\n\n## Credentials\n\nAn API key, token or other secret a project's code needs comes from\n`webappwiz\u002Fcreds`. Code reads it through `Credentials`, over a list of\nsources it chooses for each place the app runs; the first source with a\nvalue wins. Never put a secret in source, a config file, a test, or a\ncommand line, never write a `.env` file yourself, and never ask for one in\nchat.\n\n### Which source, where\n\nFrom most to least locked down:\n\n1. **The system's secret store**, `SystemSecretStore`: the Keychain,\n   Credential Manager, or a Linux secret service. Encrypted at rest, held\n   apart from files and the environment, so no file read, `env` dump, child\n   process, or agent sees a value. Use it on a person's machine, and only it.\n   - `SystemSecretStore.forProject()`, kept as `webappwiz:\u003Cproject>`: keys\n     the app itself uses, like a Stripe test key. One project's keys are\n     never another's.\n   - `SystemSecretStore.device()`, kept as `webappwiz`: keys that belong to\n     the person and serve many projects, like the tokens scry runs on. Wider\n     reach, so only for keys that really are shared.\n2. **A hosted secrets manager** (1Password, Vault, AWS or GCP Secret\n   Manager), as a source of the app's own: any object with a `label` and an\n   async `get(name)`. Fetched at runtime and access-controlled. Use it where\n   the app is deployed, when the project has one.\n3. **The environment**, `Environment`: how CI, containers and hosting\n   platforms hand a deployed app its secrets. Every child process inherits\n   it, and it shows up in crash reports and debug dumps. Use it where the\n   app is deployed. On a person's machine it means exports in a shell\n   profile, which every program they run can read, so leave it out of the\n   development list.\n4. **A `.env` file**, `DotenvFile(path)`: plaintext on disk, one mistake\n   from being committed, and read by any tool or agent that opens it. Use it\n   only where a deploy target insists on one, never on a person's machine.\n   Under Bun, `.env` files are loaded into the environment already, so\n   `Environment` covers them there.\n\nHow the app tells development from production, and which sources each\nlists, is the project's choice: ask the user when the project does not\nalready say. The usual lists:\n\n```ts\nimport {\n\tCredentials,\n\tEnvironment,\n\tSystemSecretStore,\n} from \"webappwiz\u002Fcreds\";\n\nconst credentials =\n\tprocess.env.APP_ENV === \"development\"\n\t\t? new Credentials([\n\t\t\t\tawait SystemSecretStore.forProject(),\n\t\t\t\tSystemSecretStore.device(),\n\t\t\t])\n\t\t: new Credentials([new Environment()]);\nconst key = await credentials.require(\"STRIPE_SECRET_KEY\");\n```\n\nA tool that reads only its environment, like Prisma, Vite or `wrangler`,\nnever calls `Credentials`. In development, run it through\n`bunx @webappwiz\u002Fcli creds run -- \u003Ccommand>`, which hands it the stored\nkeys for that run alone, usually from a `package.json` script; never reach\nfor a `.env` file or an export to feed it.\n\n`Credentials` is a source itself, so a fallback pattern of the project's\nown is a list of lists: `new Credentials([vault, new\nCredentials([new Environment(), new DotenvFile(\".env\")])])` reads the\nvault, then the environment, then the file. `forProject()` finds the\nstore's name itself, so never write a project name into code. Take the\n`Credentials` as a dependency, so a test hands in one over\n`FakeSecretStore` from `webappwiz\u002Fcreds\u002Ftesting`.\n\n### Adding one\n\n1. Name it in `.wiz\u002Fconfig.ts`, by its environment variable name, with what\n   it is for. `creds add` takes any name, but a named one shows as missing\n   until someone keeps it, so whoever clones the project knows it is needed:\n\n   ```ts\n   export default {\n   \tcredentials: { names: { STRIPE_SECRET_KEY: \"Stripe, for checkout\" } },\n   };\n   ```\n\n2. Run `bunx @webappwiz\u002Fcli creds list` to see which are missing. It\n   never prints a value. For each missing one, ask the user to run\n   `bunx @webappwiz\u002Fcli creds add \u003CNAME>` themselves, with `--device` for a\n   key that is theirs rather than the project's: it asks for the value at a\n   prompt that shows nothing, and refuses when there is no terminal, so you\n   cannot and should not run it for them. `creds remove \u003CNAME>` deletes\n   one.\n\nNothing reads a value back out for you to see, and nothing should: do not\nprint one, log one, or look one up with the system's own tools\n(`security`, `secret-tool`, `cmdkey`). Code that needs a value reads it\nitself.\n\n## Publishing from GitHub Actions\n\nA release whose npm packages publish `via: githubActions()` (from\n`webappwiz\u002Fship`) publishes from the generated workflow, with no token and no\n2FA code. npm allows that only once each package has a trusted publisher\nentry naming the repository and the workflow, and making one takes the\nuser's own npm login in a browser. You cannot do it for them, so when you\nadd `via: githubActions()`, or a ship fails with \"npm refused the run\",\nguide the user through it:\n\n1. Have them run the project's trust command once: `bunx @webappwiz\u002Fcli ship\n   trust` when the release is declared in `.wiz\u002Fship.ts`, or the project's\n   own command that calls `release.trust()`. It runs `npm trust github` for\n   each package.\n2. Tell them npm asks them to authenticate in a browser, and that ticking\n   \"skip two-factor authentication for the next 5 minutes\" there lets the\n   other packages go through without asking again.\n3. A package must already be on npm before it can trust anything, so a\n   package that has never been published goes out once the old way first.\n4. Then they ship as usual. A package that already trusts another workflow\n   fails, and the error says how to clear it.\n\n## Updating\n\n`bunx @webappwiz\u002Fcli update` rewrites every webappwiz dependency under the\ndirectory to one version, since they are released together and a project\nrunning two of them at different versions is running a combination nobody\ntested. The version is the one you invoked, which is what `bunx` is for.\nInstalled skills and copied rules are refreshed with it, and local edits to\nthose do not survive.\n\nIt edits manifests and stops. Nothing is installed until you run `bun install`\nyourself, and nothing is verified until you run this project's typecheck and\ntests.\n\nWhat broke is read the same way as anything else here: the module's own README\nand the exports of its `index.ts`, not the one-line blurb and not a guess. If\nthe new version dropped what this project was using, check the migrations below\nfirst. For removals not covered there, that is a gap: leave the\nlocal code working, and hand it over with the block above. Do not vendor,\nfork, or patch `node_modules` to get the build green.\n\n### Migrating removed `webappwiz\u002Ft` and `webappwiz\u002Fconfig`\n\nThese modules have been removed in favor of Zod and ordinary typed settings.\nIf the project imports either subpath, migrate those callers as part of the\nupdate. This is an intentional replacement, so do not request their restoration\nthrough the gap handoff above.\n\nAdd Zod as a direct dependency in each package importing it (`bun add zod`),\nthen replace `import { t } from \"webappwiz\u002Ft\"` with\n`import { z } from \"zod\"`. Primitive, object, array, enum, optional, and\nnullable builders have Zod equivalents. Replace `Infer\u003Ctypeof schema>` with\n`z.infer\u003Ctypeof schema>`; replace custom `Schema` implementations and\n`SchemaBase` subclasses with Zod schemas, refinements, or transforms.\n\nCheck behavior at each input boundary:\n\n- `.parse()` and `.safeParse()` validate through Zod. Replace\n  `SchemaError.path` and `.reason` with `ZodError.issues`, using each issue's\n  `path` and `message`. For `validate(schema, value)`, use\n  `schema.parse(value)` when the schema is Zod; for other libraries, use\n  their parser or the Standard Schema interface.\n- Zod has no per-schema `.coerce(raw)` method. Use\n  `z.coerce.number().parse(raw)` for numeric strings. Decode JSON strings\n  before validating object or array schemas, handling malformed JSON too.\n- `webappwiz\u002Fcmd` still accepts Standard Schema. It passes strings to the\n  schema, so numeric args and options need `z.coerce.number()`. Declare an\n  on\u002Foff switch as `.option(\"name\", z.boolean(), { default: false })`: it is\n  false unless given, `--name=false` turns it off, and a bare `--name` never\n  takes the next argument as its value. `z.coerce.boolean()` converts\n  `\"false\"` to true and is not a replacement.\n  Command validation remains synchronous and reports an ordinary `Error`\n  with the first issue's dotted path and message.\n- Zod numbers reject infinity. Object schemas still strip extra keys, but\n  missing optional properties are omitted rather than added as `undefined`;\n  their inferred object keys are optional too. Check callers that enumerate\n  keys or rely on exact error wording.\n\nReplace `Config.factory(shape)` with `z.object(shape)`, `config.get(\"key\")`\nwith typed property access, and `config.toRecord()` with the parsed object.\nUse `z.infer\u003Ctypeof Settings>` instead of `InferConfig`. If freezing matters,\nwrap the parsed object in `Object.freeze()`, which preserves the old shallow\nfreeze. For example:\n\n```ts\nimport { z } from \"zod\";\n\nconst Settings = z.object({\n  host: z.string(),\n  port: z.number(),\n});\ntype Settings = z.infer\u003Ctypeof Settings>;\n\nconst Environment = Settings.extend({ port: z.coerce.number() });\nconst settings = Object.freeze(Environment.parse(process.env));\nconst updated = Object.freeze(Settings.parse({ ...settings, port: 9090 }));\n```\n\nKeep environment decoding separate from strict settings validation when\nreplacing `factory.coerce()` and `config.update()`. Updates merge parsed\nsettings and revalidate them; do not rerun input transforms on their output\nunless those transforms accept that output. Boolean and JSON environment\nvalues need the explicit decoding described above.\n\nAfter migrating, run the project's typecheck and tests, including invalid\ninputs, absent\u002Fdefaulted options, boolean flags, and settings updates used by\nthe project.\n\n## Rules\n\n- Never edit the webappwiz repository from this project's thread.\n- Never copy its source into this project.\n- Reading the table is the whole check, and it is cheap. Do it before adding a\n  dependency, not after.\n","# Using webappwiz\n\n`webappwiz` is the parts of a web app that get written again every time, behind\ninterfaces a test can replace. One package, one subpath per module. Before\nwriting any of that here, find out whether it already exists there.\n\nIts README carries the whole catalogue, a table of every subpath and what it is\nfor. Read it from `node_modules\u002Fwebappwiz\u002FREADME.md`, or, in a project that has\nnot installed it yet, from\n`https:\u002F\u002Fraw.githubusercontent.com\u002Fjaredjj3\u002Fwebappwiz\u002Fmain\u002Fpackages\u002Fwebappwiz\u002FREADME.md`.\n\nNothing in the table is close: say so in a line and write it here. Something is:\nread that module's own README and the exports of its `index.ts`, and judge\nagainst what is actually needed rather than the one-line blurb.\n\n## It fits\n\n`bun add webappwiz` and import the subpath. There is no package entry point, so\nimport `webappwiz\u002Ftime`, never `webappwiz`. Fakes live under `\u002Ftesting` beside\nwhat they replace.\n\n## It nearly fits\n\nDo not vendor it, fork it, or patch `node_modules`. Write what this project\nneeds here so nobody is blocked, leave a `TODO: webappwiz\u002F\u003Csubpath> once \u003Cgap>`\non it, and hand the gap over: print the block below and tell the user to give it\nto an agent working on the webappwiz repo.\n\n```markdown\nIn `packages\u002Fwebappwiz\u002F\u003Csubpath>`: \u003Cthe gap, in a sentence>.\n\nWanted by \u003Cthis project> for \u003Cthe usecase, concretely>.\n\nWhat is there now: \u003Cthe export that comes closest, and where it stops>.\nWhat is missing: \u003Cthe smallest change that closes the gap: one more method, a\nwidened parameter, another implementation of an interface>.\nCalled like: \u003Cthe call site, written the way the caller wants to write it>.\n```\n\nDescribe the gap and stop. Do not design the API in the handoff: that repo has a\nstyle guide and a review, and neither of them is here.\n\n## It does not fit\n\nOne line naming the subpath you read and why it is not the one, then write it\nhere. A wrong module taken up is worse than one written twice.\n\n## Credentials\n\nAn API key, token or other secret a project's code needs comes from\n`webappwiz\u002Fcreds`. Code reads it through `Credentials`, over a list of\nsources it chooses for each place the app runs; the first source with a\nvalue wins. Never put a secret in source, a config file, a test, or a\ncommand line, never write a `.env` file yourself, and never ask for one in\nchat.\n\n### Which source, where\n\nFrom most to least locked down:\n\n1. **The system's secret store**, `SystemSecretStore`: the Keychain,\n   Credential Manager, or a Linux secret service. Encrypted at rest, held\n   apart from files and the environment, so no file read, `env` dump, child\n   process, or agent sees a value. Use it on a person's machine, and only it.\n   - `SystemSecretStore.forProject()`, kept as `webappwiz:\u003Cproject>`: keys\n     the app itself uses, like a Stripe test key. One project's keys are\n     never another's.\n   - `SystemSecretStore.device()`, kept as `webappwiz`: keys that belong to\n     the person and serve many projects, like the tokens scry runs on. Wider\n     reach, so only for keys that really are shared.\n2. **A hosted secrets manager** (1Password, Vault, AWS or GCP Secret\n   Manager), as a source of the app's own: any object with a `label` and an\n   async `get(name)`. Fetched at runtime and access-controlled. Use it where\n   the app is deployed, when the project has one.\n3. **The environment**, `Environment`: how CI, containers and hosting\n   platforms hand a deployed app its secrets. Every child process inherits\n   it, and it shows up in crash reports and debug dumps. Use it where the\n   app is deployed. On a person's machine it means exports in a shell\n   profile, which every program they run can read, so leave it out of the\n   development list.\n4. **A `.env` file**, `DotenvFile(path)`: plaintext on disk, one mistake\n   from being committed, and read by any tool or agent that opens it. Use it\n   only where a deploy target insists on one, never on a person's machine.\n   Under Bun, `.env` files are loaded into the environment already, so\n   `Environment` covers them there.\n\nHow the app tells development from production, and which sources each\nlists, is the project's choice: ask the user when the project does not\nalready say. The usual lists:\n\n```ts\nimport {\n\tCredentials,\n\tEnvironment,\n\tSystemSecretStore,\n} from \"webappwiz\u002Fcreds\";\n\nconst credentials =\n\tprocess.env.APP_ENV === \"development\"\n\t\t? new Credentials([\n\t\t\t\tawait SystemSecretStore.forProject(),\n\t\t\t\tSystemSecretStore.device(),\n\t\t\t])\n\t\t: new Credentials([new Environment()]);\nconst key = await credentials.require(\"STRIPE_SECRET_KEY\");\n```\n\nA tool that reads only its environment, like Prisma, Vite or `wrangler`,\nnever calls `Credentials`. In development, run it through\n`bunx @webappwiz\u002Fcli creds run -- \u003Ccommand>`, which hands it the stored\nkeys for that run alone, usually from a `package.json` script; never reach\nfor a `.env` file or an export to feed it.\n\n`Credentials` is a source itself, so a fallback pattern of the project's\nown is a list of lists: `new Credentials([vault, new\nCredentials([new Environment(), new DotenvFile(\".env\")])])` reads the\nvault, then the environment, then the file. `forProject()` finds the\nstore's name itself, so never write a project name into code. Take the\n`Credentials` as a dependency, so a test hands in one over\n`FakeSecretStore` from `webappwiz\u002Fcreds\u002Ftesting`.\n\n### Adding one\n\n1. Name it in `.wiz\u002Fconfig.ts`, by its environment variable name, with what\n   it is for. `creds add` takes any name, but a named one shows as missing\n   until someone keeps it, so whoever clones the project knows it is needed:\n\n   ```ts\n   export default {\n   \tcredentials: { names: { STRIPE_SECRET_KEY: \"Stripe, for checkout\" } },\n   };\n   ```\n\n2. Run `bunx @webappwiz\u002Fcli creds list` to see which are missing. It\n   never prints a value. For each missing one, ask the user to run\n   `bunx @webappwiz\u002Fcli creds add \u003CNAME>` themselves, with `--device` for a\n   key that is theirs rather than the project's: it asks for the value at a\n   prompt that shows nothing, and refuses when there is no terminal, so you\n   cannot and should not run it for them. `creds remove \u003CNAME>` deletes\n   one.\n\nNothing reads a value back out for you to see, and nothing should: do not\nprint one, log one, or look one up with the system's own tools\n(`security`, `secret-tool`, `cmdkey`). Code that needs a value reads it\nitself.\n\n## Publishing from GitHub Actions\n\nA release whose npm packages publish `via: githubActions()` (from\n`webappwiz\u002Fship`) publishes from the generated workflow, with no token and no\n2FA code. npm allows that only once each package has a trusted publisher\nentry naming the repository and the workflow, and making one takes the\nuser's own npm login in a browser. You cannot do it for them, so when you\nadd `via: githubActions()`, or a ship fails with \"npm refused the run\",\nguide the user through it:\n\n1. Have them run the project's trust command once: `bunx @webappwiz\u002Fcli ship\n   trust` when the release is declared in `.wiz\u002Fship.ts`, or the project's\n   own command that calls `release.trust()`. It runs `npm trust github` for\n   each package.\n2. Tell them npm asks them to authenticate in a browser, and that ticking\n   \"skip two-factor authentication for the next 5 minutes\" there lets the\n   other packages go through without asking again.\n3. A package must already be on npm before it can trust anything, so a\n   package that has never been published goes out once the old way first.\n4. Then they ship as usual. A package that already trusts another workflow\n   fails, and the error says how to clear it.\n\n## Updating\n\n`bunx @webappwiz\u002Fcli update` rewrites every webappwiz dependency under the\ndirectory to one version, since they are released together and a project\nrunning two of them at different versions is running a combination nobody\ntested. The version is the one you invoked, which is what `bunx` is for.\nInstalled skills and copied rules are refreshed with it, and local edits to\nthose do not survive.\n\nIt edits manifests and stops. Nothing is installed until you run `bun install`\nyourself, and nothing is verified until you run this project's typecheck and\ntests.\n\nWhat broke is read the same way as anything else here: the module's own README\nand the exports of its `index.ts`, not the one-line blurb and not a guess. If\nthe new version dropped what this project was using, check the migrations below\nfirst. For removals not covered there, that is a gap: leave the\nlocal code working, and hand it over with the block above. Do not vendor,\nfork, or patch `node_modules` to get the build green.\n\n### Migrating removed `webappwiz\u002Ft` and `webappwiz\u002Fconfig`\n\nThese modules have been removed in favor of Zod and ordinary typed settings.\nIf the project imports either subpath, migrate those callers as part of the\nupdate. This is an intentional replacement, so do not request their restoration\nthrough the gap handoff above.\n\nAdd Zod as a direct dependency in each package importing it (`bun add zod`),\nthen replace `import { t } from \"webappwiz\u002Ft\"` with\n`import { z } from \"zod\"`. Primitive, object, array, enum, optional, and\nnullable builders have Zod equivalents. Replace `Infer\u003Ctypeof schema>` with\n`z.infer\u003Ctypeof schema>`; replace custom `Schema` implementations and\n`SchemaBase` subclasses with Zod schemas, refinements, or transforms.\n\nCheck behavior at each input boundary:\n\n- `.parse()` and `.safeParse()` validate through Zod. Replace\n  `SchemaError.path` and `.reason` with `ZodError.issues`, using each issue's\n  `path` and `message`. For `validate(schema, value)`, use\n  `schema.parse(value)` when the schema is Zod; for other libraries, use\n  their parser or the Standard Schema interface.\n- Zod has no per-schema `.coerce(raw)` method. Use\n  `z.coerce.number().parse(raw)` for numeric strings. Decode JSON strings\n  before validating object or array schemas, handling malformed JSON too.\n- `webappwiz\u002Fcmd` still accepts Standard Schema. It passes strings to the\n  schema, so numeric args and options need `z.coerce.number()`. Declare an\n  on\u002Foff switch as `.option(\"name\", z.boolean(), { default: false })`: it is\n  false unless given, `--name=false` turns it off, and a bare `--name` never\n  takes the next argument as its value. `z.coerce.boolean()` converts\n  `\"false\"` to true and is not a replacement.\n  Command validation remains synchronous and reports an ordinary `Error`\n  with the first issue's dotted path and message.\n- Zod numbers reject infinity. Object schemas still strip extra keys, but\n  missing optional properties are omitted rather than added as `undefined`;\n  their inferred object keys are optional too. Check callers that enumerate\n  keys or rely on exact error wording.\n\nReplace `Config.factory(shape)` with `z.object(shape)`, `config.get(\"key\")`\nwith typed property access, and `config.toRecord()` with the parsed object.\nUse `z.infer\u003Ctypeof Settings>` instead of `InferConfig`. If freezing matters,\nwrap the parsed object in `Object.freeze()`, which preserves the old shallow\nfreeze. For example:\n\n```ts\nimport { z } from \"zod\";\n\nconst Settings = z.object({\n  host: z.string(),\n  port: z.number(),\n});\ntype Settings = z.infer\u003Ctypeof Settings>;\n\nconst Environment = Settings.extend({ port: z.coerce.number() });\nconst settings = Object.freeze(Environment.parse(process.env));\nconst updated = Object.freeze(Settings.parse({ ...settings, port: 9090 }));\n```\n\nKeep environment decoding separate from strict settings validation when\nreplacing `factory.coerce()` and `config.update()`. Updates merge parsed\nsettings and revalidate them; do not rerun input transforms on their output\nunless those transforms accept that output. Boolean and JSON environment\nvalues need the explicit decoding described above.\n\nAfter migrating, run the project's typecheck and tests, including invalid\ninputs, absent\u002Fdefaulted options, boolean flags, and settings updates used by\nthe project.\n\n## Rules\n\n- Never edit the webappwiz repository from this project's thread.\n- Never copy its source into this project.\n- Reading the table is the whole check, and it is cheap. Do it before adding a\n  dependency, not after.\n",{"name":5,"version":24,"description":7},"0.0.59","main","6b0f2e64ea56222eb80a119adaad31d841e5b65a","skills\u002Fwebappwiz",0,"https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz","https:\u002F\u002Fgithub.com\u002Fjaredjj3","jaredjohnson.dev","Software makes life better","2026-11-01 00:07:53",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add jaredjj3\u002Fwebappwiz --skill webappwiz",{"tool":40,"command":41},"bunx","bunx skills add jaredjj3\u002Fwebappwiz --skill webappwiz",{"tool":43,"command":44},"pnpm","pnpm dlx skills add jaredjj3\u002Fwebappwiz --skill webappwiz","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz\u002Fblob\u002Fmain\u002Fskills\u002Fwebappwiz\u002FSKILL.md",true,[],[49,56,63,70],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79J272FDFDPEZ6WBMP9KR8E","scry","Write, update, and remove the scry rules in this project's .wiz\u002Fscry, which `wiz scry` checks code against like a linter. Use when the user explicitly asks for a rule, or asks for a style or convention change across the codebase that a rule could enforce from now on (\"stop using default exports\", \"comments should say why\"). Also use when asked to scry a change or run `wiz scry`.","https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz\u002Fblob\u002Fmain\u002Fskills\u002Fscry\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79J217G3RTZN1A6HMFTQB4H","splates","Use the splates CLI to land your work on trunk, or a base branch given as an argument, from an isolated git worktree without pull requests. Read this before investigating anything that may lead to a code change in a splates repository, since it decides where the work happens, and whenever you need to add, claim, merge, remove, list, show, locate, or defer a task, or queue, pick up, link, or reorder a task for later, or work down a lane of them. Also read it before asking the user a question or proposing anything in a splates repository, with a task open or not.","https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsplates\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79J1SXVK09C6JY8BDPSX2P6","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", or \"switch to --preset\".","https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[],{"skillNo":71,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79J1QQCJJ8YWN8SFTXWV15F","https:\u002F\u002Fgithub.com\u002Fjaredjj3\u002Fwebappwiz\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscry\u002FSKILL.md",[],[]]