Concept
Turns the brief into the page idea: the promise, the tone, what it stands on.
These roles come from OKYS workflows. They join according to the scenario and settings, and their output informs the next stage.
People set goals. Roles do the work.
Turns the brief into the page idea: the promise, the tone, what it stands on.
Builds the page outline: which blocks, in what order and why each one.
Writes the page script: what a person reads screen by screen and where it leads.
Decides where the page needs pictures and what is on them.
Storyboard of the reel: scenes, frames, motion.
Looks at the files and links sent in: are they about the client and are they usable. A smart model reviews the doubtful rejections.
Pulls checkable facts out of the materials and reconciles the contradictions.
Collects the market picture along axes: demand, prices, objections, the language of the niche.
Reads other people's pages: structure, blocks, promises.
Reads the design of a page with its own eyes: mood, palette, rhythm and the flow top to bottom.
The audience portrait: pains, words, objections — and the vocabulary to speak with them.
Puts other people's pages side by side: where everyone is the same and what nobody says.
Reads reviews about the niche: what gets praised and what gets complained about.
Writes the block text and variants from different angles.
Compares block variants: each judge looks strictly through their own lens.
Proofreads the page: typos, line breaks, micro-typography.
Looks for promises in the text that must not be made.
Holds the page's through-line so the blocks do not drift apart.
Understands the client's edit and rewrites exactly what it touched.
Gathers the brand voice and promise into a styleguide.
Picks the design axes: life, texture, accent.
Lays the page out: rhythm, grid, the kind of every block.
Looks at the assembled page with real eyes and says what is wrong.
Looks at the finished page top to bottom and catches defects.
Hunts for tell-tale AI clichés on the finished page.
Fixes a section the browser measured as overflowing the screen or squeezed into a narrow column.
Looks at the generated picture: does it fit its place.
Codes the section as markup rather than assembling it from ready blocks.
Lays out the whole page: draws the section boundaries itself and invents their markup and styles.
Finishes the page design and checks the result with a seeing model.
Puts a captured design system into words: what holds it together and what it never does.
Looks at a screenshot of a foreign site and calls out type sizes, corners and spacing by eye — where there is no stylesheet to measure.
Matches the client's wish for the look against the studio's ready design systems — or plainly says none of them fits.
Adds staging to what the person wrote: light, camera angle, how close the shot is. Leaves genre, medium and subject alone.
Spreads a batch along a single axis — camera angle, light, how close the shot is — so there is something to choose between. Called instead of the stager: every variant arrives as a finished prompt.
Turns a request about a finished picture — “take the hat off” — into a whole prompt. The network remembers nothing of the previous frame: without this role three words of the request would go to it instead of a frame.
Looks at the shot with real eyes and decides whether it will do. Rejected it — writes the prompt for one retake; there is never a second.
Turns the task into narration text for the selected format.
Reads the latest posts of a venue and says in three to five sentences what the channel is and what it lives on. The client sees this gist in the channel catalogue.
The roster comes from the application registry and changes with its code. The role count does not mean every role runs on every order.
You have the idea. Take the first step.
Free DEMO · No credit card required