[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GNJGC0CK54RFFQ1HBQYAC":3,"skill-same:01M79GNJGC0CK54RFFQ1HBQYAC":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79GNJGC0CK54RFFQ1HBQYAC","saasaloy-config",null,"Work with @repo\u002Fconfig — the values this project checks into its repo and ships identically to every environment. Use when a value needs a single home, when deciding whether something belongs in config or in .env, when adding a section for a capability, when a project override is not taking effect, or when the owner says \"where do I change the product name\", \"where do I put this constant\", \"config or env\".","mimukit\u002Fsaasaloy","mimukit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11677026?v=4","01M79GFSERAQQ77QPQMC1N0Y6M","Mukitul Islam Mukit","01M79GFSFA4WMGEEBHA68N59WV",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Ftemplates\u002Fbase\u002F_agents\u002Fskills\u002Fsaasaloy-config\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: saasaloy-config\ndescription: Work with @repo\u002Fconfig — the values this project checks into its repo and ships identically to every environment. Use when a value needs a single home, when deciding whether something belongs in config or in .env, when adding a section for a capability, when a project override is not taking effect, or when the owner says \"where do I change the product name\", \"where do I put this constant\", \"config or env\".\n---\n\n# saasaloy-config — one home for a checked-in value\n\n`@repo\u002Fconfig` is a frozen plain object of values this project checks into its repo. Read it\nwith a plain import, from an app, a capability or a React island alike:\n\n```ts\nimport { config } from \"@repo\u002Fconfig\";\n\nconfig.app.name;\nconfig.app.locale;\nconfig.auth.adminRole; \u002F\u002F once `auth` is installed\n```\n\nThere is no factory, no `env` argument, no async and no I\u002FO. The object is built once at\nmodule load and frozen, so a bundler can inline it.\n\n## The rule: config or `.env`\n\n- **`env`** owns a value the platform supplies per deployment, secret or not. A database\n  URL, an API origin, a Stripe key, a provider selection.\n- **`config`** owns a value checked into the repo that is the same in every deployment. The\n  product name, the locale, a role string.\n\n**The test.** Two deployments of *this* project — production and staging. If the value can\ndiffer between them, it is `env`. If it cannot, it is `config`. A value that differs between\ntwo *different* projects but not between one project's environments is `config`.\n\n`packages\u002Fconfig` imports nothing, `@repo\u002Fenv` included, so a section cannot read an env\nvar. A value derived from both channels is derived where it is used, not in a section file.\n\n## Not the landing copy\n\nEverything on the landing page, prices and tier ids included, lives in\n`packages\u002Fui\u002Fsrc\u002Fcontent\u002Flanding.ts`, and `saasaloy-landing-copy` owns it. `config` holds\nthe facts more than one workspace reads: the product name, the locale, the legal paths, and\nwhatever an installed module's section adds.\n\n## The four files\n\n| Path | Who owns it |\n|------|-------------|\n| `src\u002Fproject.ts` | **You.** The only file here you are expected to edit. Nothing overwrites it. |\n| `src\u002Fsections.ts` | The registry. `saasaloy add` patches one line into it; do not hand-edit the array. |\n| `src\u002Fsections\u002F\u003Ckey>.ts` | The module that installed it (`app` belongs to the base template). |\n| `src\u002Fdefine.ts` | The base template. The composition core. |\n\n## Changing a value\n\nEdit `src\u002Fproject.ts`. It is typed as a partial of the composed shape, so a key no\ninstalled section defines is a `typecheck` error rather than a value nothing reads.\n\n```ts\nexport const project: ProjectOverride = {\n  app: { name: \"Ledgerly\", locale: \"en-GB\" },\n};\n```\n\n**The merge goes one level below the section, and no deeper.** `app: { name: \"...\" }`\nreplaces the name and keeps the rest of `app`. A nested record or an array is replaced\nwhole, so `app: { legal: { termsPath: \"\u002Flegal\u002Fterms\" } }` must also name `privacyPath`.\n\nRun `pnpm typecheck` after an edit. That is the only validation there is: the values are\nliterals in this repo, so a wrong one is a review problem rather than a runtime one.\n\n## Adding a section\n\nA capability contributes one section, keyed by the module name. The module ships one file\ninto `packages\u002Fconfig\u002Fsrc\u002Fsections\u002F\u003Ckey>.ts` and registers it with a `plugin-array` patch:\n\n```ts\n\u002F\u002F packages\u002Fconfig\u002Fsrc\u002Fsections\u002Fshop.ts\nimport { defineSection } from \"@repo\u002Fconfig\u002Fdefine\";\n\nexport function shopConfig() {\n  return defineSection(\"shop\", {\n    defaultCurrency: \"USD\",\n    maxCartItems: 50,\n  });\n}\n```\n\n```jsonc\n\u002F\u002F the module's registry-item.json\n{\n  \"file\": \"packages\u002Fconfig\u002Fsrc\u002Fsections.ts\",\n  \"kind\": \"plugin-array\",\n  \"exportName\": \"sections\",\n  \"arrayProp\": \"sections\",\n  \"call\": \"shopConfig\",\n  \"import\": { \"name\": \"shopConfig\", \"from\": \".\u002Fsections\u002Fshop\" }\n}\n```\n\nFour rules:\n\n- **The key is the module name**, flat, and unique. `saasaloy add` refuses two modules\n  claiming one key and names both, and the base's own `app` is taken; at runtime a\n  duplicate throws at module load. The file name and the key passed to `defineSection`\n  must match, and `add` refuses a section file where they differ.\n- **The section file lives in `packages\u002Fconfig`, not in the capability.** `@repo\u002Fconfig` is\n  the leaf of the dependency graph — it imports nothing, so everything may import it,\n  including the capability whose values these are. A section inside the capability would\n  invert that and cycle.\n- **Import the helper by subpath**, `@repo\u002Fconfig\u002Fdefine`, never by relative path.\n- **A section never reads another section.** They are composed side by side. Apply a\n  fallback between two sections where the value is used, the way\n  `apps\u002Fapi\u002Fsrc\u002Fsubscription-store.ts` does for `config.subscription.appName || config.app.name`.\n\n## When an override does not take effect\n\n1. **The section is not installed.** `config.shop` only exists once `saasaloy add shop`\n   has patched `src\u002Fsections.ts`. Check the array.\n2. **You edited a section file, not `project.ts`.** A module-owned section file may be\n   rewritten by `saasaloy update`. Move the edit to `project.ts`.\n3. **You expected a deep merge.** One level below the section is the whole rule; a nested\n   record is replaced whole.\n4. **Something reads the value at build time.** A Node config file (`astro.config.mjs`,\n   `vite.config.ts`) is not part of the app graph and keeps its own literals on purpose.\n\n## What is not here\n\n- **A runtime override channel.** A value that must change per deployment is an `env` value\n  by definition.\n- **Schema validation.** `typecheck` is the gate.\n- **A `\u003CCAP>_PROVIDER` key.** Provider selection stays in `env`.\n- **The dev ports.** 3000\u002F3001\u002F4000 are read by Node config files at build time.\n","# saasaloy-config — one home for a checked-in value\n\n`@repo\u002Fconfig` is a frozen plain object of values this project checks into its repo. Read it\nwith a plain import, from an app, a capability or a React island alike:\n\n```ts\nimport { config } from \"@repo\u002Fconfig\";\n\nconfig.app.name;\nconfig.app.locale;\nconfig.auth.adminRole; \u002F\u002F once `auth` is installed\n```\n\nThere is no factory, no `env` argument, no async and no I\u002FO. The object is built once at\nmodule load and frozen, so a bundler can inline it.\n\n## The rule: config or `.env`\n\n- **`env`** owns a value the platform supplies per deployment, secret or not. A database\n  URL, an API origin, a Stripe key, a provider selection.\n- **`config`** owns a value checked into the repo that is the same in every deployment. The\n  product name, the locale, a role string.\n\n**The test.** Two deployments of *this* project — production and staging. If the value can\ndiffer between them, it is `env`. If it cannot, it is `config`. A value that differs between\ntwo *different* projects but not between one project's environments is `config`.\n\n`packages\u002Fconfig` imports nothing, `@repo\u002Fenv` included, so a section cannot read an env\nvar. A value derived from both channels is derived where it is used, not in a section file.\n\n## Not the landing copy\n\nEverything on the landing page, prices and tier ids included, lives in\n`packages\u002Fui\u002Fsrc\u002Fcontent\u002Flanding.ts`, and `saasaloy-landing-copy` owns it. `config` holds\nthe facts more than one workspace reads: the product name, the locale, the legal paths, and\nwhatever an installed module's section adds.\n\n## The four files\n\n| Path | Who owns it |\n|------|-------------|\n| `src\u002Fproject.ts` | **You.** The only file here you are expected to edit. Nothing overwrites it. |\n| `src\u002Fsections.ts` | The registry. `saasaloy add` patches one line into it; do not hand-edit the array. |\n| `src\u002Fsections\u002F\u003Ckey>.ts` | The module that installed it (`app` belongs to the base template). |\n| `src\u002Fdefine.ts` | The base template. The composition core. |\n\n## Changing a value\n\nEdit `src\u002Fproject.ts`. It is typed as a partial of the composed shape, so a key no\ninstalled section defines is a `typecheck` error rather than a value nothing reads.\n\n```ts\nexport const project: ProjectOverride = {\n  app: { name: \"Ledgerly\", locale: \"en-GB\" },\n};\n```\n\n**The merge goes one level below the section, and no deeper.** `app: { name: \"...\" }`\nreplaces the name and keeps the rest of `app`. A nested record or an array is replaced\nwhole, so `app: { legal: { termsPath: \"\u002Flegal\u002Fterms\" } }` must also name `privacyPath`.\n\nRun `pnpm typecheck` after an edit. That is the only validation there is: the values are\nliterals in this repo, so a wrong one is a review problem rather than a runtime one.\n\n## Adding a section\n\nA capability contributes one section, keyed by the module name. The module ships one file\ninto `packages\u002Fconfig\u002Fsrc\u002Fsections\u002F\u003Ckey>.ts` and registers it with a `plugin-array` patch:\n\n```ts\n\u002F\u002F packages\u002Fconfig\u002Fsrc\u002Fsections\u002Fshop.ts\nimport { defineSection } from \"@repo\u002Fconfig\u002Fdefine\";\n\nexport function shopConfig() {\n  return defineSection(\"shop\", {\n    defaultCurrency: \"USD\",\n    maxCartItems: 50,\n  });\n}\n```\n\n```jsonc\n\u002F\u002F the module's registry-item.json\n{\n  \"file\": \"packages\u002Fconfig\u002Fsrc\u002Fsections.ts\",\n  \"kind\": \"plugin-array\",\n  \"exportName\": \"sections\",\n  \"arrayProp\": \"sections\",\n  \"call\": \"shopConfig\",\n  \"import\": { \"name\": \"shopConfig\", \"from\": \".\u002Fsections\u002Fshop\" }\n}\n```\n\nFour rules:\n\n- **The key is the module name**, flat, and unique. `saasaloy add` refuses two modules\n  claiming one key and names both, and the base's own `app` is taken; at runtime a\n  duplicate throws at module load. The file name and the key passed to `defineSection`\n  must match, and `add` refuses a section file where they differ.\n- **The section file lives in `packages\u002Fconfig`, not in the capability.** `@repo\u002Fconfig` is\n  the leaf of the dependency graph — it imports nothing, so everything may import it,\n  including the capability whose values these are. A section inside the capability would\n  invert that and cycle.\n- **Import the helper by subpath**, `@repo\u002Fconfig\u002Fdefine`, never by relative path.\n- **A section never reads another section.** They are composed side by side. Apply a\n  fallback between two sections where the value is used, the way\n  `apps\u002Fapi\u002Fsrc\u002Fsubscription-store.ts` does for `config.subscription.appName || config.app.name`.\n\n## When an override does not take effect\n\n1. **The section is not installed.** `config.shop` only exists once `saasaloy add shop`\n   has patched `src\u002Fsections.ts`. Check the array.\n2. **You edited a section file, not `project.ts`.** A module-owned section file may be\n   rewritten by `saasaloy update`. Move the edit to `project.ts`.\n3. **You expected a deep merge.** One level below the section is the whole rule; a nested\n   record is replaced whole.\n4. **Something reads the value at build time.** A Node config file (`astro.config.mjs`,\n   `vite.config.ts`) is not part of the app graph and keeps its own literals on purpose.\n\n## What is not here\n\n- **A runtime override channel.** A value that must change per deployment is an `env` value\n  by definition.\n- **Schema validation.** `typecheck` is the gate.\n- **A `\u003CCAP>_PROVIDER` key.** Provider selection stays in `env`.\n- **The dev ports.** 3000\u002F3001\u002F4000 are read by Node config files at build time.\n",{"name":5,"description":7},"main","5ecf3d110b216ef678e06a1630f6b63a8e730bb5","packages\u002Fcli\u002Ftemplates\u002Fbase\u002F_agents\u002Fskills\u002Fsaasaloy-config",0,"https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy","https:\u002F\u002Fsaasaloy.com","https:\u002F\u002Fgithub.com\u002Fmimukit","https:\u002F\u002Fmimukit.com","Senior Software Engineer · 9+ yrs Fullstack (TS\u002FNode\u002FReact) · AI integrations, distributed systems · Building @saasaloy & @codealoy · Bangladesh 🇧🇩 \u002F Remote","2026-11-13 20:39:28",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add mimukit\u002Fsaasaloy --skill saasaloy-config",{"tool":40,"command":41},"bunx","bunx skills add mimukit\u002Fsaasaloy --skill saasaloy-config",{"tool":43,"command":44},"pnpm","pnpm dlx skills add mimukit\u002Fsaasaloy --skill saasaloy-config","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Ftemplates\u002Fbase\u002F_agents\u002Fskills\u002Fsaasaloy-config\u002FSKILL.md",true,[],[49,56,63,70,77,83],{"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},"01M7BE75C34XHSPVJNQC8FY4Q0","saasaloy-subscription","Runbook for the subscription capability — provider-agnostic subscriptions in packages\u002Fsubscription, with a plan file, a projection table, a billable-subject file, plan entitlements and per-provider modules. Use when adding a plan, adding a plan feature or a numeric limit, gating an API route with requireFeature or requireWithinLimit, reading the 402 it returns, working out why a subject resolves to the free plan, wiring a checkout or portal route, reading a SubscriptionError, choosing or switching SUBSCRIPTION_PROVIDER, registering a webhook in the vendor's dashboard, writing a third subscription provider, or upgrading a project that still has `billing` installed.","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fmodules\u002Fsubscription\u002Fskills\u002Fsaasaloy-subscription\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},"01M7BE68MJ8H47JZKTBDFYR6JD","saasaloy-notification","Runbook for the notification module, in-app notifications for apps\u002Fapp. It owns the notifications and notification_opt_outs tables, notify() in apps\u002Fapi\u002Fsrc\u002Flib\u002Fnotify.ts, the \u002Fnotifications api routes, the bell in the app header, the sidebar badge, the \u002Fnotifications page with Inbox and Preferences tabs, the notification config section, and the daily prune. Use when sending a notification from an api route, adding or changing a category, changing retention, debugging a badge or bell count that does not move, or removing the module.","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fmodules\u002Fnotification\u002Fskills\u002Fsaasaloy-notification\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},"01M7BE53PDQV0YDPG8RNVGTPEQ","saasaloy-cms","Runbook for the cms module, the in-house CMS behind apps\u002Fadmin. Covers code-defined collections, the Tiptap editor, drafts, revisions and redirects, the publish-time renderer, the public blog on apps\u002Fweb and its 60-second cache. Use when adding a collection or a field, rendering a stored body, reusing the editor, renderer or media field from another module, moving the blog to another path, re-rendering live posts after a renderer upgrade or a STORAGE_PUBLIC_URL change, or working out why a published post is not live yet.","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fmodules\u002Fcms\u002Fskills\u002Fsaasaloy-cms\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79GQ03M63V5EKSST92B3S5X","saasaloy-beta","The beta module's own procedure.","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Ftest\u002Ffixtures\u002Fregistry-clean\u002Fbeta\u002Fsaasaloy-beta\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"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":80,"categories":81,"keywords":82,"publishedAt":19},"01M79GPXV3K8YF3M4VA0KGVE0B","helper","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Ftest\u002Ffixtures\u002Fregistry-broken\u002Fbad-skill\u002Fhelper\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79GPR8EVS1YX0W8X33Q9YD8","saasaloy-update","Runbook for an AI agent that updates this project to a newer Saasaloy CLI and newer module versions with saasaloy update. Use when the owner says \"update saasaloy\", \"upgrade the CLI\", \"pull the latest modules\", \"update the base template\", \"work the merge plan\", \"clear the update notes\", when saasaloy update or saasaloy outdated --check exits 3 or 2, when a merge plan or .saasaloy\u002Fmerge-plan.md is handed to you, or when an adopted project takes its first update. Covers the CLI upgrade, the preview, --out, the file merges, the update notes and \"Notes that may apply\", --resolved and --done, a file deleted locally and --restore, a three-way or two-way base, an update that skips releases, --from, the verify commands, and the exit codes.","https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Ftemplates\u002Fbase\u002F_agents\u002Fskills\u002Fsaasaloy-update\u002FSKILL.md",[],[]]