CMS check skill

# CMS Check Review a Framer project’s CMS for unfinished content, inconsistencies, and problems in the pages that use it. Learn each collection’s pattern before judging individual items. ## Scope - Review all collections unless the user names specific ones. - Inspect each item’s status when available. Keep visible items, drafts, and items with unknown status distinct. Do not treat a visible setting as proof that an item is live on the published site. - For collections with 30 items or fewer, inspect every item. - For larger collections, scan all accessible items for suspicious field values. Closely inspect at least 15 items: five from the start, five from the middle, and five from the end of the current order, plus items flagged by the scan. State the actual coverage. - Inspect the collection lists and detail-page templates that use each collection when accessible. - If there are no CMS collections, report that and stop. ## Checks 1. Find placeholder text, test items, editorial notes, and substantially unfinished visible items. List unfinished drafts as optional cleanup unless they affect visible content or the user says they are intended for launch. 2. Compare similar items for meaningful inconsistencies in naming, capitalization, dates, categories, summaries, and field use. 3. Check fields connected to collection lists and detail pages. Before flagging an empty value, inspect the field’s default and whether the page uses a fallback or hides the element when the value is empty. 4. Look for item-specific content on a detail-page template that is static instead of connected to a CMS field. Flag it when it would show the wrong text or image across items. 5. Check collection-list filters, sort order, and limits for settings that exclude intended items or show the wrong items. Report the exact setting and affected items; do not assume every hidden item is an error. 6. Check references to other CMS items. Flag missing references or clearly wrong targets that make visible content incorrect or incomplete. 7. Check fields used for page titles and descriptions. Flag empty values when there is no suitable fallback. 8. Flag unfinished, misleading, or duplicate slugs for review when they may affect routing. If duplicate slugs cannot be checked, say so under Unverified. Do not suggest changing a URL solely for style. 9. Identify possibly repeated or outdated content as review candidates, not confirmed items to remove. Similar titles or a lack of visible links alone are insufficient evidence. ## Changes - Correct only clear typos and formatting inconsistencies when an established pattern makes the intended value unambiguous. - Do not invent facts or fill gaps with plausible content. - Do not delete items, change slugs, collection fields, references, visibility, draft status, filters, or templates unless the user asks. - Leave uncertain values unchanged and report the decision needed. ## Output Start with the collections reviewed, the number of items scanned and closely inspected in each, and a brief assessment. ## Needs attention Number each issue. Give the collection, item title and path when available, exact evidence, the affected page or list, and one specific fix or decision needed. Group items with the same issue, but name every affected item. ## Optional cleanup List unfinished drafts and possible repeated or outdated content here. Explain why each was flagged without calling it a confirmed problem. ## Fixed List each change with the collection, item, field, and before/after value. Omit this section if nothing changed. ## Unverified Name statuses, items, fields, page settings, or published pages that could not be checked. Distinguish project settings and CMS values from behavior confirmed on the published site. Do not create a finding solely because an optional field is empty. If no issues were found in the scope checked, say so and describe the coverage.