What this prompt does
This prompt builds a cohesive set of developer-themed avatar and profile images around a single visual identity rather than one isolated picture. You provide [developer_name], their [developer_role], and [tech_stack], plus [personality_traits], and it designs a primary avatar concept in [art_style], then derives platform-specific variants, mood variations, a conference badge, a cover banner, and a style guide that keeps future images consistent. The point is a recognizable mark, not a one-off render.
The variables drive both look and reuse. [avatar_color] and [avatar_shape] fix the core palette and frame, and the prompt is explicit that the design must stay legible at 48x48px, which forces simplicity. [badge_style], [variation_count], and [variation_elements] define how many mood states (default, presenting, celebrating, focused) you get and what changes between them, while [cover_dimensions] extends the same visual language into a banner. The closing style guide is what makes the set commissionable later.
When to use it
- Establishing a consistent personal brand across GitHub, X, LinkedIn, and Discord at once.
- Designing a conference or event badge that needs a circular avatar inset.
- Creating mood variations (speaker mode, milestone, deep-work) from one base concept.
- Producing a matching header or cover image that shares the avatar's style language.
- Writing a style guide so a future designer can extend the set without it drifting.
- Building a tech-stack badge system for a README or portfolio that matches your avatar.
Example output
You get a structured design package: a description of the primary avatar concept and palette, per-platform variant specs (GitHub square, circular X crop with safe zone, LinkedIn tone, Discord at 128px), a [badge_style] conference badge layout, [variation_count] mood variations describing exactly which [variation_elements] shift, a [cover_dimensions] banner concept, a color-coded badge system for each item in [tech_stack], and a style guide listing color values, art rules, and forbidden treatments. These are detailed briefs for a generator or designer, not final PNGs.
Pro tips
- Pick an
[art_style]that survives downscaling; intricate styles fall apart at the 48px target the prompt designs for. - Set
[avatar_color]as a real hex and let accents derive from[tech_stack]logos so the identity feels earned, not random. - Keep
[variation_elements]to a small set (background, expression, accessories) so variations stay recognizably the same character. - Match
[cover_dimensions]to the platform you actually use most; 1500x500 suits an X header but check each network's spec. - Lean on the generated style guide when commissioning later art so new pieces inherit the same rules.
- If variants look inconsistent, lower
[variation_count]and tighten what each one is allowed to change. - Treat the generated badge system for
[tech_stack]as reusable README assets, so your profile and repos share one visual language.
