nocobase-prototype-repro
Goal
Turn a prototype + a one-line ask into a faithful NocoBase app. This is a meta / orchestration skill — it sequences nocobase-data-modeling + nocobase-ui-builder + nocobase-app-discipline and adds the two things that decide fidelity: a region → native-block mapping and a visual convergence loop. It does not re-teach the CLI; it routes to the sibling skills for mechanics and owns only the reproduction-specific judgment.
When to use / Non-Goals
Hard gate (check before selecting this skill): there must be an actual prototype in hand — an HTML file, a screenshot, or a link to one — that you are matching against. No prototype, no fidelity gap → this is not the skill; a plain "build me an app / a page" request belongs to nocobase-app-discipline (whole system) or nocobase-ui-builder (single page/edit). Do not let this skill shadow the normal build flow.
Use when:
- The user gives a prototype (HTML file, link, screenshot, or a
public/prototypes/...URL to curl) and wants it reproduced in NocoBase. - A page already exists but the user says it's monotone / ugly / doesn't match the prototype / a region should be a list/card/kanban instead of a table — i.e. there is a visual target and a fidelity gap.
Non-Goals — hand off, do not do here:
- Pure data modeling (collections/fields/relations with no visual target) →
nocobase-data-modeling. - Workflows / automations →
nocobase-workflow-manage. ACL / permissions →nocobase-acl-manage. Plugin work →nocobase-plugin-development. - A localized UI edit with no visual target and no fidelity gap (move one field, rename an action, tweak a reaction) →
nocobase-ui-builderdirectly. This skill is only worth its overhead when you are matching a prototype's look/behavior; for a mechanical surface edit, skip straight to ui-builder. - Whole-page authoring from a business sentence with no prototype → author a quick prototype first (prototype-authoring.md), then this skill; or if the user just wants a generic page, that's
nocobase-ui-builder'sapplyBlueprint.