---
name: rednote-carousel
description: Turn a source-backed narrative into an editable Xiaohongshu (小红书) carousel with deterministic Chinese typography, safe-area and overflow checks, caption, contact sheet, and export manifest. Use for RedNote social cards. Do not use image models to render Chinese text.
license: Apache-2.0
metadata:
  compatibility: Codex, Kimi Code, and Grok Build; requires HTML or vector rendering and screenshot export; image generation is optional for non-text visuals.
  author: Lei Huang
  version: "0.1.0"
  status: experimental
---

# RedNote Carousel

Content structure comes first. Chinese typography must remain deterministic and editable.

## Inputs

Require a reader promise, audience, claim ledger or approved content, desired card count or range, brand context, and publication constraints. If facts are not sourced, invoke `research-claims` before visual production.

## Visual-target gate

Use an existing brand or selected direction when available. For greenfield work without a target, generate exactly three image-based directions that differ in composition, typography, density, color, and illustration behavior. Wait for selection before producing the final cards.

## Workflow

1. Create a narrative spine: cover promise, tension, claims, proof, practical steps, counterpoint, and close.
2. Assign one job and one primary claim to each card. Preserve claim identifiers in card metadata.
3. Write concise Chinese copy. Do not distort certainty or remove essential caveats for engagement.
4. Define editable content, layout, and style tokens separately.
5. Render all Chinese text with deterministic HTML/CSS, SVG, Canvas text, or another typography engine with known fonts.
6. Use generative imagery only for non-text illustration, texture, or photography. Never ask an image model to spell Chinese copy.
7. Export individual PNGs, an overview contact sheet, caption copy, source ledger, and machine-readable manifest.
8. Test every card for overflow, line breaks, safe area, contrast, font fallback, cross-card consistency, factual traceability, and export dimensions.

## Deliverables

```text
carousel/
  content.yaml
  tokens.json
  cards.html or cards.svg
  exports/01-cover.png ...
  contact-sheet.png
  caption.md
  claims.csv
  manifest.json
```

The manifest records card number, title, primary claim IDs, dimensions, file hash, fonts, render engine and version, and export timestamp.

## Card checks

- The cover makes one defensible promise, not a vague topic label.
- Body text remains readable at phone scale.
- No important text enters platform or crop safe areas.
- Long words, punctuation, mixed Latin text, and numbers wrap intentionally.
- Color is not the only carrier of meaning.
- Font fallback does not change line breaks silently.
- Visuals do not add unsupported factual detail.
- Caption citations map to the same claim ledger as the cards.

## Evidence packet

Return the editable source, exports, contact sheet, caption, claims, manifest, render and validation commands, failures corrected, and remaining platform-specific uncertainty.