SkillsAdd

smithery/bnomei

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.

Installation

$ npx skills add smithery/bnomei --skill kirby-panel-and-blueprints
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/bnomei · top by installs.

npx skills add smithery/bnomei
kirby-upgrade-and-maintenance 0 kirby-security-and-auth 0 kirby-project-tour 0 kirby-plugin-development 0 kirby-performance-and-media 0 kirby-ide-support 0 kirby-i18n-workflows 0 kirby-headless-api 0 kirby-forms-and-frontend-actions 0 kirby-debugging-and-tracing 0

Browse all from smithery/bnomei

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,010 B
  • docs SUMMARY.md 222 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

  1. 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:kirbyblueprintsindex - kirby:kirbyblueprintread

  1. Use Panel reference resources for field/section choices:

- kirby://fields - kirby://sections

  1. Check plugin surface when custom Panel UI is needed:

- kirby:kirbypluginsindex - kirby://extensions

  1. Search the KB with kirby:kirby_search (examples: "blueprints reuse extends", "programmable blueprints", "custom panel field", "custom panel section", "panel branding").
  2. Implement minimal, convention-aligned YAML/PHP; prefer extends and shared sections over duplication.
  3. Validate by re-reading the blueprint (kirby:kirbyblueprintread) and verifying frontend output with kirby:kirbyrenderpage when relevant.