Menu
Create and edit boring.generated-pane JSON specs from predefined safe component catalogs.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | generated-pane-authoring |
| description | Create and edit boring.generated-pane JSON specs from predefined safe component catalogs. |
Use when the user asks for a custom pane, dashboard, report, workflow UI, status view, or other workspace UI composed from predefined components.
Write JSON specs to panes/*.pane.json unless a profile/plugin says otherwise.
Required root shape:
{
"kind": "boring.generated-pane",
"version": 1,
"profile": "base",
"title": "Short title",
"root": "main",
"elements": {
"main": { "type": "Card", "props": { "title": "Overview" }, "children": [] }
}
}
Rules:
*.pane.json specs, validate with WorkspaceBridge op generated-pane.v1.validate using { "spec": <json> } when available. Profile-specific specs must use their owning plugin validate op.Drive one ready artifact through implementation, proof, review, and owner handoff.
Review the named UI scenario or emit one bounded improvement packet.
Teach a boring-ui child app how to enable Google signup with @hachej/boring-core. Use when the user asks for Google auth, Google OAuth, social signup, or how to turn on Google sign-in/sign-up in a child app.
Ask which Boring skill or workflow fits your situation. A router over the local Boring skills.
Run an extremely strict maintainability review for abstraction quality, giant files, spaghetti-condition growth, and code-judo simplification opportunities.
Route a request to the right Boring v2 workflow skill without doing the work.