@typeroll/mcp-server 0.45.65 → 0.45.66

package/skills/tr-seo.md

@@ -36,7 +36,8 @@ read_site_settings
 ```
 
 For each page, check:
-- Is `seo_title` set? (if not, Google uses `title` + suffix — often fine)
+- Is `seo_title` set? (if not, Google uses `title` + suffix — often fine;
+  aim for 50–60 characters, longer gets truncated)
 - Is `seo_description` set? (150–160 chars, unique per page, includes keywords)
 - Is `og_image` set for the homepage and key landing pages?
 - Does the page have exactly one `<h1>`?
@@ -79,6 +80,20 @@ update_page page_id="home" patch={
 }
 ```
 
+### 3b. URL and article conventions
+
+When creating or moving pages:
+
+- Slugs are lowercase kebab-case: `our-services`, not `Our_Services`.
+- Reflect hierarchy in the address. A team member lives at `/team/jane-doe`
+  (set `path`, or use a content type whose `route_template` adds the
+  prefix), not at `/jane-doe`. Breadcrumbs and their BreadcrumbList schema
+  follow the resolved route.
+- Blog posts and news get `kind: "article"` and an `author`: that emits
+  Article JSON-LD and `og:type=article`. No author means no author in the
+  rich result.
+- Give shared pages, especially articles, their own `og_image`.
+
 ### 4. Add Open Graph images
 
 Set `og_image` on pages that get shared on social media. If the site has
@@ -116,6 +131,37 @@ repeating it on every page (`null` clears it):
 update_site_settings organization={"name":"Acme Studio","logo":"<cdn_url>","same_as":["https://www.linkedin.com/company/acme"]}
 ```
 
+**FAQ, recipe and event pages have tools.** They validate the input, build
+the schema.org JSON-LD and merge it into the page's `json_ld` (a node of the
+same type is replaced, anything else is kept). Use them instead of
+hand-writing JSON-LD, and copy the content from what the page visibly shows:
+
+```
+add_faq_schema page_id="faq" items=[
+  {"question": "Do you deliver on weekends?", "answer": "Yes, Saturdays 9–15."}
+]
+add_recipe_schema page_id="kanelbullar" name="Kanelbullar"
+  ingredients=["500 g vetemjöl", "2 tsk kanel"] instructions=["Blanda degen.", "Grädda i 225 °C."]
+  prep_time="PT1H30M" cook_time="PT10M" recipe_yield="24 bullar" image_url="<cdn_url>"
+add_event_schema page_id="sommarkonsert" name="Sommarkonsert"
+  start_date="2026-06-12T19:00:00+02:00" location_name="Stadshuset"
+  location_address="Storgatan 1, Sundsvall" offers_price=250 offers_currency="SEK"
+```
+
+Rules they enforce: FAQ needs at least one question with an answer; a recipe
+needs a name, ingredients and steps, durations are ISO 8601 (`PT30M`) and
+URLs absolute; an event needs a name and an ISO 8601 `start_date` (include
+the UTC offset), `end_date` not before it, and a price needs
+`offers_currency`. Read the returned `warnings`: a recipe without an image or
+an event without a location is valid but not eligible for Google's rich
+results. Like other content writes they land in the draft — `save: true` or
+`commit_working_copy` when approved.
+
+FAQ markup only belongs on a page that visibly presents those questions and
+answers; Google penalizes FAQ markup for content the page does not show.
+
+For other types write `json_ld` yourself:
+
 ```
 update_page page_id="home" patch={
   "json_ld": "{\"@context\":\"https://schema.org\",\"@type\":\"LocalBusiness\",\"name\":\"Acme Studio\",\"url\":\"https://acme.se\",\"telephone\":\"+46812345\",\"address\":{\"@type\":\"PostalAddress\",\"streetAddress\":\"Drottninggatan 1\",\"addressLocality\":\"Stockholm\",\"postalCode\":\"111 51\",\"addressCountry\":\"SE\"}}"
@@ -124,16 +170,25 @@ update_page page_id="home" patch={
 
 **Important:** JSON-LD goes in the `json_ld` field as a JSON *string*
 (not a nested object). The renderer injects it inside
-`<script type="application/ld+json">`.
+`<script type="application/ld+json">`. To keep several nodes on one page,
+store them as `{"@context":"https://schema.org","@graph":[…]}` — the
+`add_*_schema` tools do this for you. Read the page first: an update
+replaces the whole `json_ld` value.
 
 Common schemas worth adding:
 - Homepage: `LocalBusiness` or `Organization`
 - About: `AboutPage`
 - Contact: `ContactPage`
 - Blog articles: auto-generated from `kind:"article"` + `author`
-- Events: `Event` with `startDate`, `location`
+- FAQ, recipe and event pages: the `add_*_schema` tools above
 - Products: `Product` with `offers`
 
+**Instead of the `schema_markup` workflow.** That workflow runs the model with
+the Organization's own AI key; on a Site without that access it fails with
+`failure_code: "ai_not_enabled"`. Don't retry it. Do the same work here: read
+each published page, pick the one type it genuinely represents (or none),
+apply the tool or `json_ld` above, and tell the user you did it yourself.
+
 ### 6. robots.txt
 
 The default robots.txt allows all crawlers. Update if needed:

package/skills/tr-starter-design.md

@@ -0,0 +1,79 @@
+---
+name: tr-starter-design
+description: Reference for the default design new Typeroll sites start with — CSS variables, spacing, radii, container width, header and footer skeletons. Read it when a site is blank or clearly follows these conventions and you need new markup or CSS to fit in; skip it for sites with their own design.
+---
+
+# Starter design system
+
+A reference for the *default* design that ships with new Typeroll sites.
+The customer may have replaced it — always inspect the actual header partial
+(`read_partial partial_id="header"`) and an existing page before assuming any
+of this is in use. On a site with its own design, mirror what is there.
+
+## CSS variables
+
+Colors (set in site settings `colors`; each key becomes `--color-<key>`,
+`text_light` becomes `--color-text-light`):
+  --color-primary       brand CTAs, links, accents
+  --color-secondary     supporting brand color (rarely used)
+  --color-accent        a third highlight (badges, callouts)
+  --color-background    page background (the body)
+  --color-surface       slightly raised areas (header, footer, cards)
+  --color-text          body copy + headings
+  --color-text-light    secondary text (captions, meta, footer fine-print)
+
+For subtle borders/dividers that follow the text color without being heavy,
+use `color-mix(in srgb, var(--color-text) 8%, transparent)` (6% for very soft).
+
+Spacing scale:
+  --spacing-xs (0.25rem)  --spacing-sm (0.5rem)  --spacing-md (1rem)
+  --spacing-lg (2rem)     --spacing-xl (4rem)
+
+Layout:
+  --container-medium (1080px)  Center page content with
+    `max-width: var(--container-medium); margin: 0 auto; padding: var(--spacing-md);`
+  --container-narrow (720px) and --container-wide (1400px) exist for prose
+    and wide layouts.
+
+Radii:
+  --radius-sm (0.25rem)  --radius-md (0.5rem)  --radius-lg (1rem)
+
+Typography (set in site settings `fonts`):
+  --font-heading  Use for h1-h6 and brand wordmark
+  --font-body     Default for everything else
+  --font-size-base (the rem baseline)
+
+Block-mode pages get these through the blocks and named styles; reach for the
+variables in custom CSS, HTML-mode pages and template markup.
+
+## Default header skeleton
+
+Surface-tinted bar with a hairline bottom border. Brand text on the left
+in the heading font, bold, slight negative letter-spacing. Nav on the
+right. Last nav item is typically a primary CTA: `background:
+var(--color-primary); color: var(--color-background); border-radius:
+var(--radius-md)`.
+
+## Default footer skeleton
+
+Three-column responsive grid (brand+tagline / Site links / Get in touch),
+then a fine-print row with copyright + Typeroll attribution. Top border
+uses the same color-mix() recipe as the header.
+
+## When to use this
+
+- A brand new site, or one where the header partial still matches this
+  layout.
+- A page or block where the customer wants something that "fits the rest
+  of the site" and the rest follows these conventions.
+
+## When NOT to use this
+
+- The customer has a totally different design (e.g. dark mode, custom
+  utility classes, no CSS variables, migrated theme).
+- The customer says "use this brand color" — honor their literal request
+  instead of substituting a CSS variable.
+- Mid-edit on an existing page that doesn't follow these conventions —
+  match what's already there.
+- Choosing a new palette or fonts is brand work (the MCP recipe `tr-brand`),
+  not this reference.