cratis-screenplay-ui-composition

cratis-screenplay-ui-composition is a skill for Claude Code, Codex from Cratis/AI. It costs 178 tokens per session (4,062 once invoked), scanned A, original, MIT.

A guide to declaring user-interface structure in a Cratis Screenplay .play model. It covers application layouts, reusable templates, forms linked to commands, navigation, themes, and localized text.

In plain words
What is it for?
Use it to describe an application shell, screens, dialogs, command forms, navigation entries, visual themes, and translated interface strings.
Why use it?
It keeps the intended screens and their behavior in the same model as the rest of the system, including responsive layout and language-specific text.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to describe an application shell, screens, dialogs, command forms, navigation entries, visual themes, and translated interface strings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cratis/ai/cratis-screenplay-ui-composition
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 Cratis/AI --skill cratis-screenplay-ui-composition
Clone the repo
git clone --depth 1 https://github.com/Cratis/AI

Made for: Claude Code, Codex.

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 cratis-screenplay-ui-composition

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/ai/cratis-screenplay-ui-composition/github.svg)](https://agentmods.dev/skills/cratis/ai/cratis-screenplay-ui-composition)
Your own site
<a href="https://agentmods.dev/skills/cratis/ai/cratis-screenplay-ui-composition"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-screenplay-ui-composition/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 cratis-screenplay-ui-composition

Your own site · 80×15
<a href="https://agentmods.dev/skills/cratis/ai/cratis-screenplay-ui-composition"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-screenplay-ui-composition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 178 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,062 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.00178 $0.04062
Opus 5.5 $0.00071 $0.01625
Sonnet 5.5 $0.00036 $0.00812
Haiku 4.5 $0.00018 $0.00406

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

Security

Grade A, and why

cratis-screenplay-ui-composition 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 5d 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.

.cratis/ai/skills/cratis-screenplay-ui-composition/SKILL.md · 317 lines

How it starts

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

UI composition in Screenplay

Read preferred syntax when writing or reviewing .play.

Event Modeling's wireframe step is a first-class part of the language. The shell, the reusable shapes inside it, the forms bound to commands, and the navigation entries other modules contribute are all declared in the .play model.

⚠️ file <Identifier> is read as a property named file, not a directive — the type-reference shape wins the tie. file Invoices/Register.cs is a directive; file Attachment is a property. In a trigger body the directive always wins, so a trigger value named file is written @file.

Locate the model

Look first for the project's existing .play files: their folder is the model. For a new model, check Source/ or src/, else use Screenplay/ at the repository root. Never put a model under .cratis/ or hand-copy it between repositories. cratis ai install manages .cratis/ai/, never model files. Keep explanatory Markdown in project documentation; .play is the single flow model.

Product sources

Tool versions: toolchain SKILL.md. UI statements come from Screenplay screens.md, contributions.md, navigation.md, sample-data.md, forms.md, templates.md, ui-profile.md, fixtures/screen-release-ui.play, layout-arrangement.md, interactions.md, theme.md, internationalization.md and file-references.md under Documentation/screenplay/. Scene runtime sources: scaffold Scene tag, Source/JavaScript/**. This guidance does not verify UI rendering.

Every construct on this page is deferred from the executable model with information PLAY0269: it never blocks binding, and it is not evidence that a target renders it.

The screens-release surface adds component data-context bindings, exposed template configuration, package/icon catalogs, manual form columns, hierarchical outlets, routes, toolbars and dialog destinations, each with a separate support level (authoring accepted, executable admitted, runtime implemented). Discover the installed shape through MCP syntax-schema; details: references/screen-composition-contract.md.

Read the full file on GitHub · 317 lines

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. 5d ago Changed · -12 lines · +40 tokens per session 0a51ab043faf
  2. 6d ago Changed · +2 lines de13ca990d5f
  3. 7d ago Changed · -98 lines ff4f7e9cceaa
  4. 9d ago Changed · -2 lines 2af3d82498ac
  5. 10d ago Changed 9e402ab41a6d
  6. 11d ago Changed · +1 lines 2a09df7697c5
  7. 12d ago Changed · +15 lines · +2 tokens per session 8b2caec50fa2
  8. 15d ago Changed · +52 lines 387a756755fa
  9. 17d ago Changed · +7 lines 1ab27496b753
  10. 26d ago First seen · 352 lines · 136 tokens per session scan A 928e4381af91

Subscribe to this mod's changes

cratis-screenplay-ui-composition is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 178 tokens to every session and 4,062 once invoked, about $0.0007 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-09-19.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens