Build MATLAB apps from requirements to working code. Asks discovery questions (or skips them when the path is known), recommends UIFigure or UIHTML architecture, identifies layout archetype (Dashboard, Explorer, Tabbed, Wizard, Canvas), produces an implementation plan, and executes the build. For UIFigure apps, optionally serializes as App Designer (.mlapp or plain-text .m + .xml).
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/17/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill48%
With skill91%
Checks it passed that the model alone missed
The response names the plan document SignalLab-plan.md.
The response identifies the primary layout archetype as Explorer.
The response designates .mlapp as the fallback serialization format.
and 10 more in the full report
11 fixed10 passed either way1 still failing1 broke
Pass-rate lift
+43 pp
Tokens
+194%
Agent turns
0%
Response time
-44%
Model gemini-3.6-flashMeasured 8/17/2026v221 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Our team wants to save a UIFigure app using App Designer plain-text format (.m and .xml files). Which MATLAB release version is required at minimum to support this plain-text format?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies MATLAB release R2026b as the minimum requirement.
Missed
Passed
case-16 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md403 lines5 filesincludes scripts
MATLAB Build App
Determine the best architecture for a MATLAB application, produce an implementation plan grounded in internal references, and execute the build. For UIFigure apps, optionally serialize into an App Designer format.
When to Use This Skill
Use this skill when:
User wants to build a MATLAB app, GUI, or interactive tool
User asks "how should I build this app?" or "which approach should I use?"
User describes an application — with or without specifying an implementation path
User describes spatial layout needs: dashboard, control panel, sidebar, tabs, wizard, stepper, canvas, workspace
User has already chosen a path (e.g., "build me a uihtml app") — handle directly
When Not to Use
The request is purely about MATLAB computation with no UI component
The user is asking about an existing app they want to modify → read references/editing-guide.md
The user wants to convert between App Designer formats (e.g., .mlapp to plain-text or vice versa) → tell them to use File > Save As in App Designer. Do NOT attempt the conversion programmatically.
Critical Rules
MUST ask discovery questions before recommending a path — unless the user already specified one
MUST confirm the path choice with the user before producing the implementation plan
MUST produce an implementation plan grounded in internal references before writing any code
MUST write the plan to a file (<app-name>-plan.md) in the working directory
NEVER recommend a path without understanding the user's constraints (unless path was pre-specified)
NEVER apply dark mode, custom colors, or visual themes unless the user explicitly requests them
ALWAYS present the recommendation as guidance, not a mandate — the user decides
MUST choose archetype based on the user's primary task, not aesthetics
NEVER treat two archetypes as equals within one app — one is always the primary container
UIFigure app: MUST use uigridlayout for all structural layout — never Position-based sizing
UIHTML/web app: MUST use CSS Grid or Flexbox for chrome — no absolute positioning for structural panels
The chrome (header, sidebar, tabs, step indicator) MUST remain spatially stable
App Designer serialization: MUST read references/app-designer/agent-guide-shared.md (covers ownership models, editing discipline, property rules, quoting) plus the format-specific guide (agent-guide-mlapp.md or agent-guide-plaintext.md) before building. Those docs are the single source of truth; do not attempt to edit app files without reading them first.
Build, modify, and diagram SimBiology models — API reference, helper functions, and layout patterns. Use when constructing or editing models programmatically or visually.