Design Principles
Constraints are the tools of a designer
1. Make It Obvious
If someone can’t get it in 3 seconds, it’s not ready.
Why this is yours
You value clarity, precision, and efficiency. Recruiters need fast comprehension — your work must speak instantly.
Rules
One idea per section.
Reduce until it clicks at first glance.
Use whitespace the way editors use silence — to reveal what matters.
If it doesn’t help understanding, cut it.
Example
Your case study headers answer the question “What am I looking at?” without reading.
2. Show Your Mind
Sketch it. Animate it. Visualize it. Make people see your thinking.
Why this is yours
Your identity is storytelling through visuals and filmmaking instincts.
Your strength is showing thought, not describing it.
Rules
Lead every section with a visual anchor.
Replace paragraphs with sketches, flows, or micro-demos.
Use annotations like storyboards: focused, essential, revealing.
Make before/after visuals explain the rationale for you.
Example
A rough pencil sketch next to the final UI that instantly communicates your insight.
3. Guide With Motion
Use subtle movement and cursor behavior to guide, not perform.
Why this is yours
Your cinematic instinct comes alive through micro-interactions and pacing.
Your goal: a website that feels alive, organic, intentional.
Rules
Motion = direction. Never decoration.
Cursor acts like a silent character (pointing, highlighting, reacting).
Micro-interactions should feel like breath — small, purposeful.
Transitions should clarify hierarchy, not show off.
Example
Cursor highlights key project elements by subtly shifting weight or glow, like a guide.
4. Tell It Like a Film
Every project is a story: setup → tension → insight → transformation → impact.
Why this is yours
You think like a filmmaker. You build narrative beats, not slideshows.
Your process is emotional, structured, and driven by revealing “why.”
Rules
Hook with the moment that started the problem.
Show the turning point — your insight or decision.
Reveal transformation through visuals, not paragraphs.
End every project with the result or what you learned.
Example
A storyboard of the user moment that triggered the redesign.
