@supatent/skills 0.3.0 → 0.5.0

package/skills/supatent-content-landing/landing-sections.md

@@ -0,0 +1,360 @@
+# Landing Page Section Catalog
+
+Defines the schemas created by the landing page content skill. The SKILL.md references this file for schema generation. Each section is either a singleton (one content item) or a collection (multiple items).
+
+## Category 1: Above the Fold
+
+### landing-hero (Singleton)
+
+Main hero section with headline, subheadline, and call-to-action.
+
+```json
+{
+  "slug": "landing-hero",
+  "name": "Landing Hero",
+  "description": "Main hero section with headline, subheadline, and call-to-action",
+  "isSingleton": true,
+  "fields": [
+    { "slug": "headline", "name": "Headline", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "subheadline", "name": "Subheadline", "type": "text", "interface": "textarea", "order": 1 },
+    { "slug": "cta-text", "name": "CTA Text", "type": "text", "interface": "textInput", "order": 2 },
+    { "slug": "cta-url", "name": "CTA URL", "type": "text", "interface": "textInput", "order": 3 },
+    { "slug": "hero-image", "name": "Hero Image", "type": "image", "interface": "singleImage", "order": 4 }
+  ]
+}
+```
+
+Image guidance: Hero image: 1920x1080px or 16:9 ratio. Required for visual impact.
+
+### landing-announcement (Singleton)
+
+Top banner bar for announcements or promotions.
+
+```json
+{
+  "slug": "landing-announcement",
+  "name": "Landing Announcement",
+  "description": "Top banner bar for announcements or promotions",
+  "isSingleton": true,
+  "fields": [
+    { "slug": "text", "name": "Text", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "link-text", "name": "Link Text", "type": "text", "interface": "textInput", "order": 1 },
+    { "slug": "link-url", "name": "Link URL", "type": "text", "interface": "textInput", "order": 2 }
+  ]
+}
+```
+
+Image guidance: No images required.
+
+## Category 2: Social Proof
+
+### landing-logo (Collection)
+
+Client or partner logos for trust building.
+
+```json
+{
+  "slug": "landing-logo",
+  "name": "Landing Logo",
+  "description": "Client or partner logos for trust building",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "name", "name": "Name", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "logo-image", "name": "Logo Image", "type": "image", "interface": "singleImage", "order": 1 }
+  ]
+}
+```
+
+Default count: 5. Image guidance: Logo image: 200x80px or similar horizontal format. Required per logo.
+
+### landing-testimonial (Collection)
+
+Customer quotes and social proof.
+
+```json
+{
+  "slug": "landing-testimonial",
+  "name": "Landing Testimonial",
+  "description": "Customer quotes and social proof",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "quote", "name": "Quote", "type": "text", "interface": "textarea", "order": 0 },
+    { "slug": "author-name", "name": "Author Name", "type": "text", "interface": "textInput", "order": 1 },
+    { "slug": "author-title", "name": "Author Title", "type": "text", "interface": "textInput", "order": 2 },
+    { "slug": "author-company", "name": "Author Company", "type": "text", "interface": "textInput", "order": 3 },
+    { "slug": "author-image", "name": "Author Image", "type": "image", "interface": "singleImage", "order": 4 }
+  ]
+}
+```
+
+Default count: 3. Image guidance: Author image: 100x100px square. Optional but recommended.
+
+### landing-stat (Collection)
+
+Key metrics and statistics.
+
+```json
+{
+  "slug": "landing-stat",
+  "name": "Landing Stat",
+  "description": "Key metrics and statistics",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "value", "name": "Value", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "label", "name": "Label", "type": "text", "interface": "textInput", "order": 1 },
+    { "slug": "description", "name": "Description", "type": "text", "interface": "textInput", "order": 2 }
+  ]
+}
+```
+
+Default count: 3. Image guidance: No images required.
+
+## Category 3: Features and Info
+
+### landing-feature (Collection)
+
+Product features with title and description.
+
+```json
+{
+  "slug": "landing-feature",
+  "name": "Landing Feature",
+  "description": "Product features with title and description",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "title", "name": "Title", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "description", "name": "Description", "type": "text", "interface": "textarea", "order": 1 },
+    { "slug": "icon-image", "name": "Icon Image", "type": "image", "interface": "singleImage", "order": 2 }
+  ]
+}
+```
+
+Default count: 3. Image guidance: Icon image: 64x64px or SVG icon. Optional.
+
+### landing-pricing-tier (Collection)
+
+Pricing plans with features and CTA.
+
+```json
+{
+  "slug": "landing-pricing-tier",
+  "name": "Landing Pricing Tier",
+  "description": "Pricing plans with features and CTA",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "name", "name": "Name", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "price", "name": "Price", "type": "number", "interface": "numberInput", "order": 1 },
+    { "slug": "price-period", "name": "Price Period", "type": "text", "interface": "textInput", "order": 2 },
+    { "slug": "description", "name": "Description", "type": "text", "interface": "textarea", "order": 3 },
+    { "slug": "features-list", "name": "Features List", "type": "markdown", "interface": "markdownEditor", "order": 4 },
+    { "slug": "cta-text", "name": "CTA Text", "type": "text", "interface": "textInput", "order": 5 },
+    { "slug": "cta-url", "name": "CTA URL", "type": "text", "interface": "textInput", "order": 6 },
+    { "slug": "is-featured", "name": "Is Featured", "type": "text", "interface": "textInput", "order": 7 }
+  ]
+}
+```
+
+Default count: 3. Notes: `features-list` uses markdown with bullet list format (one feature per bullet). `is-featured` uses "true" or "false" as string values (no boolean field type in Supatent). Image guidance: No images required.
+
+### landing-team-member (Collection)
+
+Team members with name, role, and bio.
+
+```json
+{
+  "slug": "landing-team-member",
+  "name": "Landing Team Member",
+  "description": "Team members with name, role, and bio",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "name", "name": "Name", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "role", "name": "Role", "type": "text", "interface": "textInput", "order": 1 },
+    { "slug": "bio", "name": "Bio", "type": "markdown", "interface": "markdownEditor", "order": 2 },
+    { "slug": "photo", "name": "Photo", "type": "image", "interface": "singleImage", "order": 3 }
+  ]
+}
+```
+
+Default count: 3. Image guidance: Photo: 400x400px square. Required for team display.
+
+### landing-faq-item (Collection)
+
+Frequently asked questions and answers.
+
+```json
+{
+  "slug": "landing-faq-item",
+  "name": "Landing FAQ Item",
+  "description": "Frequently asked questions and answers",
+  "isSingleton": false,
+  "fields": [
+    { "slug": "question", "name": "Question", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "answer", "name": "Answer", "type": "markdown", "interface": "markdownEditor", "order": 1 }
+  ]
+}
+```
+
+Default count: 5. Image guidance: No images required. FAQ answers use markdown for rich formatting (links, lists, emphasis).
+
+## Category 4: Conversion and Footer
+
+### landing-cta (Singleton)
+
+Primary call-to-action section.
+
+```json
+{
+  "slug": "landing-cta",
+  "name": "Landing CTA",
+  "description": "Primary call-to-action section",
+  "isSingleton": true,
+  "fields": [
+    { "slug": "headline", "name": "Headline", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "description", "name": "Description", "type": "text", "interface": "textarea", "order": 1 },
+    { "slug": "cta-text", "name": "CTA Text", "type": "text", "interface": "textInput", "order": 2 },
+    { "slug": "cta-url", "name": "CTA URL", "type": "text", "interface": "textInput", "order": 3 },
+    { "slug": "secondary-cta-text", "name": "Secondary CTA Text", "type": "text", "interface": "textInput", "order": 4 },
+    { "slug": "secondary-cta-url", "name": "Secondary CTA URL", "type": "text", "interface": "textInput", "order": 5 }
+  ]
+}
+```
+
+Image guidance: No images required.
+
+### landing-footer (Singleton)
+
+Page footer with company info.
+
+```json
+{
+  "slug": "landing-footer",
+  "name": "Landing Footer",
+  "description": "Page footer with company info",
+  "isSingleton": true,
+  "fields": [
+    { "slug": "company-name", "name": "Company Name", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "tagline", "name": "Tagline", "type": "text", "interface": "textInput", "order": 1 },
+    { "slug": "copyright-text", "name": "Copyright Text", "type": "text", "interface": "textInput", "order": 2 }
+  ]
+}
+```
+
+Image guidance: No images required.
+
+### landing-metadata (Singleton)
+
+Page metadata and structured data for SEO.
+
+```json
+{
+  "slug": "landing-metadata",
+  "name": "Landing Metadata",
+  "description": "Page metadata and structured data for SEO",
+  "isSingleton": true,
+  "fields": [
+    { "slug": "page-title", "name": "Page Title", "type": "text", "interface": "textInput", "order": 0 },
+    { "slug": "page-description", "name": "Page Description", "type": "text", "interface": "textarea", "order": 1 },
+    { "slug": "json-ld", "name": "Organization Data", "type": "jsonLd", "interface": "jsonLdEditor", "order": 2 }
+  ]
+}
+```
+
+Conditional JSON-LD fields added based on section selection:
+- If FAQ section is selected, add: `{ "slug": "json-ld-faq", "name": "FAQ Data", "type": "jsonLd", "interface": "jsonLdEditor", "order": 3 }`
+- If pricing section is selected (SaaS product), add: `{ "slug": "json-ld-product", "name": "Product Data", "type": "jsonLd", "interface": "jsonLdEditor", "order": 4 }`
+
+Image guidance: No images required.
+
+## JSON-LD Guidance
+
+The landing-metadata singleton uses JSON-LD structured data fields. Each field stores a complete JSON-LD object.
+
+### Organization (always present)
+
+Used on every landing page. Stored in the `json-ld` field.
+
+- Required: `@context`, `@type`
+- Recommended: `name`, `url`, `description`
+- Optional: `sameAs` (social links array)
+- Do NOT include `logo` unless user provides an actual URL (asset slugs fail URI validation)
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  "name": "Company Name",
+  "url": "https://example.com",
+  "description": "Brief company description.",
+  "sameAs": [
+    "https://twitter.com/example",
+    "https://linkedin.com/company/example"
+  ]
+}
+```
+
+### FAQPage (conditional)
+
+Only when `landing-faq-item` section is selected. Stored in the `json-ld-faq` field. Generate FAQ entries from landing-faq-item content items.
+
+- Required: `@context`, `@type`, `mainEntity` (array of Question objects, min 1)
+- Each Question: `@type: "Question"`, `name`, `acceptedAnswer`
+- Each Answer: `@type: "Answer"`, `text`
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "What is your product?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Our product helps you do X."
+      }
+    }
+  ]
+}
+```
+
+### SoftwareApplication (conditional)
+
+Only when `landing-pricing-tier` section is selected for a SaaS product. Stored in the `json-ld-product` field. Do NOT use `Product` type -- it requires `image` which conflicts with the no-image decision. If the product is physical (not SaaS), skip the product JSON-LD entirely.
+
+- Required: `@context`, `@type`, `name`
+- Recommended: `applicationCategory`, `description`, `offers` (array of Offer objects)
+- Each Offer: `@type: "Offer"`, `price`, `priceCurrency`
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "Product Name",
+  "applicationCategory": "BusinessApplication",
+  "description": "Brief product description.",
+  "offers": [
+    {
+      "@type": "Offer",
+      "price": "29",
+      "priceCurrency": "USD"
+    }
+  ]
+}
+```
+
+## Section Selection Summary
+
+| Section | Type | Default Count | Required Images |
+|---------|------|---------------|-----------------|
+| landing-hero | singleton | 1 | hero-image (1920x1080) |
+| landing-announcement | singleton | 1 | none |
+| landing-logo | collection | 5 | logo-image (200x80) |
+| landing-testimonial | collection | 3 | author-image (100x100, optional) |
+| landing-stat | collection | 3 | none |
+| landing-feature | collection | 3 | icon-image (64x64, optional) |
+| landing-pricing-tier | collection | 3 | none |
+| landing-team-member | collection | 3 | photo (400x400) |
+| landing-faq-item | collection | 5 | none |
+| landing-cta | singleton | 1 | none |
+| landing-footer | singleton | 1 | none |
+| landing-metadata | singleton | 1 | none |

package/skills/{core → supatent-core}/SKILL.md

@@ -42,7 +42,7 @@ Dev mode provides automatic validation on file save and real-time sync with the
 
 ### 3. Check installed skill version
 
-Read the version from `.claude/skills/supatent/.manifest.json` (the `version` field).
+Read the version from `.claude/skills/supatent-core/.manifest.json` (the `version` field). If that file does not exist, check `.claude/skills/supatent/.manifest.json` (legacy path).
 
 Then check the latest published version:
 ```bash
@@ -70,7 +70,7 @@ npm view @supatent/skills version 2>/dev/null
 
 **Interface determines the UI editor**, not the storage format. For example, `text` with `textInput` gives a single-line input; `text` with `textarea` gives a multi-line editor.
 
-For full details on field validation rules, constraints, and JSON-LD structured data types, read `../references/schema-reference.md`.
+For full details on field validation rules, constraints, and JSON-LD structured data types, read `../supatent-references/schema-reference.md`.
 
 ## Quick Reference: File Locations
 
@@ -98,7 +98,7 @@ Load these files when you need detailed information beyond the quick references
 
 ### Schema details
 
-**File:** `../references/schema-reference.md`
+**File:** `../supatent-references/schema-reference.md`
 
 **Read when:** Creating or modifying schemas, adding fields, choosing field types and interfaces, working with JSON-LD structured data, or checking naming conventions.
 
@@ -106,7 +106,7 @@ Load these files when you need detailed information beyond the quick references
 
 ### Workflow details
 
-**File:** `../references/workflow-reference.md`
+**File:** `../supatent-references/workflow-reference.md`
 
 **Read when:** Running CLI commands (init, dev, pull, push, validate, status, merge), troubleshooting validation errors, resolving sync conflicts, or understanding the content authoring flow.
 

package/skills/supatent-references/schema-reference.md

@@ -0,0 +1,289 @@
+# Schema Reference
+
+> **Source of truth:** `packages/cli/src/constants.ts` and `packages/cli/src/types.ts` define the canonical field types, interfaces, and validation rules. `packages/jsonld-schemas/src/registry.ts` defines supported JSON-LD types. Phase 45 CI drift check will verify this file stays in sync with those sources.
+
+## Field Types and Interfaces
+
+Every field in a schema has a `type` and an `interface`. The type determines the data format; the interface determines the editing UI.
+
+| Type | Interface | Value Format | Notes |
+|------|-----------|-------------|-------|
+| `text` | `textInput` | `string` | Single-line text input |
+| `text` | `textarea` | `string` | Multi-line text area |
+| `number` | `numberInput` | `number` or `null` | Numeric input; `null` represents empty (distinct from `0`) |
+| `image` | `singleImage` | `string` or `null` | Asset slug string (e.g., `"hero-image"`), or legacy object with `assetPath` |
+| `image` | `multiImage` | `string[]` | Array of asset slug strings (e.g., `["hero", "banner"]`) |
+| `markdown` | `markdownEditor` | `string` | Markdown-formatted text |
+| `jsonLd` | `jsonLdEditor` | `object` | JSON-LD object with `@context` and `@type` |
+
+**Important:** Each interface is valid only for its corresponding type. Using `textarea` with a `number` type (or any other mismatch) will fail validation.
+
+### Interface-Type Compatibility Map
+
+```
+text       -> textInput, textarea
+number     -> numberInput
+image      -> singleImage, multiImage
+markdown   -> markdownEditor
+jsonLd     -> jsonLdEditor
+```
+
+## Schema File Structure
+
+Schema files live at `.supatent/schema/{slug}.json`. The complete structure:
+
+```json
+{
+  "slug": "blog-post",
+  "name": "Blog Post",
+  "description": "Articles for the company blog",
+  "isSingleton": false,
+  "fields": [
+    {
+      "slug": "title",
+      "name": "Title",
+      "description": "The post headline",
+      "type": "text",
+      "interface": "textInput",
+      "order": 0
+    },
+    {
+      "slug": "body",
+      "name": "Body",
+      "type": "markdown",
+      "interface": "markdownEditor",
+      "order": 1
+    }
+  ]
+}
+```
+
+### Property Reference
+
+| Property | Required | Type | Description |
+|----------|----------|------|-------------|
+| `slug` | Yes | `string` | Must match filename (without `.json`). Lowercase alphanumeric with hyphens. |
+| `name` | Yes | `string` | Display name. Minimum 1 character. |
+| `description` | No | `string` | Optional description of the schema's purpose. |
+| `isSingleton` | Yes | `boolean` | Whether this schema has exactly one content item per locale. |
+| `fields` | Yes | `array` | Array of field definitions. |
+
+### Field Property Reference
+
+| Property | Required | Type | Description |
+|----------|----------|------|-------------|
+| `slug` | Yes | `string` | Unique within the schema. Lowercase alphanumeric with hyphens. |
+| `name` | Yes | `string` | Display name. Minimum 1 character. |
+| `description` | No | `string` | Optional description of the field's purpose. |
+| `type` | Yes | `string` | One of: `text`, `number`, `image`, `markdown`, `jsonLd` |
+| `interface` | Yes | `string` | Must be valid for the field's type (see compatibility map above). |
+| `order` | Yes | `number` | Integer >= 0. Controls display order in the editor. |
+
+## Validation Rules
+
+These rules are enforced by `packages/cli/src/lib/validation.ts` using AJV (JSON Schema draft-07).
+
+### Slug Pattern
+
+All slugs (schema slugs, field slugs, content item slugs) must match:
+
+```
+^[a-z0-9]+(?:-[a-z0-9]+)*$
+```
+
+Valid: `blog-post`, `title`, `cover-image`, `my-post-1`
+Invalid: `Blog_Post`, `my post`, `_title`, `post--double`, `-leading`
+
+### Required Schema Properties
+
+The top-level object requires: `slug`, `name`, `isSingleton`, `fields`.
+
+### Required Field Properties
+
+Each field object requires: `slug`, `name`, `type`, `interface`, `order`.
+
+### Additional Rules
+
+- **Slug-filename match:** The `slug` value must match the filename (e.g., `blog-post.json` must have `"slug": "blog-post"`).
+- **Unique field slugs:** No two fields within the same schema can share a slug.
+- **Interface-type compatibility:** The `interface` must be valid for the given `type` (see compatibility map).
+- **Order minimum:** The `order` field must be a number >= 0.
+- **Name minimum length:** Both schema `name` and field `name` must have at least 1 character.
+
+## Singleton vs Collection
+
+### Singleton (`isSingleton: true`)
+
+One content item per locale. The content file **must** use slug `"default"`.
+
+File path: `.supatent/content/{schemaSlug}/default.{locale}.json`
+
+Use for: site settings, homepage hero, footer, navigation, about page, any content that exists as a single instance.
+
+Example schemas: `site-settings`, `homepage-hero`, `footer`, `about-page`
+
+### Collection (`isSingleton: false`)
+
+Multiple content items, each with its own slug.
+
+File path: `.supatent/content/{schemaSlug}/{itemSlug}.{locale}.json`
+
+Use for: blog posts, team members, FAQ items, product listings, testimonials, any content with multiple entries.
+
+Example schemas: `blog-post`, `team-member`, `faq-item`, `product`
+
+### Decision Guide
+
+| Question | Yes -> Singleton | No -> Collection |
+|----------|-----------------|-----------------|
+| Is there only ever one of this? | Singleton | Collection |
+| Would "list all X" make sense? | Collection | Singleton |
+| Does it have its own slug/URL? | Collection | Singleton |
+
+## Content File Structure
+
+Content files live at `.supatent/content/{schemaSlug}/{itemSlug}.{locale}.json`.
+
+The file is a flat JSON object where keys are field slugs from the schema:
+
+```json
+{
+  "title": "My First Blog Post",
+  "body": "# Welcome\n\nThis is the post content in **markdown**.",
+  "cover-image": "blog-hero",
+  "read-time": 5
+}
+```
+
+### Value Types by Field Type
+
+| Field Type | Expected Value | Example |
+|------------|---------------|---------|
+| `text` | `string` | `"Hello world"` |
+| `number` | `number` or `null` | `42` or `null` |
+| `image` (singleImage) | `string` (asset slug) or `null` | `"hero-image"` |
+| `image` (multiImage) | `string[]` (asset slugs) | `["photo-1", "photo-2"]` |
+| `markdown` | `string` | `"# Heading\n\nParagraph"` |
+| `jsonLd` | `object` | `{ "@context": "https://schema.org", "@type": "Article" }` |
+
+### File Naming
+
+- Collection: `{itemSlug}.{locale}.json` (e.g., `my-post.en.json`, `my-post.fr.json`)
+- Singleton: `default.{locale}.json` (e.g., `default.en.json`)
+- Locale format: `xx` or `xx-XX` (e.g., `en`, `en-US`, `fr`, `fr-CA`)
+
+### Content Validation Behavior
+
+- **Unknown fields** (not in schema) produce errors with "did you mean?" suggestions using Levenshtein distance.
+- **Missing fields** produce errors (required), except `jsonLd` fields which produce warnings.
+- **Wrong value types** produce errors with examples of correct format.
+
+## JSON-LD Types
+
+Supatent supports 23 JSON-LD types for structured data, validated by the `@supatent/jsonld-schemas` package. Types are organized by category.
+
+To use JSON-LD: add a field with `type: "jsonLd"` and `interface: "jsonLdEditor"`. The content value must include `@context` and `@type`:
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Article",
+  "headline": "My Article Title",
+  "author": { "@type": "Person", "name": "Jane Doe" }
+}
+```
+
+### Commerce
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `Product` | Product | Physical or digital products for sale |
+| `SoftwareApplication` | Software App | Software applications and tools |
+| `VacationRental` | Vacation Rental | Short-term rental properties |
+
+### Content
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `Article` | Article | News articles, blog posts, editorial content |
+| `Recipe` | Recipe | Cooking and food preparation instructions |
+| `FAQPage` | FAQ Page | Frequently asked questions pages |
+| `Review` | Review | Product or service reviews |
+| `DiscussionForumPosting` | Discussion Forum Posting | Forum threads and community posts |
+| `QAPage` | Q&A Page | Question and answer pages |
+
+### Local
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `LocalBusiness` | Local Business | Physical business locations |
+| `Event` | Event | Events, conferences, meetups |
+
+### Education
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `Course` | Course | Educational courses and programs |
+| `Quiz` | Education Q&A | Educational quizzes and assessments |
+| `MathSolver` | Math Solver | Mathematical problem solvers |
+
+### Media
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `VideoObject` | Video | Video content and clips |
+| `Movie` | Movie | Feature films and movies |
+| `ImageMetadata` | Image Metadata | Image licensing and attribution |
+
+### People and Organizations
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `Organization` | Organization | Companies, nonprofits, institutions |
+| `ProfilePage` | Profile Page | Personal or professional profile pages |
+| `EmployerAggregateRating` | Employer Rating | Aggregated employer ratings and reviews |
+| `JobPosting` | Job Posting | Job listings and opportunities |
+
+### Navigation
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `BreadcrumbList` | Breadcrumb List | Site navigation breadcrumbs |
+
+### Data
+
+| @type | Label | Description |
+|-------|-------|-------------|
+| `Dataset` | Dataset | Structured data collections |
+
+### JSON-LD Validation
+
+- The `@context` field must be `"https://schema.org"`.
+- The `@type` must be one of the 23 supported types listed above.
+- Additional properties are validated against schema.org specifications by the `@supatent/jsonld-schemas` package (deep property checking).
+- Deprecated types generate warnings, not errors.
+- Empty `jsonLd` fields (missing from content) produce warnings rather than errors.
+
+## Naming Conventions
+
+### Schema Slugs
+
+Use lowercase-hyphenated: `blog-post`, `site-settings`, `team-member`
+
+Do not use: `blogPost`, `Blog_Post`, `BLOG-POST`
+
+### Field Slugs
+
+Use lowercase-hyphenated: `cover-image`, `read-time`, `full-name`
+
+Do not use: `coverImage`, `cover_image`, `CoverImage`
+
+### Display Names
+
+Use Title Case: `"Blog Post"`, `"Cover Image"`, `"Read Time"`
+
+### Content Item Slugs
+
+Use lowercase-hyphenated: `my-first-post`, `about-us`, `john-doe`
+
+Singleton items always use: `default`