Skip to content

Skill

Imagegen Frontend Mobile

leonxlnx

Produces app screens as images, several at once so a flow reads as one product instead of unrelated frames, usually sat inside a plain handset shell. Handset-shaped work only, and it stops at the picture: no Swift, no React Native, no code at all.

A situation it fits

A fintech team has six onboarding steps sketched on a whiteboard and a stakeholder review on Thursday. They want the six as finished screens sitting in a plain handset shell, consistent enough that nobody claims they came from different products. The engineers have not chosen between React Native and Swift yet and do not want that pre-empted.
Imagegen Frontend Mobile. Several screens that have to read as one flow, framed in a handset, and deliberately no code: refusing to emit Swift or React Native is a rule this one states rather than an accident, which is exactly what protects the choice the engineers have not made. The most tempting wrong answer is imagegen-frontend-web, which shares the picture-only contract and the several-frames-one-product discipline - its trap is the shape, wide page bands rather than handset screens, and the shape is the one thing this brief pins down. image-to-code would settle the look and then write the frontend, pre-empting the very decision being protected. brandkit works on the identity, not on a product's screens.

Skills it gets confused with

These share a family with Imagegen Frontend Mobile, which is another way of saying they are the ones you might reach for by mistake.

Every comparison with Imagegen Frontend Mobile

Knowing what Imagegen Frontend Mobile does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Imagegen Frontend Mobile is part of leonxlnx/taste-skill. Licence: MIT. The description above was written for this game, not taken from the skill.