outsystems-design-to-app

outsystems-design-to-app is a skill for Claude Code, Codex from OutSystems/outsystems-mcp. It costs 222 tokens per session (11,885 once invoked), scanned A, original, MIT.

A guide for turning a design source—such as a Figma file, screenshot, HTML mockup, or front-end code—into an OutSystems app. It translates each screen into OutSystems UI building blocks and directs the OutSystems Mentor tool through the build.

In plain words
What is it for?
Use it to extract screen structure, write a screen-by-screen specification, and create the app through OutSystems Mentor with review points before changes are made.
Why use it?
It helps bridge the gap between a visual design and an application built with OutSystems, while keeping the implementation tied to real OutSystems components. This feature is in beta, so its behavior may change or be discontinued.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: positional $N argument; mentions Claude Code.

Part of the outsystems plugin — 6 skills, 1 command, 1 agent, 1 hook, 1 MCP server shipped together

Good fit Use it to extract screen structure, write a screen-by-screen specification, and create the app through OutSystems Mentor with review points before changes are made.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outsystems/outsystems-mcp/outsystems-design-to-app
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add OutSystems/outsystems-mcp --skill outsystems-design-to-app
Clone the repo
git clone --depth 1 https://github.com/OutSystems/outsystems-mcp

Made for: Claude Code, Codex.

Or install outsystems, the plugin that ships this one along with the rest of its 6 skills, 1 command, 1 agent, 1 hook, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for outsystems-design-to-app

README.md
[![agentmods](https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-design-to-app/github.svg)](https://agentmods.dev/skills/outsystems/outsystems-mcp/outsystems-design-to-app)
Your own site
<a href="https://agentmods.dev/skills/outsystems/outsystems-mcp/outsystems-design-to-app"><img src="https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-design-to-app/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for outsystems-design-to-app

Your own site · 80×15
<a href="https://agentmods.dev/skills/outsystems/outsystems-mcp/outsystems-design-to-app"><img src="https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-design-to-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 222 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 11,885 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00222 $0.11885
Opus 5.5 $0.00089 $0.04754
Sonnet 5.5 $0.00044 $0.02377
Haiku 4.5 $0.00022 $0.01188

Measured 4d ago against content hash f8308a239178, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

outsystems-design-to-app scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/skills/outsystems-design-to-app/SKILL.md · 427 lines

How it starts

The opening of the file, as written. The whole thing — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Beta Feature. This skill is a Beta Feature: a non-final OutSystems capability provided to collect customer feedback. It can change significantly, including through breaking changes, or be discontinued. The first time you use this skill in a conversation, tell the user it's a Beta Feature and share https://www.outsystems.com/legal/beta-features-agreement.

OutSystems Design-to-App

Turn a design source (Figma, screenshot, HTML mockup, or front-end code) into a working OutSystems app via the OutSystems MCP / Mentor. The skill bridges three things a vanilla LLM does poorly on its own: design extraction, OutSystems UI domain knowledge, and Mentor invocation discipline. It authors an anatomy-first spec (a per-screen widget-tree of real blocks with inline styles), gates every visual element through a real OutSystems UI block, and drives Mentor in tight batches.

Load the main outsystems skill before Step 1: session, polling and publish rules come from it (read the live tool catalog, one Mentor session per task, cursor polling and waiting from a fresh context where your harness offers one, confirm before every tenant write). This skill adds only what is specific to building from a design; where the two seem to differ, the main skill wins.

Prerequisites

  • The outsystems MCP server connected and authenticated, per the main outsystems skill.
  • Mentor enabled on the tenant (this skill drives Mentor).
  • Figma MCP server connected if the design source is a Figma URL (its design-context, variables and screenshot tools, whatever your toolset calls them). For HTML / image / code sources, the Figma MCP is not required.
  • A target app. Either an existing app the user names, or a new Web app the skill creates (after confirmation) from the standard template; see Steps 1 and 5.

When NOT to use

  • Just running Mentor with a free-form prompt (no design source, no spec discipline needed): drive Mentor directly with your prompt.
  • Building from a written brief or spec with no design or code: this skill does not apply; build it with Mentor directly, following the main outsystems skill.
  • Adding non-visual features to an existing app (logic, data, integrations, no design source): drive Mentor directly with your prompt. Adding a screen from a design to an existing app is in scope: see "Adding a screen to an existing app" under Step 1.
  • Auditing / reviewing an existing app: drive Mentor directly with your prompt.

Read the full file on GitHub · 427 lines

Files

What ships with it

45 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago Changed · +9 lines f8308a239178
  2. 6d ago First seen · 418 lines · 222 tokens per session scan A 1443670f1a79

Subscribe to this mod's changes

outsystems-design-to-app is a skill published in the GitHub repository OutSystems/outsystems-mcp (40 stars, last pushed today), licensed MIT. It adds 222 tokens to every session and 11,885 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.

Related

Other skills, from other repositories

sage-review

Deep, platform-neutral code review for PRs and CRs in ONE thorough single pass — design reasoning (Problem Worth Solving & Solution Fit) as one dimension alongside the 9 code-level dimensions, with chain-of-consequences, self-critique, and draft-only comments. The single app-owned source of truth.

kirodotdev/KiroCrew · 68 tokens

design-critique

Run a heuristic evaluation of a UI design (image, HTML, Figma, URL, or flow) the way an experienced designer would. Evaluates 4 categories (Visual & hierarchy, Usability & interaction, Accessibility, Content) using recognized frameworks, NN/g 0-4 severity, and evaluability-aware prioritization that never judges what…

kirodotdev/KiroCrew · 131 tokens

dashboard-template

Kiro Crew repo only: load this when a task will author or change a dashboard page. A page never ships alone: the same PR carries its TypedDict contract, its provider, and a parity test that the two agree. Scaffold all four from one field list; read numbers from an existing fold, never type them.

kirodotdev/KiroCrew · 68 tokens

theme-pack-authoring

Build, validate, and install Kiro Crew theme packs -- pack anatomy, the 56-variable palette, role-tagged fonts, the overrides.css allowlist (what installs vs what actually renders), and the install-verify cycle. Use when the user wants to create or edit a theme pack.

kirodotdev/KiroCrew · 64 tokens

image-authoring

Author images and diagrams as code — SVG, Pillow, Excalidraw, mermaid. Load when asked to draw, illustrate, or make an image, icon, logo, poster, or diagram.

kirodotdev/KiroCrew · 45 tokens

frontend-design-workflow

Workflow for frontend features and visual/product design changes — present mockup options before code, build on the project's design system, capture the right evidence (screenshots vs video), run a new-user usability review. Use when building or changing UI, styling, layout or animation.

kirodotdev/KiroCrew · 59 tokens