schema-markup
ACTIVATE when the user asks for Schema.org structured data (JSON-LD) to earn rich results — FAQ, Product, Article, Breadcrumb, Organization, HowTo, Review, LocalBusiness, Event, Recipe. Trigger phrases: 'schema markup', 'structured data', 'JSON-LD', 'rich snippets', 'rich results', 'FAQ schema', 'product schema', 'article schema'. For technical SEO diagnostics, see seo-audit.
- License 许可
- MIT
- 最近更新
- 2026-10-13
- Stars
- ★ 9
- Forks
- 2
01 前言 Front Matter
- name
- schema-markup
- description
- ACTIVATE when the user asks for Schema.org structured data (JSON-LD) to earn rich results — FAQ, Product, Article, Breadcrumb, Organization, HowTo, Review, LocalBusiness, Event, Recipe. Trigger phrases: 'schema markup', 'structured data', 'JSON-LD', 'rich snippets', 'rich results', 'FAQ schema', 'product schema', 'article schema'. For technical SEO diagnostics, see seo-audit.
02 资源文件 3
- 参考文档.skillkit.json216 B
- 参考文档index.json512 B
- 参考文档references/schema-types.md9.4 KB
03 SKILL.md 正文
Schema Markup Generator Skill
You are an expert in Schema.org structured data and Google's rich results requirements. Generate valid, complete JSON-LD markup that maximizes eligibility for Google rich results.
Supported Schema Types
This skill supports Article/BlogPosting/NewsArticle, Product, FAQPage, HowTo, Organization,
LocalBusiness, BreadcrumbList, and Review/AggregateRating. When the user asks for schema,
determine which type(s) are appropriate based on the page content, then pull the matching
JSON-LD template and Google requirements from
references/schema-types.md. Most pages need 2-4 types combined
via @graph — see the "Multi-Schema Pages" section there.
Generation Process
When the user asks for schema markup:
- Determine page type - Ask what kind of page this is for (or infer from context)
- Gather information - Ask for or collect the required fields. If the user provides a URL, fetch it to extract data.
- Select schema types - Choose all applicable schemas (most pages need 2-4 types)
- Generate JSON-LD - Create complete, valid markup
- Validate - Check against Google's requirements for each type
- Provide implementation instructions - Tell the user exactly where to place it
Implementation Instructions
For Next.js App Router:
// In your page component or layout
export default function Page() {
const jsonLd = {/* generated schema */};
return (
<>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
{/* page content */}
</>
);
}
For Next.js with next/head (Pages Router):
import Head from 'next/head';
export default function Page() {
const jsonLd = {/* generated schema */};
return (
<>
<Head>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
</Head>
{/* page content */}
</>
);
}
For plain HTML:
<head>
<script type="application/ld+json">
{/* generated schema */}
</script>
</head>
Validation
After generating the markup, remind the user to validate using:
- Google Rich Results Test: https://search.google.com/test/rich-results
- Schema.org Validator: https://validator.schema.org/
Common Mistakes to Avoid
- Do not add schema for content that is not visible on the page
- Do not use
Reviewschema for self-serving reviews of your own business - Do not markup content behind a paywall as
isAccessibleForFree: true - Do not use fake or placeholder data in production schema
- Do not add
AggregateRatingwithout actual user reviews - Always use absolute URLs, never relative
- Always use ISO 8601 date format
priceValidUntilmust be a future dateavailabilitymust use full Schema.org URL (e.g.,https://schema.org/InStock)- Image URLs must be crawlable and indexable
04 同仓库更多 Skills
vitest-test-conventions
ACTIVATE when writing Vitest tests, creating test files, using vi.fn()/vi.mock()/vi.spyOn(), or test factories. ACTIVATE for 'Vitest', 'it.each', 'NestJS testing module', 'supertest', 'vi.fn', 'vi.mock', 'spyOn'. Provides Vitest/NestJS-specific testing patterns; cross-language testing principles (DAMP, AAA, spy over mock, what NOT to test) live in craft:testing-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), TDD workflow/iterations (see vitest:vitest-tdd-workflow), PHP/PHPUnit tests (see phpunit:php-test-conventions).
vitest-tdd-workflow
ACTIVATE when building new features, endpoints, or user stories using TDD with Vitest in a TypeScript/NestJS context. ACTIVATE for '/feature-tdd-dev', 'TDD', 'red-green-refactor' in TS context. Provides Vitest/NestJS-specific TDD examples and commands; cross-language TDD workflow (cross-layer iterations, RED-GREEN-REFACTOR, working app, bug-fix-first-test, mocks-hiding-bugs) lives in craft:tdd-workflow-principles. DO NOT use for: node:test files (a file importing node:test) or a project whose tests run under node --test (see node-test:node-test-conventions), test writing conventions (see vitest:vitest-test-conventions), PHP TDD (see phpunit:php-tdd-workflow).
ts-refactoring
ACTIVATE when refactoring TypeScript code. ACTIVATE for 'refactor', 'extract', 'redesign', 'simplify', or 'clean up' in a TypeScript / Node / NestJS context. This skill provides TS-specific examples for the cross-language refactoring rules defined in craft:refactoring-principles. DO NOT use for: writing new features from scratch, general OOP patterns (see ts-oop).
ts-ports-adapters
ACTIVATE when a TypeScript codebase with no dependency-injection container has to declare a port and wire its adapter — a repository, a clock, an id generator, an event dispatcher the domain depends on. ACTIVATE for 'port', 'adapter', 'SPI', 'dependency inversion' or 'composition root' in a codebase that wires its dependencies by hand. Covers: the port as a type of functions in the domain layer, the adapter as an object literal annotated with it, the handler that takes its dependencies first and its data second, the composition root in the infrastructure layer, and the in-memory stub that substitutes for the adapter in a unit test. DO NOT use for: NestJS, or any container-based DI with decorators and tokens (see nest-ddd-conventions), aggregate operations and smart constructors (see ddd-ts-fp), the Result type itself (see ts-functional).
ts-oop
ACTIVATE when designing TypeScript classes, and the value objects or collections modelled as classes, or when the user asks about object design, encapsulation, Tell Don't Ask, or Symbol.iterator. Provides TS-specific examples for the cross-language OOP rules defined in craft:oop-principles, plus TS-specific patterns (Symbol.iterator, branded types for primitive identifiers). DO NOT use for: a value object or an aggregate modelled as an immutable record rather than a class (see ddd-ts-fp), refactoring methodology (see ts-refactoring).
ts-layer-boundaries
ACTIVATE when wiring a Worker entry point, a Router, a controller, or a domain event consumer in a TypeScript CQRS codebase, or when deciding where a port belongs. ACTIVATE for 'composition root', 'layer boundary', 'ESLint zones', 'domain must not import infrastructure'. Covers: the *Worker.ts composition root, the curried consumer, Router wiring of command endpoints, the five-gesture controller, the domain-to-infrastructure import boundary enforced by ESLint, infrastructure-only ports, in-memory doubles for every port, the read-can-reach-write asymmetry, and read endpoints going through a domain handler. DO NOT use for: the port's own shape and adapter binding (see ts-ports-adapters), the Result type (see ts-functional), domain event structure (see ts-ddd-events).