aris pixel art

Design Community

Skill notes

Pixel Grid

Each "pixel" is a <rect> with width/height of 7px Grid spacing: 7px (no gaps between pixels) Characters are typically 8-10 pixels wide, 8-12 pixels tall Use <g transform="translate(x,y)"> to position and reuse character groups

Color Palette

Keep it simple — 3-5 colors per character: Skin: #FFDAB9 (light), #E8967A / #D4956A (blush/shadow) Eyes: #333 Hair: #8B5E3C (brown), #2C2C2C (black), #FFD700 (blonde), #C0392B (red) Clothes: use project's brand color (e.g. #4A9EDA for blue, #74AA63 for green)

Scene Composition

Chat Dialogue Layout (like our hero image) Two characters on left/right sides, vertically centered Chat bubbles between them, alternating left/right Bubble tails point toward the speaking character Arrows between bubbles show direction of communication

Step 1: Understand the Request

What characters/objects to draw? What's the scene? (dialogue, portrait, group, diagram) What colors/brand to match? What size? (compact for badge, wide for README hero)

Step 2: Generate SVG

Write to a temp file or project directory Open with open <file.svg> for preview Keep viewBox tight — measure actual content bounds

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
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@OpenLAIR · MIT
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: Understand the Request

What characters/objects to draw? What's the scene? (dialogue, portrait, group, diagram) What colors/brand to match? What size? (compact for badge, wide for README hero)

02
Step 2: Generate SVG

Write to a temp file or project directory Open with `open <file.svg>` for preview Keep viewBox tight — measure actual content bounds

03
Step 3: Iterate with User

User provides feedback on screenshot Common fixes: overlap, arrow direction, spacing, sizing Use `Edit` for small tweaks, `Write` for major redesigns Typical: 2-4 iterations to get it right

04
Step 4: Finalize

Ensure no personal info in the SVG Clean up: remove unused defs, tighten viewBox Suggest adding to README: `Alt text`

Discussion

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