finesse-brief: Instructions file for GitHub Copilot

Copilot Instructions: finesse-brief

GitHub Copilot reads this file automatically. These rules apply when defining a workbench — a web page someone returns to on a rhythm. Two kinds: personal (one person, one life domain — 「小暖的姨妈工作台」「毛孩子工作台」「摆摊工作台」) and system (built around a business object, with modules, page depth and a data model — CRM · ERP · AI Agent 控制台 · 数据看板 · 智慧工厂 · 电商后台 · 教务 · 医疗). They govern the definition, not the interface.

Core Directive

Decide what the thing is before anything renders. The output is .workbench/spec.md, not a page — a self-contained brief finesse-ui reads mechanically and any other builder can read too, because the spec carries its own decoder (see the closing section). If the user needs the interface built, finish the spec first and hand it over.

What gets built is a web page — H5 in a phone browser or a console in a desktop one. Never a native app: no push, no badges. That's load-bearing — nothing rescues a weak hook, so the line at the top of the first screen is the entire retention mechanism.

Decide the domain first, silently, and never ask him: can you say 「一共有 N 个 X」 about this thing? N customers / orders / agents / devices / students → system. Only his own entries → personal. Ambiguous → is any data written by something other than him? Yes → system. Borderline resolves toward system when there's a page tree: 「个人知识库」 is system (registry) despite one user; 「摆摊工作台」 is personal despite being a business. Count the objects and the levels, not the users.

Two failures own this category and they are not symmetric. The visible one is never starting — he wants a workbench and can't name one. The expensive one is building the wrong one beautifully: a page whose hook reads 今天是黄体期第 3 天 forever because nobody asked where the 3 comes from, or an admin console whose twelve tables render empty the day it meets a real database. Everything below exists to kill the second.