@bettercms-ai/mcp 0.73.2 → 0.74.0

package/dist/skills/bettercms/SKILL.md

@@ -15,6 +15,7 @@ that only show up in code. Read doctrine from the MCP, never from memory:
 
 - Schema, sections, variants, publish order: resource `bettercms://playbook/schema` (§1–§14).
 - Content sidebar organisation: resource `bettercms://playbook/structure`.
+- Section patterns (149 worked kit entries by category and edge tag): resource `bettercms://kit`.
 - Guided flows: the `studio` prompt routes to the rest (`convert_site` prompt,
   `build_site` prompt, `componentize_site` prompt, `propose_schema` prompt, `new_page` prompt,
   `new_component` prompt, `new_form` prompt, `seo_optimize` prompt, `import-site` prompt,
@@ -127,8 +128,10 @@ resources: `bettercms://skill/bettercms` for this file, and each reference under
 | What the server does and does not check on a write | [write-limits.md](references/write-limits.md) | before relying on a limit; reading a refused write; a bulk load or re-run | validation, maxLength, unique, 400, refused write, dry run, externalKey, upsert, re-run |
 | Plan a site by business type | [site-blueprints.md](references/site-blueprints.md) | the IA of a known site type, with its collections, forms and structured data | new site, IA, portfolio, agency, corporate, SaaS, ecommerce, directory, blog, docs, restaurant, events, course, jobs, real estate, nonprofit, multi-brand |
 | Components, props, variants, component publish codes | [components.md](references/components.md) | creating, swapping, publishing or validating a component | component, prop, variant, sectionType, publish component |
-| One section, source HTML to bound template: hero, feature grid, pricing table, testimonials, FAQ | [worked-examples.md](references/worked-examples.md) | you want the whole path for one section in production shapes | example, hero, pricing, FAQ, testimonial, source to schema |
+| Which kit pattern fits a section, and its shape and pitfalls, by category and edge tag | [kit-scenarios.md](references/kit-scenarios.md) | before designing any section's fields or props; a band detection.md classified | kit, pattern, scenario, edge tag, events, locations, calculator, map, chart, docs, team, bento, slots, personalization, localized |
+| One section, source HTML to bound template: hero, feature grid, pricing table, testimonials, FAQ, bento | [worked-examples.md](references/worked-examples.md) | you want the whole path for one section in production shapes | example, hero, pricing, FAQ, testimonial, source to schema |
 | The same for an article entry, navigation in the Global Layout, tabs holding columns | [worked-examples-advanced.md](references/worked-examples-advanced.md) | a collection entry with a body, site chrome, or nested blocks | example, blog post, document body, mega menu, tabs, columns |
+| The modelled section closest to the one you are building: schema, HTML signals, mcp steps, pitfalls | [kit-catalog.md](references/kit-catalog.md) | before designing a section or its props; matching source HTML to a known pattern | kit, catalogue, edge tag, section pattern, bento, localized, personalization, a11y, responsive |
 | Componentize a derived site | [componentize.md](references/componentize.md) | `get_site_composition` shows pages made of fields only | componentize, sections, fields-only, get_componentize_plan, BcmsSections, --sections |
 | Click-to-edit attributes, addresses, declared mode | [bindings.md](references/bindings.md) | `grep -rl "data-bcms-" src` finds files; a value the editor cannot select | data-bcms-field, click to edit, binding report, stega, declared |
 | Animated sites: GSAP, ScrollTrigger, split text, Motion, Lenis, Locomotive, three.js and WebGL, marquees, carousels, Lottie, hydrated islands, and what must stand down in the editor's canvas (`inEditor()`) | [animation.md](references/animation.md) | `package.json` lists `gsap`, `lenis`, `locomotive-scroll`, `framer-motion` or `motion`, `three`, `swiper` or a text splitter; a publish refused with `SPLIT_PATTERN_UNKNOWN` or `ISLAND_PROPS_UNMATCHED`; a `client-only-island` gate exception | animation, GSAP, ScrollTrigger, SplitText, Lenis, Framer Motion, marquee, Swiper, Lottie, island, client:only, data-bcms-split |

package/dist/skills/bettercms/references/content-modeling.md

@@ -108,6 +108,11 @@ sitemap), RSS (dated by `publishedAt`), `llms.txt` (one link per published item)
 
 ## 4. Field decisions
 
+Before designing a section's fields, find the closest component-kit entry: the chooser by
+category and edge tag is [kit-scenarios.md](kit-scenarios.md), the full list is the
+`bettercms://kit` resource and [kit-catalog.md](kit-catalog.md). The entry's notes are the
+field mapping and its pitfalls the review list; the rules below still decide the storage.
+
 - **Model each visual band as a `group` field (or a repeater), or a component instance.** The
   schema's shape decides whether the site can ever be componentized. The componentize lane finds
   a section in a `group`, a repeater, or two or more top-level keys sharing a prefix before `-` or

package/dist/skills/bettercms/references/detection.md

@@ -177,6 +177,11 @@ For each band, find the row whose strong signals all match. One match: classify.
 None: §9. The class picks the component family (`sectionType`) and the fields; it is never a
 field itself.
 
+Every group below is a category of the component kit. Once a band is classified, open the
+closest kit entry (the chooser in [kit-scenarios.md](kit-scenarios.md), the full list in the
+`bettercms://kit` resource or [kit-catalog.md](kit-catalog.md)), map it by that entry's notes and
+check its pitfalls before you write.
+
 | Confidence | Evidence | Action |
 |---|---|---|
 | High | A unique structural or vendor signal: `<form action="/cart/add">`, `role="tablist"`, JSON-LD of the right type | Model it |
@@ -229,7 +234,17 @@ field itself.
 | Long-form | Blog post | `<article>` with one `h1`, a byline, a hero image, a rich body |
 | Long-form | Docs page | Left nav tree, article, right "On this page" anchors, prev and next |
 | Long-form | Recipe, job, event detail | JSON-LD of that type, or the matching plugin classes |
+| Long-form | Help article | "Was this article helpful?" at the end, a Help Center breadcrumb, numbered steps with screenshots |
+| Long-form | Glossary or curriculum | An A–Z letter bar over `<dl>` terms; or "Module 1" accordions of lesson rows with durations |
 | Company | Team or leadership | Headshots with name and role; leadership adds C-level titles, bio modals, Board headings |
+| Company | Careers or job | Job rows under department headings linking to a hiring board; or "What you'll do", a salary range, JobPosting JSON-LD |
+| Company | Values or press kit | Three to eight headed value blocks and a perks grid; or logo tiles with SVG and PNG downloads |
+| Events | Events list | Rows led by a big day and short month (12 NOV), Upcoming and Past tabs, "Get tickets" per row |
+| Events | Webinar | A date with a time zone, a registration form beside speakers, "Watch on demand" |
+| Places | Locations or location page | A map beside an address list, hours rows per day, `data-lat`; or one address with `tel:` and Restaurant JSON-LD |
+| Places | Menu | Section headings with dish and price per line, dietary letter codes and a key, "MP" |
+| Data | Calculator or configurator | Range and number inputs with listeners and an `<output>`, no submit; or "Step 1 of 3" option cards with "+$60" |
+| Data | Countdown or poll | Digits as dd:hh:mm:ss with `data-end`; or one question with radio inputs and a Vote button |
 | Data | Table | `<table>` with `<th scope="col">`, more than two rows, a `<caption>` |
 | Data | Chart or map | An `<svg>` with axis ticks or a chart library global; a Leaflet, Mapbox or Google container |
 | Data | Embed or code | A third-party `<iframe>` or script widget; `<pre><code class="language-*">` |