Evidence-first Orchard Core theming skill for shapes, alternates, placement, Razor/Liquid templates, content model access, assets/resources, and recipes.
Use for theme adjustments, shape overrides, template discovery, content item/field access, placement.json rules, and recipe authoring in Orchard Core projects.
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars8
LicenseLicense.md
Default branchdev
Open issues0
Status
Archived
Skill metadata
Parsed from SKILL.md frontmatter.
Version1.0
LicenseMIT
More metadata
author
Lombiq Technologies
version
1.0
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md4,761 B
docsSUMMARY.md341 B
History
First seen on skills.sh
First recorded snapshot · 19 installs
SKILL.md
Orchard Core Theming
Use this skill for Orchard Core theming and content-definition/recipe work.
How to use
Path A (task match): scan the Tasks list; if the request matches, open references/TASK-MAP.md and go directly to the leaf files.
Path B (exploration): use the section cues to pick a reference section, open that section's INDEX.md, then choose the leaf file it points to.
Determine Razor vs Liquid early using the workflow in references/TASK-MAP.md. If it cannot be decided, fall back to Liquid and confirm with the user.
Open only the necessary leaf files; use a section INDEX.md only for orientation and discovery.
Prefer examples and ready-to-copy patterns.
Evidence rules
Prefer repo evidence over assumptions: active theme, base theme, placement.json, and existing templates.
Trace the shape model first when it is unclear; use references/TASK-MAP.md to find shape tracing guidance and ask the user if needed.
Confirm unknown part/field properties in ContentDefinition.json (or OrchardCore.db) and the relevant field references.
Ask for missing identifiers (content type, part name, field name, display type) instead of inventing them.
Do not invent recipe steps or feature IDs; use references/TASK-MAP.md to find the right recipe references.
Scripts
Use these scripts instead of hand-building extracts.
scripts/extract-content-definitions.py to extract content types/parts/fields from ContentDefinition.json or OrchardCore.db, with optional related-type expansion and Markdown/JSON output. See references/50-content-model/CONTENT-DEFINITIONS-EXTRACTOR.md.
scripts/extract-content-items.py to get content items from OrchardCore.db, filter by type/IDs/text, and optionally emit a recipe content step or a Markdown/JSON extract. See references/50-content-model/CONTENT-ITEMS-EXTRACTOR.md.
scripts/generate-orchard-ids.py to generate Orchard Core IDs that match the DefaultIdGenerator alphabet for stable ContentItemId values in recipes. See references/70-recipes/ID-GENERATION.md.
scripts/sync-skill.py to refresh the entire skill folder from the Lombiq/Orchard-Core-Agent-Skills repo (references, scripts, SKILL.md, assets). The running script is not overwritten until the next sync.