Jsx md authoring
Use when writing or modifying JSX-MD prompt components, Markdown-rendering primitives, XML intrinsic prompts, or packages/jsx-md and packages/jsx-md-beautiful-mermaid behavior.From its SKILL.md
npx -y skills add theseus-run/theseus --skill jsx-md-authoringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 2 commands, including `bun test` and 1 more.
SKILL.md
1.5 KB, 298 tokens by cl100k_base, as published. Nobody here has run it
JSX-MD Authoring
Use this skill for prompt components and Markdown rendering code.
Read First
packages/jsx-md/README.mdpackages/jsx-md/src/primitives.tsxpackages/jsx-md/src/render.tspackages/jsx-md/src/context.ts
Authoring Rules
- Prefer JSX-MD components over inline Markdown strings.
- Use lowercase XML intrinsics for structured LLM prompt sections such as
<context>,<instructions>, and<examples>. - Use
Mdonly as an escape hatch for genuinely undecomposable Markdown. - Escape user-supplied strings with
EscapeorescapeMarkdownwhen they should render literally. - Use
Codeblockfor fenced code and let it choose a safe fence length. - Keep
render()deterministic and synchronous. - Do not introduce React or DOM runtime assumptions into
jsx-md. - Use context only for cross-cutting rendering state, not arbitrary global state.
Text Rules
- Bare JSX text is preferred for plain prose.
- Use
{...}only when JSX syntax requires it, such as backticks, braces,<,>, or apostrophes inside the text. - Keep XML attributes primitive and serializable.
Verification
- Run
bun testinpackages/jsx-mdfor renderer changes. - Run
bun run typecheckafter export, type, or JSX runtime changes.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.