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.