UI & Social Mockups
Handwritten Notebook Photo
Handwritten Notebook Photo prompt pattern with controls, failure modes, attribution, and a case-specific rewrite checklist for ui & social mockups.
handwritten notebook photo prompt
UI concept frames, social screenshots, keynote photos, notebook pages, feed mockups, and creator-content thumbnails.
Adapted prompt template
Copyable derivative prompt
This page turns the source case "Handwritten Notebook Photo" into a reusable ui & social mockups pattern that can be adapted without copying the original prompt verbatim.
UI concept frames, social screenshots, keynote photos, notebook pages, feed mockups, and creator-content thumbnails.
UI and screenshot prompts work when they treat platform chrome, text density, camera artifacts, and device framing as first-class prompt ingredients.
Generate a realistic notebook photography with handwriting, cross-outs, and daylight texture. The result should look like a captured product or social artifact, not a clean design board.
Platform or device: {{platform_device_and_screen_ratio}}
Primary scene: {{screen_content_or_mockup_goal}}
Capture style: {{camera_angle_reflections_noise_or_compression}}
UI chrome: {{status_bar_buttons_notifications_comments}}
Text behavior: {{what_text_must_be_readable_and_what_can_be_abstracted}}
Visual finish: {{lighting_surface_and_background_context}}
Quality rules:
- match platform conventions before adding decorative detail
- keep text amount realistic for the renderer
- include mild imperfections when the image should feel photographed
- check trademark, likeness, and impersonation boundaries before commercial use What to change first
- platform or device frame
- screen density and text blocks
- camera angle and artifact level
- ambient light and reflections
- notification chrome or status bar
- brand and likeness boundaries
How to apply this pattern
Use this page as a working prompt brief, not as a one-click style copy. First confirm that the page's stated fit matches your actual task: UI concept frames, social screenshots, keynote photos, notebook pages, feed mockups, and creator-content thumbnails. Then rewrite the subject, scene, camera, composition, and review rules so the output fits your own use case.
| Step | What to decide | Why it improves the result |
|---|---|---|
| 1. Define the job | UI concept frames, social screenshots, keynote photos, notebook pages, feed mockups, and creator-content thumbnails. | Prevents the prompt from becoming a vague style request. |
| 2. Pick the strongest controls | platform or device frame, screen density and text blocks, camera angle and artifact level | Gives the model concrete constraints instead of decorative adjectives. |
| 3. Preserve the source boundary | Use the source as inspiration, not as text to republish. | Keeps the page useful while respecting creator attribution. |
| 4. Review known failures | mockups that look like generic Figma boards instead of captured screens | Turns the most likely mistake into a pre-flight check. |
Rewrite memo
- Start the Handwritten Notebook Photo rewrite by naming handwritten, notebook, photo, not by pasting the original sample. The @patrickassale source should remain a credit line while the working brief uses your own subject, output owner, and review standard.
- For handwritten notebook photo prompt, define one acceptance condition before generating: the result must match the stated fit (UI concept frames, social screenshots, keynote photos, notebook pages, feed mockups, and creator-content thumbnails.) without triggering "mockups that look like generic Figma boards instead of captured screens".
- Use platform or device frame as the first editable field for Handwritten Notebook Photo. If that control is still vague, the prompt is not ready for a useful model run.
- Keep screen density and text blocks separate from mood words. This prevents Handwritten Notebook Photo from becoming a generic ui & social mockups request with no measurable constraint.
- When comparing related cases, ask whether One-Prompt UI Design Generation has a closer failure mode than Handwritten Notebook Photo. Choose the case with the stricter review rule, not the prettier example.
- Record the final Handwritten Notebook Photo variant with model name, source link, changed variables, and rejection notes. That record is the part future users can trust.
- Do not scale generation volume for handwritten notebook photo prompt until one result passes the first failure check and one result is rejected for a documented reason.
Case-specific adaptation read
The useful part of Handwritten Notebook Photo is the specific production constraint behind the prompt opening: Generate a realistic notebook photography with handwriting, cross-outs, and daylight texture. The result should look like a captured product or social artifact, not a clean design board. Treat that line as the case anchor. The rest of the brief should be rewritten around your own subject, rights context, output size, and review standard.
| Case signal | Use it to decide | Do not copy blindly |
|---|---|---|
| Handwritten Notebook Photo by @patrickassale | Which visual problem made the original example worth studying. | The creator's subject, identity, brand context, or exact composition. |
| platform or device frame, screen density and text blocks, camera angle and artifact level, ambient light and reflections | Which knobs should be changed before the prompt is useful for a new task. | Category-wide adjectives that do not change the acceptance criteria. |
| mockups that look like generic Figma boards instead of captured screens | The first rejection reason to check before saving or publishing an output. | A visually pleasing result that still fails the stated control. |
| image prompts, gpt-image-2, prompt patterns, ui mockup prompts | Whether this belongs in a prompt test, campaign brief, mockup pass, or comparison set. | Using the same output in a commercial workflow without rights and policy review. |
Compare this case against One-Prompt UI Design Generation, Amateur iPhone Keynote Snapshot, Song Dynasty Social Media Feed before choosing it as the working pattern. If the nearby page has a closer failure mode or control set, start there instead.
Rewrite worksheet
| Checkpoint | Inspect this case signal | Rewrite action | Reject when |
|---|---|---|---|
| Handwritten Notebook Photo task boundary | UI concept frames, social screenshots, keynote photos, notebook pages, feed mockups, and creator-content thumbnails. | Replace the borrowed subject with the real owner, setting, and output context for handwritten notebook photo prompt. | mockups that look like generic Figma boards instead of captured screens |
| platform or device frame control | Generate a realistic notebook photography with handwriting, cross-outs, and daylight texture. The result should look like a captured product or social artifact, not a clean design board. | Turn the opening line into a concrete platform or device frame decision before changing style words. | perfectly clean screenshots when a camera-photo look was intended |
| screen density and text blocks evidence | UI and screenshot prompts work when they treat platform chrome, text density, camera artifacts, and device framing as first-class prompt ingredients. | Keep the review tied to handwritten, notebook, photo; remove any generated detail that cannot be checked against that signal. | too much text for the renderer to keep stable |
| @patrickassale reuse boundary | Handwritten Notebook Photo by @patrickassale; CC BY 4.0 attribution-required source inspiration | Credit the source case, then document the changed variables and final prompt variant for Handwritten Notebook Photo. | brand or celebrity references with no boundary note for commercial use |
Case fit notes for Handwritten Notebook Photo
Choose Handwritten Notebook Photo only when the brief needs the specific signal set handwritten, notebook, photo. If the task can be solved by any generic ui & social mockups prompt, use the category page instead; this case is meant for a narrower rewrite decision tied to handwritten notebook photo prompt.
| Fit check | How to read this case | What would make it the wrong starting point |
|---|---|---|
| Handwritten Notebook Photo | Keep the handwritten, notebook, photo signal visible while replacing the subject, setting, and output context with your own brief. | The final image depends on copying the original creator's exact subject or framing. |
| @patrickassale | Use the source as evidence that the pattern is worth studying, then document your own rewrite choices before publishing or reusing the result. | The attribution is treated as permission to clone the original post. |
| Generate a realistic notebook photography with handwriting, cross-outs, and daylight texture. The result should look like a captured product or social artifact, not a clean design board. | Translate the opening line into concrete scene, camera, layout, or evaluation requirements instead of leaving it as an aesthetic slogan. | The first generated output looks attractive but cannot be judged against a specific requirement. |
| handwritten notebook photo prompt | Match the page to a user who is trying to adapt this exact prompt pattern, not someone browsing random inspiration. | The visitor needs a broader tutorial, model review, or image gallery rather than a reusable brief. |
| mockups that look like generic Figma boards instead of captured screens | Run this failure check before increasing generation volume; one corrected constraint is usually more valuable than another batch of similar outputs. | The review accepts visual polish while ignoring the first stated failure mode. |
Common failure modes
- mockups that look like generic Figma boards instead of captured screens
- perfectly clean screenshots when a camera-photo look was intended
- too much text for the renderer to keep stable
- brand or celebrity references with no boundary note for commercial use
Originality and review checklist
The original value of this page is the reusable control model: UI and screenshot prompts work when they treat platform chrome, text density, camera artifacts, and device framing as first-class prompt ingredients. Before publishing or sharing an output, check whether the final image can stand on its own without depending on the source post, creator identity, or a hidden reference that the viewer cannot inspect.
- Replace placeholders with your own subject, scene, product, or visual brief.
- Keep any visible brand, person, or copyrighted character use inside your own permission rules.
- Compare the output against the failure modes before using it in a client, product, or campaign workflow.
- Record the final prompt variant so future iterations can be reviewed instead of guessed.
Attribution and reuse boundary
This page is an original derivative pattern built from a public community case collected by EvoLinkAI's awesome-gpt-image-2-prompts repository and the linked creator post. It keeps attribution intact while avoiding verbatim prompt reuse.
Source lineage: repository README / original case / CC BY 4.0 attribution-required source inspiration
| Source record | Case value | Review use |
|---|---|---|
| handwritten-notebook-photo | Handwritten Notebook Photo | Use this slug to track revisions, redirects, and future consolidation decisions. |
| @patrickassale | https://x.com/patrickassale/status/2044569086013718958 | Verify that attribution remains visible and that the page does not imply ownership of the source case. |
| handwritten notebook photo prompt | UI & Social Mockups | Confirm that the page targets a specific adaptation task instead of a broad image gallery query. |
| CC BY 4.0 attribution-required source inspiration | Handwritten Notebook Photo by @patrickassale | Keep the derivative prompt, notes, and rewrite memo separate from the original creator post. |