How do I install the Kirby Panel And Blueprints skill?

Run npx skillmds@latest add tomevault-io/kirby-panel-and-blueprints in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kirby Panel And Blueprints safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kirby Panel And Blueprints?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kirby Panel And Blueprints free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kirby Panel And Blueprints?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kirby Panel And Blueprints by tomevault-io

Name: Kirby Panel And Blueprints
Author: tomevault-io

Kirby Panel And Blueprints

Designs Kirby blueprints and Panel UI, including blueprint reuse/extends, programmable blueprints, and custom Panel fields/sections/areas. Use when changing the Panel experience or schema. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Kirby Panel and Blueprints

KB entry points

kirby://kb/scenarios/06-blueprints-reuse-extends
kirby://kb/scenarios/19-programmable-blueprints
kirby://kb/scenarios/53-panel-first-custom-field
kirby://kb/scenarios/54-panel-first-custom-section
kirby://kb/panel/reference-fields
kirby://kb/panel/panel-bundling-decisions

Required inputs

Content model and required fields.
Panel UX (tabs/sections/layout) and validation rules.
Whether to extend an existing blueprint.

Minimal blueprint skeleton

title: Example
status:
  draft: true
  listed: true
fields:
  title:
    type: text
  text:
    type: textarea

Extends example

extends: pages/default

Common pitfalls

Duplicating fields instead of using extends.
Implementing Panel UI logic in templates instead of blueprints or plugins.

Workflow

Clarify the content model, required fields, and Panel UX expectations.
Call kirby:kirby_init and read kirby://roots.
Inspect existing blueprints and patterns:
- kirby:kirby_blueprints_index
- kirby:kirby_blueprint_read
Use Panel reference resources for field/section choices:
- kirby://fields
- kirby://sections
Check plugin surface when custom Panel UI is needed:
- kirby:kirby_plugins_index
- kirby://extensions
Search the KB with kirby:kirby_search (examples: "blueprints reuse extends", "programmable blueprints", "custom panel field", "custom panel section", "panel branding").
Implement minimal, convention-aligned YAML/PHP; prefer extends and shared sections over duplication.
Validate by re-reading the blueprint (kirby:kirby_blueprint_read) and verifying frontend output with kirby:kirby_render_page when relevant.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: kirby-panel-and-blueprintsdescription: Designs Kirby blueprints and Panel UI, including blueprint reuse/extends, programmable blueprints, and custom Panel fields/sections/areas. Use when changing the Panel experience or schema. Use when this capability is needed.---# Kirby Panel and Blueprints## KB entry points- `kirby://kb/scenarios/06-blueprints-reuse-extends`- `kirby://kb/scenarios/19-programmable-blueprints`- `kirby://kb/scenarios/53-panel-first-custom-field`- `kirby://kb/scenarios/54-panel-first-custom-section`- `kirby://kb/panel/reference-fields`- `kirby://kb/panel/panel-bundling-decisions`## Required inputs- Content model and required fields.- Panel UX (tabs/sections/layout) and validation rules.- Whether to extend an existing blueprint.## Minimal blueprint skeleton```yamltitle: Examplestatus: draft: true listed: truefields: title: type: text text: type: textarea```## Extends example```yamlextends: pages/default```## Common pitfalls- Duplicating fields instead of using `extends`.- Implementing Panel UI logic in templates instead of blueprints or plugins.## Workflow1. Clarify the content model, required fields, and Panel UX expectations.2. Call `kirby:kirby_init` and read `kirby://roots`.3. Inspect existing blueprints and patterns: - `kirby:kirby_blueprints_index` - `kirby:kirby_blueprint_read`4. Use Panel reference resources for field/section choices: - `kirby://fields` - `kirby://sections`5. Check plugin surface when custom Panel UI is needed: - `kirby:kirby_plugins_index` - `kirby://extensions`6. Search the KB with `kirby:kirby_search` (examples: "blueprints reuse extends", "programmable blueprints", "custom panel field", "custom panel section", "panel branding").7. Implement minimal, convention-aligned YAML/PHP; prefer `extends` and shared sections over duplication.8. Validate by re-reading the blueprint (`kirby:kirby_blueprint_read`) and verifying frontend output with `kirby:kirby_render_page` when relevant.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/bnomei) — claim your Tome and manage your conversions.

Frequently asked questions