Design system
from scratch
Wireframes first to define layout and hierarchy. Then a reusable library of buttons, cards, navigation, and forms created a lightweight design system for building new screens faster.
UI/UX and graphic design from Birgunj, Nepal. I design interfaces people can actually use — then hand developers files they can actually build.
I'm Kaushal — a designer from Birgunj who learned the front end first, so I know exactly what happens to a layout after the handoff.
I work across UI/UX and graphic design in Birgunj, Nepal: Figma wireframes, component libraries, e-commerce flows, logo and brand marks, and the WordPress websites they end up living inside. Most of my day is Figma, but I also build in WordPress and Elementor, write the HTML and CSS when it's faster, and handle the on-page SEO so the work is actually findable once it's live.
I taught frontend development to beginners for six months in 2024. That's the part that changed how I design — spending that long explaining how a layout turns into code makes you stop drawing things that can't be built. Now I lead design, development and marketing tasks at Pinned Agency, and run my own studio, Codexdesign, alongside it.
Every new screen started from a blank frame. Buttons drifted, spacing drifted, and developers received files that each looked slightly different from the last. The brief was to design the main project — but the real problem was upstream of it.
I started low-fidelity: greyboxes only, no colour, no type decisions. The job at this stage was to settle layout, structure and content hierarchy while it was still cheap to change. Once the skeleton held up, the high-fidelity pass had something to be faithful to.
Buttons, cards, navigation, form elements — each drawn once, with its states, and reused everywhere after. Instead of designing a page and extracting components from it, we designed components and assembled pages out of them.
Not a hundred-page governance document — a small, usable set: the components, the type scale, the colour roles and the spacing rhythm. Small enough that the team actually opened it, complete enough that new screens stopped being guesswork.
Alongside the system, I redesigned visual flows on a live site by looking at how people were actually navigating it — where they hesitated, where they doubled back — and reordered the path around that rather than around the sitemap.
Wireframes, a reusable component library and a lightweight design system the team could design against.
Listing pages, product detail views and a checkout flow shaped so browsing leads naturally to buying.
Full visual layout from homepage to key content pages, drawn with the build in mind.
On-page structure, titles and categories rebuilt around real search demand, then measured.
An Instagram identity for a handmade brand. Built simple on purpose — it had to stay legible as a 32px profile photo and as a watermark sitting over busy product shots.
Feed posts and stories drawn from one set of rules, so a campaign stays recognisable as it changes shape across formats.
My own studio's content: promotional posts, educational carousels and brand graphics, kept consistent enough to look like one place.
UI/UX design in Figma: wireframes, user flows and high-fidelity screens, with interactive prototypes when a flow needs testing before it gets built.
A component library and the rules around it: type scale, colour roles, spacing. Sized so your team will actually use it.
Logo design and brand identity: marks built to survive small sizes and busy backgrounds, plus the pieces that keep a brand recognisable everywhere it appears.
WordPress and Elementor web design carried through to a live, responsive site — or handed to your developers with the details already resolved.
On-page SEO: keyword research, page titles, headings and site structure, so the work you paid to design is findable once it ships.
Social media design: feed posts, stories and campaign creatives made as a set, adapted across formats without losing the thread.
What the page has to do, who it's for, and what counts as it working. Written down before anything is drawn.
Greyboxes only. Layout, structure and hierarchy settled while changing them is still free.
Components, type scale and colour roles defined once, so every screen after this one is assembly rather than invention.
The real thing: states, spacing, responsive behaviour. Prototyped where a flow needs to be felt, not described.
Named layers, resolved edge cases, and answers to the questions developers are about to ask. Or I build it myself.
On-page SEO, analytics and Search Console once it's live — then changes based on what people actually do.
If someone has to work out what a screen wants from them, the layout has failed. Hierarchy first, decoration last.
I've taught people to write the code. So I don't draw things that can't be built, and I resolve the edge cases before handoff rather than after.
One good button, reused, beats twelve good buttons. Systems are how small teams ship at a size they shouldn't be able to.
Add a short quote here about how the design handoff went — the more specific, the more it lands.
Add a second quote here — ideally one that mentions a result, a deadline met, or a problem solved.
Add a third quote here — a client or teammate describing what working with you was like day to day.
The top design honour of the internship, awarded for leading UI/UX on the main project: wireframes, component library and design system.
Certificate covering campaign strategy, on-page optimisation and web design fundamentals.
Certificate in interface and experience design workflows in Figma — components, prototyping and handoff.
Certificate following a four-month intensive online course in frontend development.
Full-time or part-time UI/UX and graphic design roles, remote or based in Nepal. I'm currently working remotely with a US agency, so I'm comfortable across time zones. Freelance project work runs through Codexdesign.
Both, depending on what you need. I design in Figma and can build the live site in WordPress and Elementor, or write the HTML, CSS and Tailwind directly. If you have developers, I hand off files with named layers, defined states and the responsive behaviour already decided.
A conversation about what the page or product needs to do, and what would count as it working. Then wireframes — always before visual design, so we're arguing about structure while it's cheap to change.
Yes — keyword research, page titles, headings, content structure, and setup in Google Analytics and Search Console. I do this at Pinned Agency and did it for Navigate®, so it's part of how I think about page structure, not a bolt-on afterwards.
Yes. Logo marks, visual identity and social content design. I approach marks practically — most of them spend their life at profile-picture size, so legibility small comes before cleverness large.
Email is fastest — hellokaushalsroy@gmail.com. WhatsApp or a call on +977 9828332275 also works, and I'm reachable on Instagram at @kaushalsroy. I'm on Nepal time, UTC+5:45.
worth using
Birgunj, Nepal
Local time —:—