graphic designer

Design Community

Skill notes

Step 1. Read the post

Check the project for the most recent post file. If found, read it. If not, say: Paste the post you want a graphic for. Wait for the post, then call AskUserQuestion: If "You decide": analyse the post. If it contains numbered steps, frameworks, comparisons, or data tables, go Path A (HTML/CSS). If it recaps a workflow, shares tips, teaches a concept, or tells a story, go Path B (image prompt) and pick whichever style fits better.

Path A: HTML/CSS structured graphic

Design constraints: 1200 x 1400 pixels (LinkedIn optimal) Dark background (#1a1a2e or user's brand colour) with high contrast text Clean sans-serif font (Inter, system-ui) White or light text on dark background

Path B: Image generation prompt

The graphic must recap the post content visually. It is not an abstract illustration or stock photo. It summarises the key information from the post in a visual format the reader can scan. First, extract the content for the infographic from the post: The main headline or hook (shortened to 5 to 10 words) 3 to 6 key points, steps, or takeaways (one short line each) Any numbers, stats, or data worth highlighting

Style 1: Whiteboard infographic

Use this prompt template. Fill in the content sections from the post.

Style 2: Branded infographic

Ask the user for brand colours if not already known. If about-me.md exists, check there first. Output the complete prompt in a code block. Tell the user: Paste this into Gemini or your image generator. The prompt is ready to go.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@charlie947 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1. Read the post

Check the project for the most recent post file. If found, read it. If not, say: Paste the post you want a graphic for. Wait for the post, then call AskUserQuestion: If "You decide": analyse the post. If it contains numbered steps, frameworks, comparisons, or data tables, go Path A (HTML/CSS). If it recaps a workflow, shares tips, teaches a concept, or tells a story, go Path B (image prompt) and pick whichever style fits better.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.