Multidisciplinary designer. Lagos, Nigeria.
I'm a Multidisciplinary designer with six years across brand identity, motion, 3D, UI/UX, and front-end development. I don't hand off. I design a system, write the code, and ship it.
Right now I'm Principal Designer at Parable VC in Dubai, taking on client work in parallel, and quietly building a design agency called Layout Studio.
A token-driven design system built for AG Mortgage Bank Plc, a CBN-licensed Nigerian Primary Mortgage Institution. Built in Next.js. Documented and surfaced at /design.
A full rebuild of Systemspec Technology Solutions as three deliverables in one monorepo: marketing site, design system, and UI kit. The design system lives inside the marketing site at /design/
Public marketing site for AG Mortgage Bank Plc. Twelve pages: home, mortgage products, calculator, about, insights, contact, and application start. Built with Eleventy 3.1.5 and GSAP ScrollTrigger for line-by-line heading entrances and scroll-reveal sections.
Marketing site for Pacific Blue, an Australian renewable energy company. The turbine section locks sticky below the header as you scroll through content phases.
A dark-first productivity dashboard modelled on a bento grid layout. Eight modules: inbox, job board aggregator with Google X-Ray ATS search, Pomodoro focus timer, news feeds, networking leads tracker, calendar, cold email composer, and activity log. Single-page HTML/CSS/JS.
Landing page concept for Synexis, a Decentralized Science project. Built in HTML, exploring how DeSci infrastructure might be communicated to an audience that isn't already in the space.
A front-end build in HTML. In progress.
Holding portfolio site while the main one is rebuilt. CSS-driven layout.
A build log for the STSL marketing site rebuild. Covers how a multi-agent Claude workflow handled the heavy lifting, and the sequence of bugs that surfaced once real users hit the live build. The honest version of shipping a quietly modern site for an audience that doesn't want to be marketed to.
Design and code are the same conversation for me. When I spec a component, I'm already thinking about how it renders. When I write CSS, I'm making design decisions. Keeping those two tracks separate adds lag, misses context, and produces worse work on both sides.
Brand identity is a system problem before it's an aesthetic problem. The question isn't what looks good. It's what holds together at scale: across applications, screen sizes, production constraints, and people who weren't in the original brief. I work out the rules first and let the visuals follow from them.
For early-stage clients, the designer-developer combination matters because there's no margin for miscommunication. A startup can't afford a two-week loop between spec and implementation for every component. When one person holds the full picture, decisions are faster and the output is more coherent.
The agentic question is the one I'm sitting with right now. If AI can handle execution reliably at the component and layout level, what does the senior designer's job actually become? My answer: the thing AI can't own is the judgment call about what the client needs versus what they asked for, the read on whether a brand direction is going to age badly, and the relationship that makes honest feedback possible. That's where I want to spend my time.
| Design | Development |
|---|---|
| Figma, Paper, Claude.design | HTML, CSS, JavaScript |
| After Effects, Lottie, Blender | Three.js, Canvas API, Matter.js |
| Premiere Pro | TypeScript, React (in progress) |
| Adobe Creative Suite | Claude Code, Lovable |
I started in design and got pulled toward code because I kept running into things I wanted to build that no developer was going to prioritise. Six years later the split is roughly 60/40: design direction and systems thinking on one side, front-end implementation on the other. The curiosity that drives the work is broader than either. I read across art, science, maths, finance, biology, and history, and that range shows up in the work. Different domains borrow from each other constantly. The best design decisions I've made came from thinking that started somewhere else entirely. Now I'm founding Layout Studio, which is the thing I want to build long enough to have an opinion about.
- Three.js: scenes, GLB pipelines, scroll-driven animation
- React: moving from vanilla JS toward component-driven front-end work
- Blender scripting: Python automation for 3D pipeline tasks
- Agentic studio structure: what a creative studio looks like when AI owns execution (team model, pricing, client relationships)
- AGMB design system: extending token coverage and pattern library
- artbyade.com
- Open to: freelance, full-time remote (UK, UAE, global tech), Web3 design and brand collaborations


