[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CV0EE23EEFD7XW58RGZ98H":3,"skill-same:01M7CV0EE23EEFD7XW58RGZ98H":46},{"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":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CV0EE23EEFD7XW58RGZ98H","mercur-blocks",null,"Discover, evaluate, install, and verify Mercur blocks in the basic starter using `blocks.json` aliases and CLI workflows.","amoai-tech\u002Fmdeai","amoai-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F320616881?v=4","01M7CTJYGWP82J2HHMQC5NN9JP","amo","01M7CTJYHE5YQRGQSDJES3Z0QE",2,"MIT","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fcommerce\u002Fmercur\u002F.claude\u002Fskills\u002Fmercur-blocks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mercur-blocks\ndescription: Discover, evaluate, install, and verify Mercur blocks in the basic starter using `blocks.json` aliases and CLI workflows.\n---\n\n# Mercur Blocks Workflow\n\nUse this skill when:\n- evaluating whether a block fits the starter project\n- adding a block\n- checking installed block impact\n- updating a block and reviewing drift\n\n## Alias map\n\nIn the basic starter:\n- `api` -> `packages\u002Fapi\u002Fsrc`\n- `admin` -> `apps\u002Fadmin\u002Fsrc`\n- `vendor` -> `apps\u002Fvendor\u002Fsrc`\n\nThink about block impact by alias destination, not just by name.\n\n## Workflow\n\n1. Search if the exact block name is not known.\n2. View the block before installation.\n3. Identify which aliases and workspaces it will touch.\n4. Add the block.\n5. When CLI asks to overwrite `middlewares.ts` — **always decline** and merge manually.\n6. Inspect the installed files and the block docs output.\n7. Apply all configuration from the block docs (middleware, medusa-config, env vars, migrations).\n8. Run `bun run dev` from `packages\u002Fapi` and check for startup errors before moving on.\n\n## Post-install checklist\n\n- Did files land under `packages\u002Fapi\u002Fsrc`, `apps\u002Fadmin\u002Fsrc`, or `apps\u002Fvendor\u002Fsrc`?\n- Does `packages\u002Fapi\u002Fmedusa-config.ts` need module or provider registration?\n- Did the block docs specify middleware to add to `src\u002Fapi\u002Fmiddlewares.ts`?\n  - Check the **actual export names and paths** in the installed middleware files — block docs may have wrong paths.\n  - Verify the import path matches `.\u002Factual\u002Ffolder\u002Fmiddlewares` not a generic path from docs.\n- Did the block add custom modules that need `db:generate \u003Cmodule>` and `db:migrate`?\n  - Even if docs don't mention migrations, check if the module has a `models\u002F` directory — if it does, migrations are needed.\n- Did the block add UI routes? They must be under `src\u002Froutes\u002F` (not `src\u002Fpages\u002F`) for the dashboard SDK to detect them.\n- Did the block add UI pages that need `export const config: RouteConfig` for sidebar visibility?\n- Did the block docs require env vars, plugin options, or config changes?\n- Did the block specify npm dependencies? Install any that CLI didn't handle automatically.\n\n## Known issues with block docs\n\nBlock docs may contain inaccurate information. Always verify:\n- **Middleware import paths**: docs may reference generic paths like `.\u002Fadmin\u002Fmiddlewares` when the actual file is at `.\u002Fadmin\u002F\u003Cfeature>\u002Fmiddlewares`.\n- **Middleware export names**: check the actual `export const` name in the installed file.\n- **Missing dependencies**: some blocks import npm packages not listed in their `dependencies` array.\n- **Missing migration instructions**: some blocks with custom modules don't mention `db:generate` \u002F `db:migrate` in docs.\n- **File conflicts**: multiple blocks may try to write the same file (e.g. workflow hooks). Decline overwrites and merge manually.\n\n## Middleware merging\n\nWhen adding a block's middleware to `src\u002Fapi\u002Fmiddlewares.ts`:\n1. Read the actual installed middleware file to get the correct export name and path.\n2. Add the import to the existing `middlewares.ts`.\n3. Spread it into the existing `routes` array.\n\nDo NOT accept CLI's middleware overwrite — it replaces the entire file.\n\n## Useful commands\n\n```bash\nnpx @mercurjs\u002Fcli@latest search --query \u003Ckeyword>\nnpx @mercurjs\u002Fcli@latest view \u003Cblock>\nnpx @mercurjs\u002Fcli@latest add \u003Cblock>\nnpx @mercurjs\u002Fcli@latest diff \u003Cblock>\n```\n\nRun CLI commands from the project root where `blocks.json` lives.\nRun `medusa` commands (db:generate, db:migrate) from `packages\u002Fapi`.\n\n## Avoid\n\n- adding blocks without reviewing their docs first\n- accepting middleware.ts overwrite from CLI\n- ignoring config or env follow-up after install\n- skipping `diff` when reviewing block updates\n- trusting docs blindly — verify import paths and dependencies against installed files\n","# Mercur Blocks Workflow\n\nUse this skill when:\n- evaluating whether a block fits the starter project\n- adding a block\n- checking installed block impact\n- updating a block and reviewing drift\n\n## Alias map\n\nIn the basic starter:\n- `api` -> `packages\u002Fapi\u002Fsrc`\n- `admin` -> `apps\u002Fadmin\u002Fsrc`\n- `vendor` -> `apps\u002Fvendor\u002Fsrc`\n\nThink about block impact by alias destination, not just by name.\n\n## Workflow\n\n1. Search if the exact block name is not known.\n2. View the block before installation.\n3. Identify which aliases and workspaces it will touch.\n4. Add the block.\n5. When CLI asks to overwrite `middlewares.ts` — **always decline** and merge manually.\n6. Inspect the installed files and the block docs output.\n7. Apply all configuration from the block docs (middleware, medusa-config, env vars, migrations).\n8. Run `bun run dev` from `packages\u002Fapi` and check for startup errors before moving on.\n\n## Post-install checklist\n\n- Did files land under `packages\u002Fapi\u002Fsrc`, `apps\u002Fadmin\u002Fsrc`, or `apps\u002Fvendor\u002Fsrc`?\n- Does `packages\u002Fapi\u002Fmedusa-config.ts` need module or provider registration?\n- Did the block docs specify middleware to add to `src\u002Fapi\u002Fmiddlewares.ts`?\n  - Check the **actual export names and paths** in the installed middleware files — block docs may have wrong paths.\n  - Verify the import path matches `.\u002Factual\u002Ffolder\u002Fmiddlewares` not a generic path from docs.\n- Did the block add custom modules that need `db:generate \u003Cmodule>` and `db:migrate`?\n  - Even if docs don't mention migrations, check if the module has a `models\u002F` directory — if it does, migrations are needed.\n- Did the block add UI routes? They must be under `src\u002Froutes\u002F` (not `src\u002Fpages\u002F`) for the dashboard SDK to detect them.\n- Did the block add UI pages that need `export const config: RouteConfig` for sidebar visibility?\n- Did the block docs require env vars, plugin options, or config changes?\n- Did the block specify npm dependencies? Install any that CLI didn't handle automatically.\n\n## Known issues with block docs\n\nBlock docs may contain inaccurate information. Always verify:\n- **Middleware import paths**: docs may reference generic paths like `.\u002Fadmin\u002Fmiddlewares` when the actual file is at `.\u002Fadmin\u002F\u003Cfeature>\u002Fmiddlewares`.\n- **Middleware export names**: check the actual `export const` name in the installed file.\n- **Missing dependencies**: some blocks import npm packages not listed in their `dependencies` array.\n- **Missing migration instructions**: some blocks with custom modules don't mention `db:generate` \u002F `db:migrate` in docs.\n- **File conflicts**: multiple blocks may try to write the same file (e.g. workflow hooks). Decline overwrites and merge manually.\n\n## Middleware merging\n\nWhen adding a block's middleware to `src\u002Fapi\u002Fmiddlewares.ts`:\n1. Read the actual installed middleware file to get the correct export name and path.\n2. Add the import to the existing `middlewares.ts`.\n3. Spread it into the existing `routes` array.\n\nDo NOT accept CLI's middleware overwrite — it replaces the entire file.\n\n## Useful commands\n\n```bash\nnpx @mercurjs\u002Fcli@latest search --query \u003Ckeyword>\nnpx @mercurjs\u002Fcli@latest view \u003Cblock>\nnpx @mercurjs\u002Fcli@latest add \u003Cblock>\nnpx @mercurjs\u002Fcli@latest diff \u003Cblock>\n```\n\nRun CLI commands from the project root where `blocks.json` lives.\nRun `medusa` commands (db:generate, db:migrate) from `packages\u002Fapi`.\n\n## Avoid\n\n- adding blocks without reviewing their docs first\n- accepting middleware.ts overwrite from CLI\n- ignoring config or env follow-up after install\n- skipping `diff` when reviewing block updates\n- trusting docs blindly — verify import paths and dependencies against installed files\n",{"name":5,"description":7},"main","9955f6a8aa5de3c14fea562c7e6b72973366ba3c","commerce\u002Fmercur\u002F.claude\u002Fskills\u002Fmercur-blocks",1,"https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai","https:\u002F\u002Fmdeai-psi.vercel.app","https:\u002F\u002Fgithub.com\u002Famoai-tech","2026-11-13 03:54:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add amoai-tech\u002Fmdeai --skill mercur-blocks",{"tool":38,"command":39},"bunx","bunx skills add amoai-tech\u002Fmdeai --skill mercur-blocks",{"tool":41,"command":42},"pnpm","pnpm dlx skills add amoai-tech\u002Fmdeai --skill mercur-blocks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fcommerce\u002Fmercur\u002F.claude\u002Fskills\u002Fmercur-blocks\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7CV3D59CQX8N178NN3W5DEQ","mde-pr-review-supabase","Use when reviewing MDE Supabase SQL, Auth and RLS changes in a pull request.","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fscripts\u002Fpr-agent\u002Fskills\u002Fsupabase\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7CV39XR1SPH7C4FNXAXMM36","mde-pr-review-stripe","Use when reviewing MDE Stripe payments and webhooks changes in a pull request.","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fscripts\u002Fpr-agent\u002Fskills\u002Fstripe\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CV37HHNM5A144SEX2VE05N","mde-pr-review-nextjs","Use when reviewing MDE Next.js App Router changes in a pull request.","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fscripts\u002Fpr-agent\u002Fskills\u002Fnextjs\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"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},"01M7CV34C1M5STTKHX5CGVN3VS","mde-pr-review-mastra","Use when reviewing MDE Mastra agent, tool and workflow changes in a pull request.","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fscripts\u002Fpr-agent\u002Fskills\u002Fmastra\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CV31A37VPRRASAVGE8K8SN","mde-pr-review-maps","Use when reviewing MDE Google Maps and Places changes in a pull request.","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fscripts\u002Fpr-agent\u002Fskills\u002Fmaps\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CV2Y70DQJ1VXFHS732CSQ4","mde-pr-review-copilotkit","Use when reviewing MDE CopilotKit and AG-UI changes in a pull request.","https:\u002F\u002Fgithub.com\u002Famoai-tech\u002Fmdeai\u002Fblob\u002Fmain\u002Fscripts\u002Fpr-agent\u002Fskills\u002Fcopilotkit\u002FSKILL.md",[],[]]