GistHubs project showcase visuals
Create a visual proof system for the story. Every important visual should prove a capability, clarify a mechanism or establish the project's identity.
Choose the right source
Use this order unless the story requires otherwise:
- real product screenshots;
- real interaction states or terminal output;
- diagrams derived from the implementation;
- composed showcase cards using real assets;
- generated decorative art.
Generated art may express mood, but it must not impersonate a product screen, metric, user, integration or feature that does not exist.
Build the visual set
Plan a coherent set rather than unrelated images:
- one cover with a single readable focal message;
- one product proof image for the key experience;
- supporting screenshots or diagrams only where they add new information;
- optional social crops that preserve the same identity.
For each asset record its role, source, dimensions, alt text, crop safety and publication path. Record tool/model and prompt summary for generated assets. Keep original captures available when a composed image uses them.
Quality gate
Inspect every final pixel output at full size and at feed-thumbnail size. Confirm:
- text is legible and not clipped;
- the screen is real and current;
- cursor, notifications, usernames and secrets are removed when irrelevant;
- diagrams match the implementation;
- visual hierarchy survives mobile width;
- generated text and logos contain no artifacts.
Add approved assets to the Draft Bundle. Do not publish evidence-only captures or rejected variants by default.