DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to generate a React component of a figure for a docs site with Anatomy

Create a React or Next.js component version of an explainer figure for a documentation site.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA developer maintaining a Next.js documentation site who wants a figure built as a component.

The problemPasting an HTML file into a component-based docs site breaks the page structure and styling.

The outcomeA React component and a static HTML preview of the same figure, ready to import into a docs project.

What you need first

  • Node.js (the README says version 1.7.1 of the skills CLI asks for 22.20 or later)
  • Claude Code, Codex, or another supported agent with the skill installed
  • Headless Chrome, which the skill uses to check its own figures
  • No API keys and no npm install are needed, since the kit uses only Node's built-in modules

Steps

  1. Run npx skills add wheresryan22/anatomy to install the skill into the current project.
  2. Run /anatomy and ask for a React component plus a static HTML preview for your docs site.
  3. Place the generated component in your Next.js project and import it into the page.
  4. Run node scripts/capture.mjs page.html --out shots/page.png on the HTML preview to check the look.

Prompt for your agent

Using the skill in wheresryan22/anatomy, create a React component of <concept> for a Next.js docs page, with a static HTML preview. Expected output: one component file and one HTML preview. Verify that the component imports cleanly into your existing project before committing it.

Caveat. The README lists React and Next.js components as an output, but it does not describe how they plug into a specific docs framework, so test the import in your own project.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page