express-milo-block-patterns

A set of rules for developing and improving Express-Milo content blocks, reusable page sections that authors can edit. It focuses on layouts that remain understandable and compatible with Word Online.

In plain words
What is it for?
Use it when building or optimizing blocks, deciding how content should be arranged, and adapting block behavior for different section layouts.
Why use it?
It reduces confusing editing structures and fragile block behavior by keeping content layouts simple and using section metadata for special cases.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/adobecom/express-milo/express-milo-block-patterns
Clone the repo
git clone --depth 1 https://github.com/adobecom/express-milo

Made for: Cursor.

Per session 840 This file is loaded in full into every session.
When invoked 840 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00840 $0.00840
Opus 5 $0.00420 $0.00420
Sonnet 5 $0.00168 $0.00168
Haiku 4.5 $0.00084 $0.00084

Measured 2d ago against content hash 15b70c4aa2fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

express-milo-block-patterns 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 2d 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.

Origin

This is a copy

100% identical to express-milo-block-patterns — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/express-milo-block-patterns.mdc · 108 lines

How it starts

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

Express-Milo Block Patterns

APPLY: Block development and optimization

Block Design Principles

Following Helix Block design best practices:

1. Intuitive Authoring (REQUIRED)

  • Word compatibility: 100% Word Online compatible, avoid Desktop-only features
  • Visual structure: Authors should be able to "squint and see the final UI"
  • NO key/value pairs: Avoid recreating AEM dialogs in table structures
  • 3-column limit: Beyond 3 columns, flip axis (columns → rows)

2. Section Metadata Integration

// ✅ Use section metadata for edge cases instead of complex block options
// Example: accordion + three-up styling via section class
const section = el.closest('.section');
if (section.classList.contains('three-up')) {
  // Adjust block behavior for three-up layout
}

3. Resilient Block Structure

// ✅ Standard express-milo block pattern
export default async function init(el) {
  // 1. DIVIDE CONTENT: Required vs Optional parts
  const rows = [...el.querySelectorAll(':scope > div')];
  const title = el.querySelector('h1, h2, h3'); // REQUIRED: Start with title
  
  // 2. PROBE OUTWARD: Build from required content
  const detail = findContentAbove(title); // Optional: Detail above title
  const body = findContentBelow(title);   // Optional: Body below title  
  const actions = findLinkContainer(el);  // Optional: Action area
  
  // 3. DECORATE DOM: Add human-readable classes, avoid nth-child
  if (detail) detail.classList.add('detail');
  title.classList.add('headline');
  if (body) body.classList.add('body');
  if (actions) actions.classList.add('actions');

  // 4. PRESERVE CONTENT: Use append, avoid innerHTML
  const structure = createFinalStructure();
  safelyMoveContent(title, detail, body, actions, structure);
  el.append(structure);
}

Express-Milo Utilities

// Icons: Use deprecated version for compatibility
const logo = getIconElementDeprecated('adobe-express-logo');

// Dynamic cart links: Always async enhance
formatDynamicCartLink(cta);

// Branch tracking: Always await
await trackBranchParameters([link]);

Read the full file on GitHub · 108 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. 2d ago First seen · 108 lines · 840 tokens per session scan A 15b70c4aa2fb

Subscribe to this mod's changes

express-milo-block-patterns is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 840 tokens to every session, about $0.0042 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to express-milo-block-patterns, differing in 0 lines, and is treated as a copy.