Skip to content
Skills Library
Design & UX · Building & coding

compose

/compose

Suggest and generate custom element compositions for a UI goal. Use when the user asks to "compose elements", "build a layout", "combine components", "create a page with", "what elements should I use for", or describes a UI they want to build using custom elements.

Repository
cem ↗
Licence
GPL-3.0
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Suggest and generate custom element compositions for a UI goal. Use when the user asks to "compose elements", "build a layout", "combine components", "create a page with", "what elements should I use for", or describes a UI they want to build using custom elements.

Triggers from the description

compose elementsbuild a layoutcombine componentscreate a page withwhat elements should I use for
Original author description

Suggest and generate custom element compositions for a UI goal. Use when the user asks to "compose elements", "build a layout", "combine components", "create a page with", "what elements should I use for", or describes a UI they want to build using custom elements.

How it works

  1. Workflow
  2. Guidelines
Original SKILL.md headings · 111 lines, 503 words
SKILL.md preview
---
name: compose
description: >
  Suggest and generate custom element compositions for a UI goal.
  Use when the user asks to "compose elements", "build a layout",
  "combine components", "create a page with", "what elements should I use for",
  or describes a UI they want to build using custom elements.
tools: Read, generate_html, validate_html
---

# Component Composition Advisor

Given a UI goal, recommend which custom elements to use together and generate composed HTML.

## Workflow

### Phase 1: Understand the Goal

Clarify (if not already provided):
1. What UI is the user trying to build? (e.g., "login form", "data table", "card grid")
2. Any constraints? (e.g., specific elements they must use, layout requirements)
3. What level of detail? (quick wireframe-level vs production-ready)

### Phase 2: Survey Available Elements

Read the complete element library:

```text
cem://elements
```

Read project-level guidelines for composition patterns:

```text
cem://guidelines
```

For each candidate element, read its full API to understand capabilities and slot expectations:

```text
cem://element/{tagName}
cem://element/{tagName}/slots
cem://element/{tagName}/attributes
```

### Phase 3: Select Elements

Choose elements based on:

#### Semantic Fit
- Does the element's purpose match the role it would play in the composition?
- Is the element designed for this kind of content?

#### Slot Compatibility
- Can the elements nest correctly via slots?
- Do parent element slots accept the kind of content the child elements produce?
- Are there slot content guidelines that constrain composition?

#### Attribute Harmony
- Do the elements share compatible attribute patterns?
- Can they be configured to work together without conflicts?
- Do variant/size attributes compose sensibly?

#### Event Flow
- Can parent elements respond to child element events?
- Is the event propagation path logical?

### Phase 4: Generate Composed HTML

For each element in the composition, call `generate_html` to produce valid markup, then combine them.

Present the composition as:

```markdown
## Composition: [UI Goal]

### Elements Used

| Element          | Role       | Why                                    |
|------------------|------------|----------------------------------------|
| `<prefix-card>`  | Container  | Provides visual grouping and elevation |
| `<prefix-input>` | Form field | Text input with built-in validation    |


### HTML

[Complete composed HTML with comments explaining structure]

### How It Works
- [Explain the composition: which elements are slotted where]
- [Note any attribute interactions between elements]
- [Describe the event flow for interactive compositions]

### Styling

[CSS showing how to style the composition, using CSS custom properties and parts from the composed elements]

### Alternatives Considered
- [Other element combinations that could work, and why this one is better]
```

### Phase 5: Validate

Call `validate_html` on the final composed HTML to verify:
- All elements are used correctly
- Slot content follows guidelines
- No attribute conflicts
- Accessibility patterns are maintained

Report any issues and fix them before presenting the final result.

## Guidelines

- **Prefer composition over customization**: Use multiple elements together rather than forcing one element to do everything
- **Respect slot guidelines**: If a slot says "text content only", don't put a complex element in it
- **Keep nesting shallow**: Deeply nested compositions are fragile and hard to style
- **Show the minimal composition first**: Start simple, then offer enhanced versions with more elements
- **Consider responsive behavior**: Note if the composition needs different structure at different viewport sizes
- **Document the "why"**: Explain why each element was chosen so the user can make substitutions

Versions

RepositoryScoreLicence
This page · bennypowers/cem100GPL-3.0
Adolanium/hermes-stave100MIT
meet-miyani/compose-skill100MIT
caasi/dong3100MIT
rcosteira79/android-skills100MIT
sharpdeveye/maestro100MIT
joselrnz/infragram-azure91MIT
saadshahd/moo.md85MIT

Database snapshot: 13.11.2026 · package version 0028c0967f80 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100gen-tests
    Generate test scaffolding for custom elements using cem serve's chromeless demo UI with Playwright or Puppeteer. Use when the user asks to "generate tests", "scaffold tests", "create test boilerplate", "write tests for element", "playwright tests", "puppeteer tests", or mentions…
  • 87ux-elements-catalog
    Use before any UI design, wireframe, UI kit or build of a website, landing pages or app. Produces a UX elements catalog: a sitemap, then for each page the user stories ("As a [role], I want to..."), needs chains ("In order to [see my options / understand that / decide], I…
  • 100web-components-custom-elements
    Use this skill when authoring framework-agnostic Custom Elements, Shadow DOM encapsulations, and HTML templates using the Web Components standard.
  • 100write-docs
    Generate documentation for custom elements based on their manifest data. Use when the user asks to "write docs", "generate documentation", "document this element", "create API docs", or mentions "usage examples" or "component documentation".
  • 95spectrum-wc
    Build UIs with Spectrum 2 Web Components (swc-* elements, @adobe/spectrum-wc). Use when developers are working with the @adobe/spectrum-wc package or swc-* custom elements. Includes component and pattern API references (properties, slots, events, CSS custom properties, CSS…
  • 100elements
    Use this skill by default for any UI-related work or with NVIDIA Elements (nve-*), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.