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.
pinned to #3474420updated 2 weeks ago
Ask your AI client: “install skills/kirby-panel-and-blueprints”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/kirby-panel-and-blueprintsmetahub onboarded this repo on the author's behalf.
If you own github.com/bnomei/kirby-mcp on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
56
Last commit
2 weeks ago
Latest release
published
- #agent-tools
- #agentic-workflow
- #claude-code
- #cli
- #codex-cli
- #commands
- #developer-tools
- #google-gemini
- #kirby
- #kirby-cms
- #knowledge-base
- #mcp-server
- #model-context-protocol
- #php8
- #prompts
- #resources
- #tools
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.3474420· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at skills/kirby-panel-and-blueprints/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
195 words · 1,765 chars · 6 sections · 2 code blocks
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent3474420warn2 weeks ago
Contents
KB entry points
kirby://kb/scenarios/06-blueprints-reuse-extendskirby://kb/scenarios/19-programmable-blueprintskirby://kb/scenarios/53-panel-first-custom-fieldkirby://kb/scenarios/54-panel-first-custom-sectionkirby://kb/panel/reference-fieldskirby://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_initand readkirby://roots. - Inspect existing blueprints and patterns:
kirby:kirby_blueprints_indexkirby:kirby_blueprint_read
- Use Panel reference resources for field/section choices:
kirby://fieldskirby://sections
- Check plugin surface when custom Panel UI is needed:
kirby:kirby_plugins_indexkirby://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
extendsand shared sections over duplication. - Validate by re-reading the blueprint (
kirby:kirby_blueprint_read) and verifying frontend output withkirby:kirby_render_pagewhen relevant.
Reviews
No reviews yet. Be the first.
Related
orchestration-patterns
>
migration-patterns
>
deployment-sop
>
mh install skills/kirby-panel-and-blueprints