sample-01
steel-project is an image-editing application built for one specific kind of material: images that were generated by artificial intelligence. It is not a personal-photo editor, and it is not a photo-management or identity-document tool. The product exists so that a solo creator who generates synthetic images can bring those machine-made images into a focused editing workspace, apply edits, and produce finished edited results.
The audience is the AI Image Creator — a self-starting maker (the user, ALi, Arabic-speaking, typically working late) who treats AI-generated imagery as raw material to be remixed. The product's register is playful, uncensored and studio-like: a maker's toy for remixing machine dreams, deliberately operating without NSFW content limits, as explicitly requested. The surface should read as free, sensual and optimistic rather than policed and clinical.
The product intent, in one line: take AI-generated images, edit them freely, and keep the results.
steel-project is a first-party web application with application-owned identity and custom UI. It delivers:
Actors. The only active human persona is the AI Image Creator. The application itself owns identity, durable image storage, and the editing workspace. No other human roles, administrators, moderators, or reviewers are part of the current product.
Accepted behavior. Editing AI-generated images; operating without NSFW content limits; self-service enrollment; returning verification; durable storage of selected source images and edited results.
Narrow exclusions. The product is not for editing personal photos, and it is not a photo-capture, photo-organization, or identity-document tool. No stock photography of people and no imagery implying personal-photo editing appears in the product surface. There is no content-moderation gate, no NSFW warning banner, and no clinical safety iconography.
Delivery ownership. steel-project is delivered as a first-party application with its own custom interface. The application owns the Landing, Sign Up, Login, Library and Editor surfaces. There is no provider-owned or external-only surface in the current product, and no headless-only delivery.
Access ownership. Identity is application-owned. The Landing, Sign Up and Login surfaces are reachable anonymously — a visitor can read what the product is and can establish or verify identity without first being authenticated. The Library and Editor require login, because the creator must privately own and resume durable, actor-specific image state across sessions. Establishing access to a protected destination never happens inside that protected destination: enrollment and verification live on their own anonymous surfaces.
Current vs. future boundary. Everything described in this document is current. No future-horizon requirements were stated by the user; nothing in this document is deferred, and nothing outside the accepted scope is implied.
Content boundary. The application edits images generated by artificial intelligence. It does not accept or target personal photographs as its purpose, and the interface must not present itself as a personal-photo utility.
Not applicable — no reference directive in this project declares a content_source.
FR-1 — Edit AI-generated images (explicit) As an AI Image Creator, I should bring an AI-generated image into the Editor and apply edits to it, so that I produce an edited version of a machine-made image.
FR-2 — Work on AI-generated images, not personal photos (explicit) As an AI Image Creator, I should use the application for images generated by artificial intelligence rather than personal photographs, so that the tool matches the material I actually work with.
FR-3 — Operate without NSFW content limits (explicit) As an AI Image Creator, I should edit my AI-generated images without NSFW content limits, so that my work is not restricted by a moderation gate.
FR-4 — Self-service enrollment (required_inference) As an AI Image Creator, I should create my own account from the Sign Up surface, so that I can start using the application without waiting on anyone else.
FR-5 — Returning verification (required_inference) As an AI Image Creator, I should verify my identity on the Login surface, so that I can resume access to the application and my durable image workflow.
FR-6 — Durable storage of source and edited images (required_inference) As an AI Image Creator, I should have my selected source images and edited results stored durably, so that I can revisit and continue work across sessions.
FR-7 — Select an image before editing (required_inference) As an AI Image Creator, I should browse and select from my stored AI-generated and previously edited images in the Library, so that I can choose what to work on next.
FR-8 — Commit an edited result (required_inference) As an AI Image Creator, I should commit my edits with a single unmistakable finish action, so that I know when the result is final.
Product context. The AI Image Creator is a solo maker — the user, ALi, Arabic-speaking, typically working late — who generates images with artificial intelligence and treats them as raw material. The material is synthetic by definition: machine-made images, not personal photographs, not identity documents. The creator's register is playful and studio-like; the tool should feel like a glossy object on a shelf, a maker's toy for remixing machine dreams, not a corporate photo utility.
Primary goal. Take an AI-generated image, edit it in the application, and keep the edited result — without hitting a content limit that stops the work.
Distinct accepted responsibilities.
Relevant inputs and decisions. Which AI-generated image to work on; which tool and parameter values to apply; whether the pending edit is good enough to commit or should be discarded; whether to continue with the current image or return to the Library for another.
Interactions with other accepted participants. There are no other human participants in the current product. The creator interacts only with the application itself — its identity surfaces, its Library, and its Editor. No administrator, moderator, reviewer, or collaborator is involved, and no approval or handoff to another person exists in the accepted scope.
Observable success. An edited AI-generated image exists in the Library, produced without a moderation gate interrupting the work, and is still there when the creator returns in a later session.
What makes this role distinct. The creator is defined by the material, not by a job title: the work is editing synthetic, machine-generated imagery, and the product's whole surface — its imagery, its tone, its absence of NSFW limits — is shaped around that material. A generic "user of a photo editor" would not capture the constraint that the input is AI-generated rather than personal, nor the explicit freedom from content limits that the creator asked for.
Muse and headline. Karim Rashid — sensual pop minimalism for machine-made images: glossy curves on candy grounds. The product is a glossy object on a shelf, not a corporate photo utility.
Colour tokens — light mode.
| Role | Hex | Use |
|---|---|---|
| Background (ground) | #FFE9F3 | Bubblegum-pink ground covering the whole app — never white-first, including auth and editor |
| Surface | #FFFFFF | Glossy white pebble panels floating on the pink ground |
| Text | #1A0B1F | Near-black plum; 14:1 contrast on the pink ground |
| Primary | #FF2D9B | Hot Rashid pink — buttons, active tool, progress, the selection outline in the editor |
| Accent | #C6FF3D | Acid lime — used sparingly: the "طبّق" commit action, the live badge, the one thing you press to finish |
| Muted | #8A6C86 | Labels and metadata |
Proportion. 60% pink ground, 25% white surface, 10% pink primary, 5% lime.
Prohibited colours. No blue, indigo or violet anywhere — no #0057FF, #2563EB, #6366F1, no bootstrap-blue buttons, no blue-on-white. No flat neutral greys.
Typography.
#8A6C86.Shape language. Everything is a capsule, a blob or a pebble — no sharp corners anywhere. Buttons are full pills (radius = height/2). Panels are 32px-radius rounded rectangles. Section boundaries between landing blocks are cut as soft S-curves and wave edges, not straight lines. The editor's canvas frame is a single large pebble with a 40px radius and a 3px glossy pink rim. Sliders use a capsule track with a round glossy thumb carrying a tiny white specular highlight. Chips and tags are pills. Even the loading state is a morphing blob, not a spinner.
Elevation. Soft pink-tinted shadow — #FF2D9B at 12% opacity, 0 24px 48px -12px — instead of grey drop shadows, so cards look like resin objects sitting on pink. Surfaces carry a 1px pink hairline.
Spacing rhythm. Generous breathing room; the editor frame sits on pink with visible margin, never edge-to-edge chrome. Landing blocks stack as full-bleed colour fields separated by S-curves.
Imagery style. The product's own output is the imagery — AI-generated images shown large, glossy, saturated and uncropped, presented like objects in a display case on pink or white pebble plinths with

AI image remix studio
steel-project is a studio for remixing images your AI already made — synthetic art in, synthetic art out. No personal-photo workflow, no content limits.
Machine-made gallery
steel-project edits images generated by artificial intelligence. Every figure on this rail was made by a model, never photographed.
sample-01
sample-02
sample-03
sample-04

AI image remix studio
steel-project is a studio for remixing images your AI already made — synthetic art in, synthetic art out. No personal-photo workflow, no content limits.
Machine-made gallery
steel-project edits images generated by artificial intelligence. Every figure on this rail was made by a model, never photographed.
sample-01
sample-02
sample-03
sample-04
No comments yet. Be the first!