/application

Build the administration app a package owes its data. Covers the rule (data elements ⇒ an app that maintains them), the four things every package exposes (what it is, key entries, a worked sample, the Tests area), the App NodeType + the app declaration (app + entryPoint) that puts its tile on every viewer's home, and how to verify the front door actually opens. Composes /plugin, /layout-area, /code and /navigate rather than repeating them.

• Instructions: # Application — ship the app that administers your data **A package that introduces data elements owes the app that maintains them.** Shipping `NodeType`s without a place to administer them leaves an operator with content they can see and cannot change — the AI package says it on its own store card, and it is the rule, not a slogan: > *An engine nobody can configure is not a feature.* This skill is the front-door half of [/plugin](/Store/Skill/plugin): that one builds the package, this one makes it **usable by someone who did not write it**. Read [/layout-area](/Skill/layout-area) for how to build the views, [/code](/Skill/code) for authoring the source, and [/navigate](/Skill/navigate) for how navigation resolves. Do not re-derive them. ## 🚨 When you owe an app You owe one the moment your package introduces **data a human is expected to change**: a NodeType with instances, a catalog, credentials, settings, a per-user preference. You do **not** owe one for a package that only contributes renderers, a control pack, or content that is authored in git and never edited in the mesh. The test is not "is there data" — it is *"if an operator installs this, is there anything they will need to change, and where would they go?"* If the honest answer is "read the repo", the app is missing. ## What every package exposes — the four Four things, in this order. The first three are what a visitor needs; the fourth is what keeps it true. 1. **What the package IS** — the `description` on the node (a one-line tagline) and the cover `body` on `PluginContent`. Say what it does and what it deliberately does NOT do; the AI card's *"What does NOT ship here"* section is why nobody looks for OpenAI inside it. 2. **The key entries** — the `entryPoint` on `PluginContent`, plus a `UiContribution` per place a human starts. **Deep-link to the area that does the work**, never to a bare package root: the six credential-bearing provider packs (`Anthropic`, `AppleIntelligence`, `…
• Auto mount: yes
• Launches sub thread: no