1Brief
One page, written from the first call: goals, users, constraints, and what's explicitly out of scope.
I'm Trisna, a UI/UX designer based in Bali. For seven years I've designed dashboards, mobile apps and marketing sites for fintech, hospitality, SaaS and edtech clients across Australia, New Zealand and Southeast Asia.
That range is why I adapt quickly. A product designed from zero, a redesign of something that already has users, or a single page that has to convert: I've done all three, and I know which parts to skip.
I've worked remotely for most of that time, so I'm direct about scope, quick to reply, and used to clients in a different timezone. You always know what's happening and what's next.
I don't start with a mood board. I start with the problem: what's not working, who's frustrated, where the friction is.
Once that's clear, I move quickly. AI lets me open several directions in an afternoon instead of a week: different structures, different tones, different levels of density. I read what each one gets right and wrong, then commit to a direction instead of polishing a guess.
From there I prototype in code. A working screen tells the truth about spacing, motion, and empty states in a way a static mockup never does. The thing you review ends up being the thing that ships.
What AI doesn't do is decide. It can produce twenty variations of a screen in a minute and still not know which one a nervous first-time user will trust. That part stays with me: judgment, taste, and knowing what to leave out.
Six steps from the first call to a live site. AI does the drafting, I do the deciding.
Toggle AI and Me on any step to see who does what. This is the order I run a project in, not a fixed script.
One page, written from the first call: goals, users, constraints, and what's explicitly out of scope.
Before one screen exists I write the rules down: stack, spacing scale, colour and type tokens, accessibility floor.
Several directions, each shared as a clickable prototype link. You move through them and pick before anything is committed.
If your team lives in Figma, Figma MCP lets Claude read the real components and variables, and push tokens back.
Claude Code writes the first pass. Every change lands in a branch and a pull request, so nothing is invisible and nothing is permanent.
Each branch gets its own preview URL, so you review the real site on your own phone. Approve it and it deploys to your domain.
Analytics and error logs show what real visitors actually do. Those findings go back into the brief and the next round starts there.
This is my default order, not a script. A single landing page skips to Build. A product that already lives in Figma starts at Connect. A site that only needs fixing starts at Ship.
Daily tools: Claude Code, Figma MCP, Next.js, GSAP, GitHub, Vercel.
Good design doesn't announce itself. If a user notices the interface, something probably went wrong.
I care about the small things: spacing that breathes, labels that make sense on first read, states that don't surprise anyone. That discipline adds up. It's the difference between a product people tolerate and one they actually trust.
No pitch decks needed. No commitment. Just a relaxed conversation about your project, even if it's still just an idea.