Skip to content
skillxone

nexu-io/open-design / plugins/_official/examples/codex-interactive-capability-map

codex-interactive-capability-map

Verified

Turn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.

Codex Interactive Capability Map

Transform a long article, social thread, memo, product essay, or launch narrative into a visual explainer that people can scan and click through.

Use When

  • The input is mostly text and the user wants a clearer mental model.
  • The content contains repeated concepts, a process, a framework, capabilities, or operating principles.
  • The desired output is a polished web artifact, not a static summary.

Workflow

  1. Read the source material and extract 6-10 core concepts.
  2. Name the overall model in plain language. Prefer a short noun phrase such as "Operating Model", "Capability Map", or "Workflow Loop".
  3. Build three linked views:
    • A hero that frames the source and the promise.
    • A workflow loop that shows the main sequence or system.
    • A use-case matrix that combines concepts into practical scenarios.
  4. Add a right-side detail panel. Clicking any nav item, loop node, matrix card, or maturity level must update the panel.
  5. Make the clicked element and the detail panel visibly correspond through shared color, motion, icon/mark shape, or gradient.
  6. Keep copy short. The artifact should reduce reading effort, not recreate the article.

Visual Direction

  • Use a Codex-inspired refined product style with soft liquid motion, glassy surfaces, and crisp functional controls.
  • Make the first viewport feel like a finished product surface, not a wireframe.
  • Favor diagrams, loops, matrices, rails, cards, and progressive disclosure over paragraphs.
  • Use meaningful hover and active states. A click should feel consequential.
  • Avoid external image dependencies unless the user explicitly provides assets.

Interaction Requirements

  • All clickable elements must update content or scroll to a meaningful section.
  • The active state must be visually obvious.
  • The detail panel should animate on each change.
  • Long labels must wrap cleanly and never be clipped.
  • The layout must work at 1280px wide and collapse cleanly below 900px.

Output Contract

Emit one single-file HTML artifact:

<artifact identifier="codex-interactive-capability-map" type="text/html" title="Codex Interactive Capability Map">
<!doctype html>
<html>...</html>
</artifact>

Include all CSS and JavaScript inline. Do not use lorem ipsum. Do not leave placeholder cards. If the source does not include enough concrete details, infer a small, clearly labeled conceptual model from the source instead of inventing unrelated content.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall