{
 "schema_version": 1,
 "generated": "2026-10-19",
 "id": "wheresryan22-anatomy--explain-a-software-concept-as-a-physical-object",
 "repo": "wheresryan22/anatomy",
 "repo_url": "https://github.com/wheresryan22/anatomy",
 "repo_slug": "wheresryan22-anatomy",
 "title": "Explain a software concept as a working physical object",
 "page_title": "How to explain a software concept as a working physical object with anatomy",
 "summary": "Describe a concept like a cache key or rate limiter and get a figure built as a mechanism that behaves the same way.",
 "who": "Developer or technical writer preparing docs or a blog post on an abstract concept such as a token bucket",
 "problem": "Abstract ideas like caching or rate limiting are hard to show in a plain diagram.",
 "outcome": "An interactive figure where a physical mechanism (the README gives a pin-tumbler lock for a cache key) stands in for the concept, ready to embed.",
 "steps": [
  "Install the skill: npx skills add wheresryan22/anatomy -g",
  "In Claude Code run: /anatomy explain how a token bucket rate limiter works, interactive",
  "Interact with the result and check that the figure's numbers change as you play with it.",
  "Ask the agent to adjust the metaphor if it does not match your concept, then regenerate."
 ],
 "agent_prompt": "Using wheresryan22/anatomy, build an interactive figure that explains <software concept> as a physical mechanism. Output a single HTML page and verify the live readout matches the concept's real behavior.",
 "agents": [
  "claude-code",
  "codex"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The mechanism is an invented analogy, so review it for accuracy before publishing it as documentation.",
 "category": "Content & Creative",
 "tags": [
  "Content & Creative"
 ],
 "lang": "javascript",
 "requirements": [
  "An agent that supports Agent Skills: Claude Code, Antigravity, OpenCode, Codex or MiniMax Code",
  "Node.js 20.10 or later (the skills CLI itself may need a newer Node, 22.20 or later for version 1.7.1)",
  "Model usage costs from your agent account; the kit has no extra API keys or npm dependencies",
  "A browser to open the finished HTML pages (WebGL for the effects layer)"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "best": false,
 "score": 0.52,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/wheresryan22-anatomy/explain-a-software-concept-as-a-physical-object/",
 "md": "https://dedupedai.com/use-cases/wheresryan22-anatomy/explain-a-software-concept-as-a-physical-object/index.md",
 "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 hello@dedupedai.com and we will look at it promptly."
}