How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

generate-frontmatter - Prompt

Name: generate-frontmatter
Author: bamr87

Prompt file imported from bamr87/it-journey (.github/prompts/generate-frontmatter.prompt.md). Copyright stays with the author.

Generate Jekyll Frontmatter (validator-aligned)

Return YAML frontmatter that passes CI on the first attempt. Constraints differ by content type — do not apply post rules to quests.

Hard Constraints — Posts, Docs, READMEs

Enforced by .github/workflows/frontmatter-validation.yml:

Field	Rule
`title`	30–60 chars
`description`	120–160 chars
`date`	ISO 8601 `YYYY-MM-DDTHH:MM:SS.sssZ`
`categories`	YAML list
`tags`	YAML list, ≥ 3 entries
`author`	non-empty string
`draft`	`false` unless caller specifies otherwise

Count title and description characters; state counts in a YAML comment. Fix and recount if out of bounds.

Optional brand keys (posts only): section_guide — a slug from _data/brand/sections/_registry.yml (e.g. devops, devops-news-muse). Usually inferred from the post's folder, so include it only to override (e.g. a muse). voice_profile overrides the guide's profile; normally omit. Neither is CI-validated. See brand.instructions.md.

Hard Constraints — Quests (`pages/_quests/**/*.md`)

Enforced by test/quest-validator/quest_validator.py. Read .github/instructions/quest.instructions.md and .frontmatter/templates/quests.md — do not invent fields.

Field	Rule
`title`	10–100 chars (quest rule — not the 30–60 post rule)
`description`	150–300 chars (quest rule — not the 120–160 post rule)
`level`	quoted 4-digit binary: `"1100"`
`difficulty`	exact emoji+label: `"🟢 Easy"`, `"🟡 Medium"`, `"🔴 Hard"`, `"⚔️ Epic"`
`estimated_time`	`"X-X hours"` or `"X-X minutes"`
`primary_technology`	lowercase string
`quest_type`	`main_quest` \| `side_quest` \| `bonus_quest` \| `epic_quest`
`skill_focus`	`frontend` \| `backend` \| `devops` \| `security` \| `data-engineering` \| `fullstack`
`learning_style`	`hands-on` \| `conceptual` \| `project-based`
`quest_series`	non-empty string
`fmContentType`	`quest` (playable quests)
`layout`	`quest` (playable quests)
`permalink`	must match `quest_type` — see § Permalink below
`keywords`	object with `primary` and `secondary` lists

Recommended: quest_line, quest_arc, prerequisites, quest_dependencies, rewards, validation_criteria, lastmod.

Level READMEs (pages/_quests/XXXX/README.md): use layout: quest-collection, permalink: /quests/XXXX/, quoted level. Do not set fmContentType: quest.

Quest permalink by type

`quest_type`	`permalink`
`main_quest`	`/quests/XXXX/<slug>/`
`side_quest`	`/quests/XXXX/side-quests/<slug>/`
`bonus_quest` / `epic_quest`	`/quests/codex/<slug>/`

Quest dependency URLs

Use full canonical paths in quest_dependencies — never bare slugs:

quest_dependencies:
  required_quests:
    - /quests/0000/terminal-fundamentals/
  unlocks_quests:
    - /quests/0010/next-quest/ # planned quest

YAML quoting

Quote 4-digit levels and numeric tags to avoid Jekyll gsub errors:

level: "1100"
tags: ["1100", docker, main_quest]

Per-Type Summary

Type	Path	Extra rules
`post`	`pages/_posts/**`	Post title/description lengths; `learning_objectives` recommended
`quest`	`pages/_quests/**` (not templates)	Quest title/description lengths; full quest field set above
`doc`	`pages/_docs/**`	Post hard constraints; omit quest-only fields
`readme`	`pages/**/README.md`	Post hard constraints for Jekyll-processed READMEs
`note`	`pages/_notes/**`	Post hard constraints only

Output Format

Return valid YAML between --- fences with a comment showing character counts:

---
# title=48 chars, description=172 chars — quest bounds OK
title: "Docker Mastery: Container Orchestration Fundamentals"
description: "Learn container orchestration with Docker Compose: multi-service networking, volume persistence, environment configuration, and production-ready local dev stacks for teams."
date: 2026-05-18T17:21:39.000Z
lastmod: 2026-05-18T17:21:39.000Z
level: "1100"
difficulty: "🔴 Hard"
estimated_time: "6-8 hours"
primary_technology: docker
quest_type: main_quest
skill_focus: devops
learning_style: hands-on
quest_series: "Container Mastery"
author: IT-Journey Team
fmContentType: quest
layout: quest
draft: false
permalink: /quests/1100/docker-mastery/
# ... remaining recommended fields
---

Self-Check

Used the correct title/description length band for the content type
Quest: permalink matches quest_type
Quest: fmContentType: quest, layout: quest, draft: false
Numeric tags and levels quoted in YAML lists
categories and tags are lists, not strings
No invented fields outside the template / instructions

Install generate-frontmatter and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Generate Jekyll Frontmatter (validator-aligned) Return YAML frontmatter that passes CI on the first attempt. Constraints differ by content type — **do not apply post rules to quests**. ## Hard Constraints — Posts, Docs, READMEs Enforced by `.github/workflows/frontmatter-validation.yml`: | Field | Rule | |---|---| | `title` | **30–60** chars | | `description` | **120–160** chars | | `date` | ISO 8601 `YYYY-MM-DDTHH:MM:SS.sssZ` | | `categories` | YAML **list** | | `tags` | YAML **list**, ≥ 3 entries | | `author` | non-empty string | | `draft` | `false` unless caller specifies otherwise | Count `title` and `description` characters; state counts in a YAML comment. Fix and recount if out of bounds. **Optional brand keys (posts only):** `section_guide` — a slug from `_data/brand/sections/_registry.yml` (e.g. `devops`, `devops-news-muse`). Usually inferred from the post's folder, so include it only to override (e.g. a muse). `voice_profile` overrides the guide's profile; normally omit. Neither is CI-validated. See [`brand.instructions.md`](../instructions/brand.instructions.md). ## Hard Constraints — Quests (`pages/_quests/**/*.md`) Enforced by `test/quest-validator/quest_validator.py`. Read [`.github/instructions/quest.instructions.md`](../instructions/quest.instructions.md) and `.frontmatter/templates/quests.md` — **do not invent fields**. | Field | Rule | |---|---| | `title` | **10–100** chars (quest rule — not the 30–60 post rule) | | `description` | **150–300** chars (quest rule — not the 120–160 post rule) | | `level` | quoted 4-digit binary: `"1100"` | | `difficulty` | exact emoji+label: `"🟢 Easy"`, `"🟡 Medium"`, `"🔴 Hard"`, `"⚔️ Epic"` | | `estimated_time` | `"X-X hours"` or `"X-X minutes"` | | `primary_technology` | lowercase string | | `quest_type` | `main_quest` \| `side_quest` \| `bonus_quest` \| `epic_quest` | | `skill_focus` | `frontend` \| `backend` \| `devops` \| `security` \| `data-engineering` \| `fullstack` | | `learning_style` | `hands-on` \| `conceptual` \| `project-based` | | `quest_series` | non-empty string | | `fmContentType` | `quest` (playable quests) | | `layout` | `quest` (playable quests) | | `permalink` | must match `quest_type` — see § Permalink below | | `keywords` | object with `primary` and `secondary` lists | **Recommended:** `quest_line`, `quest_arc`, `prerequisites`, `quest_dependencies`, `rewards`, `validation_criteria`, `lastmod`. **Level READMEs** (`pages/_quests/XXXX/README.md`): use `layout: quest-collection`, `permalink: /quests/XXXX/`, quoted `level`. Do **not** set `fmContentType: quest`. ### Quest permalink by type | `quest_type` | `permalink` | |---|---| | `main_quest` | `/quests/XXXX/<slug>/` | | `side_quest` | `/quests/XXXX/side-quests/<slug>/` | | `bonus_quest` / `epic_quest` | `/quests/codex/<slug>/` | ### Quest dependency URLs Use full canonical paths in `quest_dependencies` — never bare slugs: ```yaml quest_dependencies: required_quests: - /quests/0000/terminal-fundamentals/ unlocks_quests: - /quests/0010/next-quest/ # planned quest ``` ### YAML quoting Quote 4-digit levels and numeric tags to avoid Jekyll `gsub` errors: ```yaml level: "1100" tags: ["1100", docker, main_quest] ``` ## Per-Type Summary | Type | Path | Extra rules | |---|---|---| | `post` | `pages/_posts/**` | Post title/description lengths; `learning_objectives` recommended | | `quest` | `pages/_quests/**` (not templates) | Quest title/description lengths; full quest field set above | | `doc` | `pages/_docs/**` | Post hard constraints; omit quest-only fields | | `readme` | `pages/**/README.md` | Post hard constraints for Jekyll-processed READMEs | | `note` | `pages/_notes/**` | Post hard constraints only | ## Output Format Return valid YAML between `---` fences with a comment showing character counts: ```yaml --- # title=48 chars, description=172 chars — quest bounds OK title: "Docker Mastery: Container Orchestration Fundamentals" description: "Learn container orchestration with Docker Compose: multi-service networking, volume persistence, environment configuration, and production-ready local dev stacks for teams." date: 2026-05-18T17:21:39.000Z lastmod: 2026-05-18T17:21:39.000Z level: "1100" difficulty: "🔴 Hard" estimated_time: "6-8 hours" primary_technology: docker quest_type: main_quest skill_focus: devops learning_style: hands-on quest_series: "Container Mastery" author: IT-Journey Team fmContentType: quest layout: quest draft: false permalink: /quests/1100/docker-mastery/ # ... remaining recommended fields --- ``` ## Self-Check - [ ] Used the correct title/description length band for the content type - [ ] Quest: `permalink` matches `quest_type` - [ ] Quest: `fmContentType: quest`, `layout: quest`, `draft: false` - [ ] Numeric tags and levels quoted in YAML lists - [ ] `categories` and `tags` are lists, not strings - [ ] No invented fields outside the template / instructions

{ "prompt": "# Generate Jekyll Frontmatter (validator-aligned)\n\nReturn YAML frontmatter that passes CI on the first attempt. Constraints differ by content type — **do not apply post rules to quests**.\n\n## Hard Constraints — Posts, Docs, READMEs\n\nEnforced by `.github/workflows/frontmatter-validation.yml`:\n\n| Field | Rule |\n|---|---|\n| `title` | **30–60** chars |\n| `description` | **120–160** chars |\n| `date` | ISO 8601 `YYYY-MM-DDTHH:MM:SS.sssZ` |\n| `categories` | YAML **list** |\n| `tags` | YAML **list**, ≥ 3 entries |\n| `author` | non-empty string |\n| `draft` | `false` unless caller specifies otherwise |\n\nCount `title` and `description` characters; state counts in a YAML comment. Fix and recount if out of bounds.\n\n**Optional brand keys (posts only):** `section_guide` — a slug from `_data/brand/sections/_registry.yml` (e.g. `devops`, `devops-news-muse`). Usually inferred from the post's folder, so include it only to override (e.g. a muse). `voice_profile` overrides the guide's profile; normally omit. Neither is CI-validated. See [`brand.instructions.md`](../instructions/brand.instructions.md).\n\n## Hard Constraints — Quests (`pages/_quests/**/*.md`)\n\nEnforced by `test/quest-validator/quest_validator.py`. Read [`.github/instructions/quest.instructions.md`](../instructions/quest.instructions.md) and `.frontmatter/templates/quests.md` — **do not invent fields**.\n\n| Field | Rule |\n|---|---|\n| `title` | **10–100** chars (quest rule — not the 30–60 post rule) |\n| `description` | **150–300** chars (quest rule — not the 120–160 post rule) |\n| `level` | quoted 4-digit binary: `\"1100\"` |\n| `difficulty` | exact emoji+label: `\"🟢 Easy\"`, `\"🟡 Medium\"`, `\"🔴 Hard\"`, `\"⚔️ Epic\"` |\n| `estimated_time` | `\"X-X hours\"` or `\"X-X minutes\"` |\n| `primary_technology` | lowercase string |\n| `quest_type` | `main_quest` \\| `side_quest` \\| `bonus_quest` \\| `epic_quest` |\n| `skill_focus` | `frontend` \\| `backend` \\| `devops` \\| `security` \\| `data-engineering` \\| `fullstack` |\n| `learning_style` | `hands-on` \\| `conceptual` \\| `project-based` |\n| `quest_series` | non-empty string |\n| `fmContentType` | `quest` (playable quests) |\n| `layout` | `quest` (playable quests) |\n| `permalink` | must match `quest_type` — see § Permalink below |\n| `keywords` | object with `primary` and `secondary` lists |\n\n**Recommended:** `quest_line`, `quest_arc`, `prerequisites`, `quest_dependencies`, `rewards`, `validation_criteria`, `lastmod`.\n\n**Level READMEs** (`pages/_quests/XXXX/README.md`): use `layout: quest-collection`, `permalink: /quests/XXXX/`, quoted `level`. Do **not** set `fmContentType: quest`.\n\n### Quest permalink by type\n\n| `quest_type` | `permalink` |\n|---|---|\n| `main_quest` | `/quests/XXXX/<slug>/` |\n| `side_quest` | `/quests/XXXX/side-quests/<slug>/` |\n| `bonus_quest` / `epic_quest` | `/quests/codex/<slug>/` |\n\n### Quest dependency URLs\n\nUse full canonical paths in `quest_dependencies` — never bare slugs:\n\n```yaml\nquest_dependencies:\n required_quests:\n - /quests/0000/terminal-fundamentals/\n unlocks_quests:\n - /quests/0010/next-quest/ # planned quest\n```\n\n### YAML quoting\n\nQuote 4-digit levels and numeric tags to avoid Jekyll `gsub` errors:\n\n```yaml\nlevel: \"1100\"\ntags: [\"1100\", docker, main_quest]\n```\n\n## Per-Type Summary\n\n| Type | Path | Extra rules |\n|---|---|---|\n| `post` | `pages/_posts/**` | Post title/description lengths; `learning_objectives` recommended |\n| `quest` | `pages/_quests/**` (not templates) | Quest title/description lengths; full quest field set above |\n| `doc` | `pages/_docs/**` | Post hard constraints; omit quest-only fields |\n| `readme` | `pages/**/README.md` | Post hard constraints for Jekyll-processed READMEs |\n| `note` | `pages/_notes/**` | Post hard constraints only |\n\n## Output Format\n\nReturn valid YAML between `---` fences with a comment showing character counts:\n\n```yaml\n---\n# title=48 chars, description=172 chars — quest bounds OK\ntitle: \"Docker Mastery: Container Orchestration Fundamentals\"\ndescription: \"Learn container orchestration with Docker Compose: multi-service networking, volume persistence, environment configuration, and production-ready local dev stacks for teams.\"\ndate: 2026-05-18T17:21:39.000Z\nlastmod: 2026-05-18T17:21:39.000Z\nlevel: \"1100\"\ndifficulty: \"🔴 Hard\"\nestimated_time: \"6-8 hours\"\nprimary_technology: docker\nquest_type: main_quest\nskill_focus: devops\nlearning_style: hands-on\nquest_series: \"Container Mastery\"\nauthor: IT-Journey Team\nfmContentType: quest\nlayout: quest\ndraft: false\npermalink: /quests/1100/docker-mastery/\n# ... remaining recommended fields\n---\n```\n\n## Self-Check\n\n- [ ] Used the correct title/description length band for the content type\n- [ ] Quest: `permalink` matches `quest_type`\n- [ ] Quest: `fmContentType: quest`, `layout: quest`, `draft: false`\n- [ ] Numeric tags and levels quoted in YAML lists\n- [ ] `categories` and `tags` are lists, not strings\n- [ ] No invented fields outside the template / instructions", "variables": [], "notes": "Generate Jekyll frontmatter for posts, quests, docs, and READMEs that passes IT-Journey CI validation Mode: agent.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/bamr87/it-journey", "path": ".github/prompts/generate-frontmatter.prompt.md", "ref": "7f3ba6be20055cee7a7dc2830283781bfdf2d6a2", "url": "https://github.com/bamr87/it-journey/blob/7f3ba6be20055cee7a7dc2830283781bfdf2d6a2/.github/prompts/generate-frontmatter.prompt.md", "key": "bamr87/it-journey/.github/prompts/generate-frontmatter.prompt.md" } } }

generate-frontmatter

About

Generate Jekyll Frontmatter (validator-aligned)

Hard Constraints — Posts, Docs, READMEs

Hard Constraints — Quests (`pages/_quests/**/*.md`)

Quest permalink by type

Quest dependency URLs

YAML quoting

Per-Type Summary

Output Format

Self-Check

Install generate-frontmatter and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

About

Generate Jekyll Frontmatter (validator-aligned)

Hard Constraints — Posts, Docs, READMEs

Hard Constraints — Quests (pages/_quests/**/*.md)

Quest permalink by type

Quest dependency URLs

YAML quoting

Per-Type Summary

Output Format

Self-Check

Install generate-frontmatter and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

Hard Constraints — Quests (`pages/_quests/**/*.md`)