JAMES
138 posts


I’ve been a graphic designer since 2016. For most of those years, I earned nothing, but I stayed consistent.
I always had this feeling that something would eventually click if I didn’t stop.
I’m glad it finally did in 2023. Seven years later.
The magic lies in consistency.
Zazzy@zazzygfx
consistency my guy, consistency! I love consistency
English

@TechnicalBben I'm a UI/UX and graphic designer and I also do video editing. I help startups and brands turn rough ideas into designs that actually make sense and help you sell.
I'm open to collaborations and referrals.
English
JAMES 리트윗함
JAMES 리트윗함

These are my personal favourite go-to for website inspiration.
maxibestof.one/websites
onepagelove.com
landings.dev
godly.website
land-book.com
minimal.gallery
English
JAMES 리트윗함

Logo Design - From Concept to Presentation
dropbox.com/scl/fo/mg3xxd1…
English
JAMES 리트윗함
JAMES 리트윗함

These are my personal favourite go-to for website inspiration.
maxibestof.one/websites
onepagelove.com
landings.dev
godly.website
land-book.com
minimal.gallery
curated.design
English

Design Books
dropbox.com/scl/fo/uh6cnaj…
English
JAMES 리트윗함

@stefanchoju Lol 😂
Why he never post am for X
Design twitter dangelous
English
JAMES 리트윗함

Every designer should know these AI tools to speed up their workflow in 2026.
🧵 Here is the List below 👇 :
Save and repost this.
1.UX Research / UX Writing
→ chatgpt.com
2.Wireframing + UX Design + Prototyping
→ uxpilot.ai
3.Advanced Prototyping
→ figma.com/make
4.UI Creation / Wireframes
→ uizard.io
5.Brand Assets + Design Editing
→ moda.app
6.Pitch Deck Creation
→ gamma.app
7.Website / UI Design
→ framer.com/ai
8.AI Thinking Partner
→ claude.ai
9.Vibe Coding
→ lovable.dev
10.Vibe Animating
→ lottiefiles.com/ai
📌AI won’t replace designers.
But designers who use AI will replace those who don’t.
Follow me and turn on notifications 🔔
Which of these are you using already? 👇

English
JAMES 리트윗함

I gave Claude one prompt.
It built me a full app architecture. For every single screen.
Sitemap. User flows. Microcopy. Error states. Empty states.
UX designers, save and repost this to help any UX Designer struggling to understand how to design a full product end to end. 👇
Don’t miss to hit the follow button if you want to get more insight on how to 10x your workflow.
The prompt 👇
You are a Senior UX Designer and Information Architect with 10+ years of
experience designing complex digital products. I need you to generate a
complete UX architecture document for my product.
---
PRODUCT CONTEXT
- Product name: [NAME]
- Product type: [Web app / Mobile app / Both]
- Industry: [e.g. Fintech / Health / E-commerce / SaaS]
- Target users: [Describe your primary user, who they are, their goals,
tech comfort level]
- Core problem it solves: [1–2 sentences]
- Key user actions (the 3–5 things users must be able to do): [List them]
- Any known competitors or inspiration: [Optional]
---
WHAT I NEED YOU TO GENERATE
1. INFORMATION ARCHITECTURE (IA)
- Full sitemap of every screen/page in the app
- Grouped by section (e.g. Onboarding, Dashboard, Settings)
- Hierarchy shown clearly (parent → child pages)
- Navigation structure (bottom nav / sidebar / top nav, recommend which
and why)
2. USER FLOWS
Generate step-by-step user flows for these core journeys:
- Onboarding & account creation
- Core action flow (the main thing the user comes to do)
- Settings & profile management
- Error recovery flow
For each flow: show every screen the user touches, the decision points,
and what happens on each path (success, error, edge case).
3. FULL SCREEN-BY-SCREEN BREAKDOWN
For EVERY screen in the app, provide:
- Screen name
- Purpose (what the user is trying to do here)
- Key UI elements on the screen
- Primary action (main CTA)
- Secondary actions
- Navigation options available
4. MICROCOPY FOR EVERY SCREEN
For each screen, write the actual copy for:
- Page/screen title
- Subheading or supporting text
- CTA button labels
- Input field placeholder text and labels
- Tooltip or helper text (where relevant)
5. ERROR STATES
For every screen or action that can fail, write:
- The error scenario (what went wrong)
- Error message headline (short, clear)
- Error body copy (explain what happened + what to do)
- CTA label to recover (e.g. "Try Again", "Go Back", "Contact Support")
Cover at minimum: form validation errors, network/connection errors,
permission denied, session expired, payment failure (if applicable).
6. EMPTY STATES
For every screen that can appear empty (no data yet), write:
- Empty state illustration description (what to show visually)
- Headline
- Supporting copy
- CTA to help user take their first action
Cover: first-time user empty states AND zero-result search/filter states.
7. LOADING & TRANSITION STATES
For key screens, describe:
- What loading state looks like (skeleton screen, spinner, etc.)
- Loading copy if any (e.g. "Getting your dashboard ready…")
- Transition message after a completed action
(e.g. success toast, confirmation screen)
8. STRUCTURAL RECOMMENDATIONS
Based on the product type and user goals:
- Recommend the best navigation pattern and why
- Flag any screens that might cause confusion or drop-off
- Suggest any flows that could be simplified or merged
- Identify where progressive disclosure should be applied
- Call out any accessibility considerations per screen
---
OUTPUT FORMAT
Structure your response like a UX specification document with clear
headings for each section. Use tables where it helps clarity
(especially for microcopy and error states). Be exhaustive, I want
this to be thorough enough to hand directly to a developer or use as
a Figma annotation reference.

English













