[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMKDD0XT42PHTZYR4P9ZSS":3,"skill-same:01M7EMKDD0XT42PHTZYR4P9ZSS":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EMKDD0XT42PHTZYR4P9ZSS","ams-cms-pro",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-cms-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cms-pro\ndescription: Integrate headless CMSs: content modeling, APIs, previews, webhooks, and editorial workflows. Use when content teams need to publish without developers.\ncategory: web-development\n---\n\n# CMS Pro\n\nA practical guide to headless CMS integration: content modeling, delivery APIs, preview\u002Fdraft workflows, webhooks for revalidation, and the editorial UX that makes content teams self-sufficient.\n\n## Overview\n\nA headless CMS separates **content management** (editorial UI, workflows) from **presentation** (your frontend consuming a content API). The integration work: modeling content types well, fetching efficiently, previewing drafts, and revalidating statically-generated pages on publish. Good modeling is 80% of success — bad models produce either developer bottlenecks or content chaos.\n\n## When to use\n\n- Marketing sites, blogs, docs, and landing pages edited by non-developers.\n- Choosing\u002Fevaluating a headless CMS (any vendor — patterns are universal).\n- Preview environments for draft content.\n- Webhook-driven revalidation and rebuilds.\n\n## Core concepts\n\n- **Content modeling.** Content types (Post, Page, Author), fields (rich text, references, media, SEO meta), and validations. Model for the editors' mental model, not the database's.\n- **References vs embeds.** Reference shared entities (authors, categories); embed page-specific blocks. Over-referencing complicates queries; over-embedding duplicates content.\n- **Delivery API.** Read-optimized CDN API (usually GraphQL or REST) with draft\u002Fpublished variants. Query at build time (static) or request time (dynamic) per page needs.\n- **Preview.** Draft mode: editors see unpublished content via preview URLs\u002Ftokens. Implementation: preview API route that bypasses the published cache with a secret token.\n- **Webhooks.** CMS publishes → webhook → revalidate affected paths (`revalidatePath`\u002F`revalidateTag`) or trigger rebuild. Map content types to URL patterns for surgical invalidation.\n- **Portable text \u002F rich text.** Structured rich text (blocks, marks, custom objects) rendered by your components — never raw HTML from the CMS without sanitization.\n- **Media.** CMS-hosted assets via CDN with transforms (resize, format). Use the CMS's image API, not originals.\n\n## Practical workflow\n\n**1. Model content.**\n```\nPost: title, slug (unique, validated), excerpt, body (portable text),\n      coverImage (media), author (reference), categories (references[]),\n      seo { title, description, ogImage }, publishedAt, status\n```\nAdd help text and validations on every field — editors shouldn't guess.\n\n**2. Fetch (Next.js example).**\n```ts\n\u002F\u002F lib\u002Fcms.ts\nexport async function getPost(slug: string, draft = false) {\n  return cms.fetch(`*[_type == \"post\" && slug.current == $slug][0]`, { slug },\n    { token: draft ? PREVIEW_TOKEN : undefined, perspective: draft ? 'drafts' : 'published' });\n}\n```\n\n**3. Draft preview.**\n```ts\n\u002F\u002F app\u002Fapi\u002Fpreview\u002Froute.ts — validates ?secret=, enables draft mode, redirects to the page\n\u002F\u002F page.tsx reads draftMode() and passes draft flag to fetches\n```\n\n**4. Revalidate on publish.** CMS webhook → `\u002Fapi\u002Frevalidate` (verify signature!) → `revalidateTag('posts')` or `revalidatePath('\u002Fblog\u002F[slug]')`. Tag-based invalidation scales best.\n\n**5. Render rich text safely.** Map portable-text blocks to your components (headings, quotes, code blocks, embeds); sanitize any raw HTML.\n\n**6. Editorial QA.** Preview links in the CMS workflow; required SEO fields; image alt requirements; broken-link checks on publish.\n\n## Common pitfalls\n\n- **Modeling for developers.** Field names and structures editors don't understand → constant support requests. Name things in editorial language; add help text.\n- **N+1 queries.** Fetching a list then each item's references individually. Use query projections\u002FGROQ to fetch nested data in one request.\n- **No preview.** Editors publishing blind → broken layouts discovered in production. Draft preview is not optional for rich pages.\n- **Full rebuilds on every edit.** Rebuilding 10k pages for a typo fix. Webhook + tag\u002Fpath revalidation instead.\n- **Unsigned webhooks.** Revalidation endpoints without signature verification = anyone can purge your cache \u002F trigger builds. Verify signatures.\n- **Raw HTML rendering.** `{@html body}` from CMS content = XSS vector. Structured rich text + component mapping, or strict sanitization.\n- **Slug changes breaking URLs.** Allow slug edits but keep redirect history (old slug → new). Or lock slugs after publish.\n- **Missing SEO fields.** No title\u002Fdescription\u002FOG per page = weak sharing and search. Make them required with sensible fallbacks.\n- **Vendor lock-in blindness.** Proprietary rich-text formats and media URLs complicate migration. Prefer portable formats; keep media URLs abstracted.\n","# CMS Pro\n\nA practical guide to headless CMS integration: content modeling, delivery APIs, preview\u002Fdraft workflows, webhooks for revalidation, and the editorial UX that makes content teams self-sufficient.\n\n## Overview\n\nA headless CMS separates **content management** (editorial UI, workflows) from **presentation** (your frontend consuming a content API). The integration work: modeling content types well, fetching efficiently, previewing drafts, and revalidating statically-generated pages on publish. Good modeling is 80% of success — bad models produce either developer bottlenecks or content chaos.\n\n## When to use\n\n- Marketing sites, blogs, docs, and landing pages edited by non-developers.\n- Choosing\u002Fevaluating a headless CMS (any vendor — patterns are universal).\n- Preview environments for draft content.\n- Webhook-driven revalidation and rebuilds.\n\n## Core concepts\n\n- **Content modeling.** Content types (Post, Page, Author), fields (rich text, references, media, SEO meta), and validations. Model for the editors' mental model, not the database's.\n- **References vs embeds.** Reference shared entities (authors, categories); embed page-specific blocks. Over-referencing complicates queries; over-embedding duplicates content.\n- **Delivery API.** Read-optimized CDN API (usually GraphQL or REST) with draft\u002Fpublished variants. Query at build time (static) or request time (dynamic) per page needs.\n- **Preview.** Draft mode: editors see unpublished content via preview URLs\u002Ftokens. Implementation: preview API route that bypasses the published cache with a secret token.\n- **Webhooks.** CMS publishes → webhook → revalidate affected paths (`revalidatePath`\u002F`revalidateTag`) or trigger rebuild. Map content types to URL patterns for surgical invalidation.\n- **Portable text \u002F rich text.** Structured rich text (blocks, marks, custom objects) rendered by your components — never raw HTML from the CMS without sanitization.\n- **Media.** CMS-hosted assets via CDN with transforms (resize, format). Use the CMS's image API, not originals.\n\n## Practical workflow\n\n**1. Model content.**\n```\nPost: title, slug (unique, validated), excerpt, body (portable text),\n      coverImage (media), author (reference), categories (references[]),\n      seo { title, description, ogImage }, publishedAt, status\n```\nAdd help text and validations on every field — editors shouldn't guess.\n\n**2. Fetch (Next.js example).**\n```ts\n\u002F\u002F lib\u002Fcms.ts\nexport async function getPost(slug: string, draft = false) {\n  return cms.fetch(`*[_type == \"post\" && slug.current == $slug][0]`, { slug },\n    { token: draft ? PREVIEW_TOKEN : undefined, perspective: draft ? 'drafts' : 'published' });\n}\n```\n\n**3. Draft preview.**\n```ts\n\u002F\u002F app\u002Fapi\u002Fpreview\u002Froute.ts — validates ?secret=, enables draft mode, redirects to the page\n\u002F\u002F page.tsx reads draftMode() and passes draft flag to fetches\n```\n\n**4. Revalidate on publish.** CMS webhook → `\u002Fapi\u002Frevalidate` (verify signature!) → `revalidateTag('posts')` or `revalidatePath('\u002Fblog\u002F[slug]')`. Tag-based invalidation scales best.\n\n**5. Render rich text safely.** Map portable-text blocks to your components (headings, quotes, code blocks, embeds); sanitize any raw HTML.\n\n**6. Editorial QA.** Preview links in the CMS workflow; required SEO fields; image alt requirements; broken-link checks on publish.\n\n## Common pitfalls\n\n- **Modeling for developers.** Field names and structures editors don't understand → constant support requests. Name things in editorial language; add help text.\n- **N+1 queries.** Fetching a list then each item's references individually. Use query projections\u002FGROQ to fetch nested data in one request.\n- **No preview.** Editors publishing blind → broken layouts discovered in production. Draft preview is not optional for rich pages.\n- **Full rebuilds on every edit.** Rebuilding 10k pages for a typo fix. Webhook + tag\u002Fpath revalidation instead.\n- **Unsigned webhooks.** Revalidation endpoints without signature verification = anyone can purge your cache \u002F trigger builds. Verify signatures.\n- **Raw HTML rendering.** `{@html body}` from CMS content = XSS vector. Structured rich text + component mapping, or strict sanitization.\n- **Slug changes breaking URLs.** Allow slug edits but keep redirect history (old slug → new). Or lock slugs after publish.\n- **Missing SEO fields.** No title\u002Fdescription\u002FOG per page = weak sharing and search. Make them required with sensible fallbacks.\n- **Vendor lock-in blindness.** Proprietary rich-text formats and media URLs complicate migration. Prefer portable formats; keep media URLs abstracted.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-cms-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-cms-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-cms-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-cms-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-cms-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]