nocobase-ui-builder

Automate NocoBase Modern Page (v2) UI authoring with blueprint creation and local previews.

45|10|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/nocobase/skills --skill nocobase-ui-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nocobase-ui-builder
Source: https://github.com/nocobase/skills/tree/main/skills/nocobase-ui-builder
Command: npx skills add https://github.com/nocobase/skills --skill nocobase-ui-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This UI-building skill provides a centralized, reusable workflow for authoring Modern Page (v2) interfaces in NocoBase apps, enabling rapid page creation, block configuration, and localized edits without resorting to DSL files.

Core Features & Use Cases

  • Canonical entry for UI authoring via nb api flow-surfaces; supports whole-page blueprint creation/replacement and localized edits.
  • Boundary-aware routing that hands off out-of-scope tasks to other skills and supports template/reference workflows.
  • Local preflight, prepare-write, and readback verification to ensure safe, persisted writes.

Quick Start

Draft a full page blueprint, preview ASCII wireframe, and then apply the prepared blueprint via nb api flow-surfaces apply-blueprint.

Frequently Asked Questions about nocobase-ui-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Modern Page (v2) interfaces in NocoBase without writing DSL files?

You can author Modern Page (v2) interfaces in NocoBase by drafting a full page blueprint, previewing an ASCII wireframe, and applying the prepared blueprint via the nb api flow-surfaces apply-blueprint endpoint without needing DSL files.

Can I make localized edits to an existing NocoBase page using a blueprint?

Yes, localized edits are supported through boundary-aware routing. This mechanism handles targeted page modifications and automatically routes out-of-scope tasks to other skills, supporting both full-page replacement and granular edits.

How does NocoBase validate UI payloads before persisting page blueprints to the remote server?

NocoBase validates UI payloads using a local prepare-write gate. This preflight mechanism checks the blueprint data and returns a normalized write body to ensure safe, persisted remote writes via flow-surfaces.

What is the best way to handle out-of-scope UI components when authoring NocoBase pages?

The best way to handle out-of-scope components is through boundary-aware routing, which automatically hands off unsupported tasks to other skills and manages template or reference workflows for those pieces.

Does the NocoBase UI authoring workflow support previewing page blueprints before applying them?

Yes, the workflow supports previewing page blueprints. You can draft a full page blueprint and preview an ASCII wireframe locally before applying the prepared blueprint to the NocoBase application.

Why do I need a normalized write body for NocoBase remote writes?

A normalized write body is required to ensure safe, persisted remote writes. It standardizes the validated payload output from the local prepare-write gate before final submission to the flow-surfaces endpoint.