schema-generatorlisted

# Schema Generator ## When This Skill Applies - Writing JSON-LD blocks for articles, FAQ pages, interviews, reviews, and tutorials - Shipping `llms.txt` so AI answer engines get a curated site map - Updating `robots.txt` to allow or deny specific AI crawler user agents - Wrapping a load-bearing passage as a citation capsule for answer-engine lift - Picking the right schema type when content does not fit the default `Article` - Validating structured data before publish using public validator URLs This skill is the executable counterpart to `skills/copywriting/references/aeo-geo-2026.md`. The reference explains *why*; this skill hands back templates, snippets, and a decision table. ## Placeholder Convention All templates in this skill and in `references/json-ld-schemas.md` use a single placeholder format: **`<ANGLE_SNAKE>`** — an `UPPER_SNAKE_CASE` token wrapped in angle brackets. | Rule | Example | |---|---| | Wrap every placeholder in `<` and `>` | `<AUTHOR_NAME>` | | Use `UPPER_SNAKE_CASE` for the inner name | `<HEADLINE_UP_TO_110_CHARS>` | | Include unit or format hints in the name when helpful | `<ISO_8601_DATETIME>`, `<BCP47_LANG_CODE>` | | Strip every `<ANGLE_SNAKE>` token before deploy | Find-and-replace pass with editor regex `<[A-Z0-9_]+>` | Editors can sweep for unresolved placeholders with a single regex: `<[A-Z0-9_]+>`. Any hit in a shipped JSON-LD file is a bug. ## Core Guidance ### 1. Schema Type Decision Table Pick one primary type per page. Add `Breadc