infographic-generator
Skill336 starsChanged 10 months agoMITView on GitHub
Generate retro arcade style infographic prompts for documentation pages
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Samueladewole/claude-skillstheir own version, first seen Oct 13, 2026
- jobottinkwork/claude-skillstheir own version, first seen Oct 8, 2026
- Mnilax/infographic-skilltheir own version, first seen Oct 2, 2026
- mashharuki/claude-code-sampletheir own version, first seen Oct 1, 2026
- wulaosiji/founder-skillstheir own version, first seen Sep 9, 2026
- wulaosiji/skillstheir own version, first seen Sep 9, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Affitor/affiliate-skills★ 757same name
- reymerekar7/rm-skills★ 37same name
- wulaosiji/skills★ 28same name
- wulaosiji/founder-skills★ 9same name
- GPTtang/skill-atlas★ 4same name
- Mnilax/infographic-skill★ 2same name
- mashharuki/claude-code-sample★ 1same name
- jobottinkwork/claude-skills★ 0same name
- konglong87/infographic-generator-skills★ 0same name
- Samueladewole/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-prd-update-progressSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- publish-mock-serverSkill
- write-docsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask the user: "Which documentation page should this infographic be for?"
- Distinctive: line 20
Read the specified documentation file to understand its content.
- Distinctive: line 24
Create a retro arcade style prompt following this format:
- Distinctive: line 51
When the user provides the image path:
- Distinctive: line 53
Add the image to the documentation file at an appropriate location (usually near the top, after the title/intro)
- Very specific: line 54
Use markdown image syntax without width constraints: !Infographic description
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generate Infographic Prompt
Generate an image AI prompt for creating a retro arcade style infographic for a documentation page.
Workflow
Step 1: Ask for the docs page
Ask the user: "Which documentation page should this infographic be for?"
Present options from the docs/ directory (use Glob to find all .md files in docs/), or let them specify a custom topic.
Step 2: Read the documentation
Read the specified documentation file to understand its content.
Step 3: Generate the image prompt
Create a retro arcade style prompt following this format:
Create a retro 8-bit pixel art infographic for "[PAGE TITLE]" from DevOps AI Toolkit.
Style: Retro arcade game aesthetic, pixel art, CRT glow effects, scanlines, neon pink/cyan on dark background, NES game instruction card style.
TOPIC: [One sentence describing what this page covers]
KEY CONCEPTS (visualize as power-ups/abilities):
[For each major section/concept in the doc, write ONE line like:]
1. [Icon emoji] [CONCEPT NAME]: [One sentence description - no bullet lists]
[Include 3-6 concepts depending on the doc's content]
Include pixel art icons, game-style UI elements, and achievement badges related to the topic.Step 4: Present the prompt
Show the generated prompt in a code block so the user can copy it.
Then say: "Copy this prompt to your image generation AI. Once you have the image, tell me the file path and I'll add it to the documentation."
Step 5: Wait for image path
When the user provides the image path:
- Copy/move the image to the appropriate location in assets/images/
- Add the image to the documentation file at an appropriate location (usually near the top, after the title/intro)
- Use markdown image syntax without width constraints:

Confirm the image was added to the doc.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

