[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GJC64D4D06JR0AYBXPNK6":3,"skill-same:01M79GJC64D4D06JR0AYBXPNK6":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},"01M79GJC64D4D06JR0AYBXPNK6","saasaloy-e2e",null,"Write and run the project's Playwright end-to-end flows in packages\u002Fe2e (@repo\u002Fe2e). Use when adding a browser flow, gating a spec on an installed module, debugging a red e2e run, signing a spec in as the seeded admin, or installing the browser.","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\u002Fmodules\u002Fe2e\u002Fskills\u002Fsaasaloy-e2e\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: saasaloy-e2e\ndescription: Write and run the project's Playwright end-to-end flows in packages\u002Fe2e (@repo\u002Fe2e). Use when adding a browser flow, gating a spec on an installed module, debugging a red e2e run, signing a spec in as the seeded admin, or installing the browser.\n---\n\n# saasaloy-e2e\n\n`packages\u002Fe2e` holds the project's browser suite. It starts the apps, drives them with headless Chromium, and stops every process it started. It is the only workspace in the repo that Playwright reads, and `pnpm test` (Vitest) never collects a file from it: the root `vitest.config.ts` leaves `packages\u002Fe2e` out.\n\n## The two commands\n\n```sh\npnpm e2e:install    # download Chromium, once per machine\npnpm e2e            # migrate and seed the database, start the apps, run the flows\n```\n\n`pnpm e2e:install` is not a `postinstall`. Downloading ~150MB on every `pnpm install` in every checkout is a cost a project should opt into, so the browser is missing until you ask for it, and `pnpm e2e` fails with that exact command in the message when it is.\n\n`pnpm e2e:ui` opens Playwright's watch UI. It needs a desktop, so it is useless on a headless box; `pnpm e2e` is the headless path and needs nothing.\n\nBefore the first run, every app needs its `.env`. Run `saasaloy env` (or copy `packages\u002Fenv\u002F.env.example` to `packages\u002Fenv\u002F.env`; the local defaults are enough), then `pnpm env:setup`. `pnpm e2e` names the missing file and that command when one is absent.\n\n## What one run does, in order\n\n1. `prepare.ts` checks Chromium is downloaded and every app it will start has its `.env`.\n2. When `database` is installed, `prepare.ts` runs `pnpm db:setup`, then `pnpm db:seed`.\n3. Playwright starts one dev server per installed app and waits for each to answer.\n4. The specs run, one at a time.\n5. `global-teardown.ts` runs `pnpm db:drop`, **on CI only**.\n\nSteps 1 and 2 are a script rather than a `globalSetup` hook because of step 3. The api Worker reads `apps\u002Fapi\u002F.env` when it boots, so a `DATABASE_URL` written after the server started is a value it never sees.\n\n## Ports\n\n| App | Port | Started when |\n| --- | --- | --- |\n| `apps\u002Fapi` | 4000 | `api` is installed |\n| `apps\u002Fweb` | 3000 | always, it is the base app |\n| `apps\u002Fadmin` | 3001 | `admin` is installed |\n\nThese are the project's pinned dev ports, the same ones in `AGENTS.md`. Off CI, `reuseExistingServer` is on, so a `pnpm dev` you already have running is used instead of a second one on a busy port. On CI it is off, because reusing would hide a start-up failure.\n\nPlaywright waits on `http:\u002F\u002Flocalhost:4000\u002Fhealth` for the api, not on its origin. The Worker answers `GET \u002F` with a 404 envelope, and Playwright reads any status at or above 400 as \"not ready\".\n\n## Adding a flow\n\n1. Write `specs\u002F\u003Cname>.spec.ts`.\n2. Wrap it in a `test.describe` that declares the modules it needs as tags.\n3. Add any new tag to `SPEC_TAGS` in `lib\u002Fproject.ts`.\n\n```ts\nimport { expect, test } from \"@playwright\u002Ftest\";\n\nimport { URLS } from \"..\u002Flib\u002Fproject.ts\";\n\ntest.describe(\"api health\", { tag: [\"@api\"] }, () => {\n  test(\"the api answers\", async ({ request }) => {\n    const response = await request.get(`${URLS.api}\u002Fhealth`);\n    expect(response.status()).toBe(200);\n  });\n});\n```\n\nFour rules, each one load-bearing:\n\n- **A tag is a module name, and nothing else.** `playwright.config.ts` turns every tag in `SPEC_TAGS` whose module is absent into `grepInvert`, so the spec is never collected. A tag that names no module is never in `installed`, so its spec would never run anywhere and the suite would still report green.\n- **Never skip on a missing route.** A `test.skip()` when a page 404s turns a broken route into a green run, which is the exact failure this suite exists to catch. Gate on the tag, which is decided before anything runs.\n- **Wait for the island before you type.** A form on `apps\u002Fweb` is a React island on a static Astro page. A value typed before hydration is thrown away when React mounts the controlled input, and the form then submits an empty value. Astro marks an island `\u003Castro-island ssr>` until it hydrates, so wait for the island that holds your field to lose it: `await expect(page.locator(\"astro-island[ssr]\").filter({ has: field })).toHaveCount(0)`. `waitlist.spec.ts` is the worked example.\n- **Imports carry the `.ts` extension.** `prepare.ts` runs under `node`, whose type stripping resolves the real file, so the whole workspace keeps one import style.\n\n## The seeded admin and the rows a spec writes\n\nThe admin specs sign in as `superadmin@example.test` with the password `saasaloy-dev-password`, `SEED_ADMIN` in `lib\u002Fproject.ts`. The suite creates no account of its own. The `auth` module's seed slices write that user, and `pnpm db:seed` upserts it back to its slice values before every run, so a password changed by hand is reset and the account is always a superadmin. Change `SEED_ADMIN` only together with `packages\u002Fdb\u002Fsrc\u002Fseed\u002Fslices\u002Fusers.ts` and `accounts.ts`.\n\nA spec that needs a signed-in admin but is not about the login screen signs in at the start of the test through the same form `admin-login.spec.ts` drives. `admin-login.spec.ts` itself starts from no cookie on purpose: a login flow that starts from a saved session tests the session.\n\nEvery **other** row a spec writes is unique, with `uniqueEmail()` from `lib\u002Ffixtures.ts`. There is no cleanup step, on purpose: a teardown that deletes rows does not run when a run crashes, so the next run starts poisoned and the failure looks like a real bug a day later. A unique row cannot collide with anything.\n\n## The flows that ship\n\n| Spec | Tags | What it proves |\n| --- | --- | --- |\n| `health.spec.ts` | `@api` | The Worker started and `GET \u002Fhealth` answers the documented body. The floor. |\n| `waitlist.spec.ts` | `@waitlist` | A real browser fills the real form on `apps\u002Fweb`, the island posts, and the route answers 201. |\n| `admin-login.spec.ts` | `@admin` `@auth` | The login form signs the seeded admin in, the guard redirects, and `GET \u002Fadmin\u002Fusers` answers 200. |\n| `admin-unauthenticated.spec.ts` | `@admin` `@auth` | The same guarded route answers 401 with the api's error envelope when nobody is signed in. |\n\n`admin-unauthenticated.spec.ts` is its own flow rather than a second assertion, because the admin SPA's guard runs in the browser and would hide a server that stopped checking.\n\n**`waitlist.spec.ts` needs the form on a page.** `saasaloy add waitlist` writes the block and the island and then stops; the `saasaloy-waitlist` skill's Wire-up section has the two lines that place it. The spec says so in its failure message rather than skipping.\n\n## When a run is red\n\n- The failing step is on **stdout**. The `list` reporter runs first for exactly that reason, so a headless box needs nothing else.\n- `playwright-report\u002F` holds the HTML report. Open it with `pnpm --filter @repo\u002Fe2e exec playwright show-report`.\n- `test-results\u002F` holds a screenshot of every failure, a video of it, and a trace of the first retry. Open a trace with `pnpm --filter @repo\u002Fe2e exec playwright show-trace \u003Cpath>`.\n- Both directories are gitignored, and `pnpm --filter @repo\u002Fe2e clean` removes them.\n\nThree failures have a fix rather than a bug behind them:\n\n- *\"Chromium is not installed\"*: run `pnpm e2e:install`. On a bare CI image the system libraries are missing too: `pnpm --filter @repo\u002Fe2e exec playwright install --with-deps chromium`, which needs root and is never run for a developer.\n- *\"apps\u002Fapi\u002F.env does not exist\"*: run `pnpm env:setup`.\n- *\"pnpm db:seed failed\"* with a refusal about the database: the seed writes only to this project's own development database. Run `pnpm db:setup` and read what it prints.\n\n## The database\n\nThe suite uses the project's own `db:setup`, `db:seed` and `db:drop`, so it works the same under `database-d1` and `database-postgres` and carries no second code path. Both setup and seed carry the guard: `db:setup` refuses a `DATABASE_URL` its state block does not vouch for, and `db:seed` refuses `NODE_ENV=production` and any database that is not this project's own, before it connects.\n\nThe database is dropped **on CI only**. Locally it is kept, because a drop means a full migration on the next run for no safety gained. Run `pnpm db:drop` yourself for a clean slate.\n\n`E2E_DB_SETUP_ARGS` passes extra flags to `db:setup`. It exists for a CI runner with a Postgres service container, which sets it to `--server` so `db:setup` creates the project's database on the server `DATABASE_URL` in `apps\u002Fapi\u002F.env` names. A developer leaves it unset.\n\n## CI\n\nThis module adds no workflow. A project that wants the suite on CI writes its own job: install, `pnpm env:setup`, `pnpm --filter @repo\u002Fe2e exec playwright install --with-deps chromium`, then `pnpm e2e` with `CI=true`.\n\n## What this suite is not\n\nNo visual regression, no accessibility assertions, no performance budget, no load or contract testing. One browser engine, Chromium. Nothing runs against a deployed preview or production: every flow drives a dev server on localhost with a development database.\n\n## Next\n\nRun `saasaloy-testing` to decide which other tests a change needs.\n","# saasaloy-e2e\n\n`packages\u002Fe2e` holds the project's browser suite. It starts the apps, drives them with headless Chromium, and stops every process it started. It is the only workspace in the repo that Playwright reads, and `pnpm test` (Vitest) never collects a file from it: the root `vitest.config.ts` leaves `packages\u002Fe2e` out.\n\n## The two commands\n\n```sh\npnpm e2e:install    # download Chromium, once per machine\npnpm e2e            # migrate and seed the database, start the apps, run the flows\n```\n\n`pnpm e2e:install` is not a `postinstall`. Downloading ~150MB on every `pnpm install` in every checkout is a cost a project should opt into, so the browser is missing until you ask for it, and `pnpm e2e` fails with that exact command in the message when it is.\n\n`pnpm e2e:ui` opens Playwright's watch UI. It needs a desktop, so it is useless on a headless box; `pnpm e2e` is the headless path and needs nothing.\n\nBefore the first run, every app needs its `.env`. Run `saasaloy env` (or copy `packages\u002Fenv\u002F.env.example` to `packages\u002Fenv\u002F.env`; the local defaults are enough), then `pnpm env:setup`. `pnpm e2e` names the missing file and that command when one is absent.\n\n## What one run does, in order\n\n1. `prepare.ts` checks Chromium is downloaded and every app it will start has its `.env`.\n2. When `database` is installed, `prepare.ts` runs `pnpm db:setup`, then `pnpm db:seed`.\n3. Playwright starts one dev server per installed app and waits for each to answer.\n4. The specs run, one at a time.\n5. `global-teardown.ts` runs `pnpm db:drop`, **on CI only**.\n\nSteps 1 and 2 are a script rather than a `globalSetup` hook because of step 3. The api Worker reads `apps\u002Fapi\u002F.env` when it boots, so a `DATABASE_URL` written after the server started is a value it never sees.\n\n## Ports\n\n| App | Port | Started when |\n| --- | --- | --- |\n| `apps\u002Fapi` | 4000 | `api` is installed |\n| `apps\u002Fweb` | 3000 | always, it is the base app |\n| `apps\u002Fadmin` | 3001 | `admin` is installed |\n\nThese are the project's pinned dev ports, the same ones in `AGENTS.md`. Off CI, `reuseExistingServer` is on, so a `pnpm dev` you already have running is used instead of a second one on a busy port. On CI it is off, because reusing would hide a start-up failure.\n\nPlaywright waits on `http:\u002F\u002Flocalhost:4000\u002Fhealth` for the api, not on its origin. The Worker answers `GET \u002F` with a 404 envelope, and Playwright reads any status at or above 400 as \"not ready\".\n\n## Adding a flow\n\n1. Write `specs\u002F\u003Cname>.spec.ts`.\n2. Wrap it in a `test.describe` that declares the modules it needs as tags.\n3. Add any new tag to `SPEC_TAGS` in `lib\u002Fproject.ts`.\n\n```ts\nimport { expect, test } from \"@playwright\u002Ftest\";\n\nimport { URLS } from \"..\u002Flib\u002Fproject.ts\";\n\ntest.describe(\"api health\", { tag: [\"@api\"] }, () => {\n  test(\"the api answers\", async ({ request }) => {\n    const response = await request.get(`${URLS.api}\u002Fhealth`);\n    expect(response.status()).toBe(200);\n  });\n});\n```\n\nFour rules, each one load-bearing:\n\n- **A tag is a module name, and nothing else.** `playwright.config.ts` turns every tag in `SPEC_TAGS` whose module is absent into `grepInvert`, so the spec is never collected. A tag that names no module is never in `installed`, so its spec would never run anywhere and the suite would still report green.\n- **Never skip on a missing route.** A `test.skip()` when a page 404s turns a broken route into a green run, which is the exact failure this suite exists to catch. Gate on the tag, which is decided before anything runs.\n- **Wait for the island before you type.** A form on `apps\u002Fweb` is a React island on a static Astro page. A value typed before hydration is thrown away when React mounts the controlled input, and the form then submits an empty value. Astro marks an island `\u003Castro-island ssr>` until it hydrates, so wait for the island that holds your field to lose it: `await expect(page.locator(\"astro-island[ssr]\").filter({ has: field })).toHaveCount(0)`. `waitlist.spec.ts` is the worked example.\n- **Imports carry the `.ts` extension.** `prepare.ts` runs under `node`, whose type stripping resolves the real file, so the whole workspace keeps one import style.\n\n## The seeded admin and the rows a spec writes\n\nThe admin specs sign in as `superadmin@example.test` with the password `saasaloy-dev-password`, `SEED_ADMIN` in `lib\u002Fproject.ts`. The suite creates no account of its own. The `auth` module's seed slices write that user, and `pnpm db:seed` upserts it back to its slice values before every run, so a password changed by hand is reset and the account is always a superadmin. Change `SEED_ADMIN` only together with `packages\u002Fdb\u002Fsrc\u002Fseed\u002Fslices\u002Fusers.ts` and `accounts.ts`.\n\nA spec that needs a signed-in admin but is not about the login screen signs in at the start of the test through the same form `admin-login.spec.ts` drives. `admin-login.spec.ts` itself starts from no cookie on purpose: a login flow that starts from a saved session tests the session.\n\nEvery **other** row a spec writes is unique, with `uniqueEmail()` from `lib\u002Ffixtures.ts`. There is no cleanup step, on purpose: a teardown that deletes rows does not run when a run crashes, so the next run starts poisoned and the failure looks like a real bug a day later. A unique row cannot collide with anything.\n\n## The flows that ship\n\n| Spec | Tags | What it proves |\n| --- | --- | --- |\n| `health.spec.ts` | `@api` | The Worker started and `GET \u002Fhealth` answers the documented body. The floor. |\n| `waitlist.spec.ts` | `@waitlist` | A real browser fills the real form on `apps\u002Fweb`, the island posts, and the route answers 201. |\n| `admin-login.spec.ts` | `@admin` `@auth` | The login form signs the seeded admin in, the guard redirects, and `GET \u002Fadmin\u002Fusers` answers 200. |\n| `admin-unauthenticated.spec.ts` | `@admin` `@auth` | The same guarded route answers 401 with the api's error envelope when nobody is signed in. |\n\n`admin-unauthenticated.spec.ts` is its own flow rather than a second assertion, because the admin SPA's guard runs in the browser and would hide a server that stopped checking.\n\n**`waitlist.spec.ts` needs the form on a page.** `saasaloy add waitlist` writes the block and the island and then stops; the `saasaloy-waitlist` skill's Wire-up section has the two lines that place it. The spec says so in its failure message rather than skipping.\n\n## When a run is red\n\n- The failing step is on **stdout**. The `list` reporter runs first for exactly that reason, so a headless box needs nothing else.\n- `playwright-report\u002F` holds the HTML report. Open it with `pnpm --filter @repo\u002Fe2e exec playwright show-report`.\n- `test-results\u002F` holds a screenshot of every failure, a video of it, and a trace of the first retry. Open a trace with `pnpm --filter @repo\u002Fe2e exec playwright show-trace \u003Cpath>`.\n- Both directories are gitignored, and `pnpm --filter @repo\u002Fe2e clean` removes them.\n\nThree failures have a fix rather than a bug behind them:\n\n- *\"Chromium is not installed\"*: run `pnpm e2e:install`. On a bare CI image the system libraries are missing too: `pnpm --filter @repo\u002Fe2e exec playwright install --with-deps chromium`, which needs root and is never run for a developer.\n- *\"apps\u002Fapi\u002F.env does not exist\"*: run `pnpm env:setup`.\n- *\"pnpm db:seed failed\"* with a refusal about the database: the seed writes only to this project's own development database. Run `pnpm db:setup` and read what it prints.\n\n## The database\n\nThe suite uses the project's own `db:setup`, `db:seed` and `db:drop`, so it works the same under `database-d1` and `database-postgres` and carries no second code path. Both setup and seed carry the guard: `db:setup` refuses a `DATABASE_URL` its state block does not vouch for, and `db:seed` refuses `NODE_ENV=production` and any database that is not this project's own, before it connects.\n\nThe database is dropped **on CI only**. Locally it is kept, because a drop means a full migration on the next run for no safety gained. Run `pnpm db:drop` yourself for a clean slate.\n\n`E2E_DB_SETUP_ARGS` passes extra flags to `db:setup`. It exists for a CI runner with a Postgres service container, which sets it to `--server` so `db:setup` creates the project's database on the server `DATABASE_URL` in `apps\u002Fapi\u002F.env` names. A developer leaves it unset.\n\n## CI\n\nThis module adds no workflow. A project that wants the suite on CI writes its own job: install, `pnpm env:setup`, `pnpm --filter @repo\u002Fe2e exec playwright install --with-deps chromium`, then `pnpm e2e` with `CI=true`.\n\n## What this suite is not\n\nNo visual regression, no accessibility assertions, no performance budget, no load or contract testing. One browser engine, Chromium. Nothing runs against a deployed preview or production: every flow drives a dev server on localhost with a development database.\n\n## Next\n\nRun `saasaloy-testing` to decide which other tests a change needs.\n",{"name":5,"description":7},"main","a46a4dd388795519840da0ed1f695634b6dcd99b","modules\u002Fe2e\u002Fskills\u002Fsaasaloy-e2e",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-e2e",{"tool":40,"command":41},"bunx","bunx skills add mimukit\u002Fsaasaloy --skill saasaloy-e2e",{"tool":43,"command":44},"pnpm","pnpm dlx skills add mimukit\u002Fsaasaloy --skill saasaloy-e2e","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmimukit\u002Fsaasaloy\u002Fblob\u002Fmain\u002Fmodules\u002Fe2e\u002Fskills\u002Fsaasaloy-e2e\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",[],[]]