Portfolio 2026 Open to work

Malik Adesiyan

maleekskies

full stack developer

Ask my assistant
Scroll to explore Nigeria · remote
Open to Development & Automation Roles
Full Stack Development · AI Automation

Ideas become products. Products become stories.

I build full stack web apps. I also automate business workflows with AI.

0+
Ecosystems
contributed to
0K+
Followers
on X
0+
Projects
built
0
Core service
lines
Ecosystems I've contributed to
About

Clarity is the product.

I'm Malik Adesiyan, and I build for the web. I take an idea from a blank page to a working product: the interface, the backend, the database, and the small details that make it feel finished. I've shipped more than 15 sites and PWAs for clients in different countries, and I still like the part where something finally works.

I also build AI automation. I use n8n to connect the forms, spreadsheets, inboxes, and chat apps a business already uses, so routine work like lead capture, replies, alerts, and follow-ups happens without someone remembering to do it. I can run it with a cloud model, a local model, or no AI at all, whichever you prefer.

Full Stack Development AI Automation
Malik Adesiyan, full stack developer and automation builder
Highlights

Featured projects.

A selection from a larger body of work. There's more behind these.

Key Benefits

Full Stack
Built End to End

From first commit to live link: clean front ends, solid back ends and the deployment work in between, so the product ships and stays up.

AI Automation
That Saves Hours

Built, Documented
and Dependable

Every build ships with clear notes and a setup that is easy to maintain.

My Toolkit

Tools I Use

Technologies and tools I use in building products.

Frontend Development

Building responsive and interactive user interfaces.

React Next.js HTML5 CSS3 JavaScript TypeScript Vite Tailwind CSS

AI Automation

Connecting forms, spreadsheets, messaging, and AI into workflows that run on their own.

n8n Ollama Webhooks Docker

Backend & Database

Building APIs and working with databases and server-side logic.

Node.js Python FastAPI Supabase

Tools & Design

Tools I use to design, build, and ship projects.

Git GitHub Vercel Figma Canva VS Code
What Drives Me

Why I do this work.

01

Builder's Instinct

I'd rather ship something small than keep polishing something that never goes out.

02

Clear Communicator

An idea nobody can follow hasn't helped anyone yet.

03

Curious by Default

I learn a new tool by using it, not by reading about it first.

04

Practical Problem Solver

The right fix is the one that works for the person using it, not the most impressive one.

Contact

Tell me what you're building.

Full stack development or AI automation. Send a short note about what you need and I'll reply.

Email me View CV

Based in Nigeria. Working remotely with clients worldwide.

Got a project in mind? Ask my assistant about my work, or tell it what you want to automate.

2026 Open to work · remote full stack · ai automation
← Back to portfolio
My Work

AI Automation

Automations that keep running without me.

← Back to portfolio
Case study

RoleSearchHQ

A job search workspace that finds roles, scores them against your CV, and builds the application kit.

Full Stack · AI-Powered Job Search

RoleSearchHQ: Scan, Score and Prepare From One Place

RoleSearchHQ scans multiple job boards, scores each role against a user's CV with a hybrid keyword and LLM engine, and turns the roles worth pursuing into tailored kits. Each kit can include a CV, cover letter, form packet, talking points, and notes on the gaps to address.

  1. Job boardsRoles scanned
  2. Keyword engineFast first pass
  3. LLM (Groq)Deeper match check
  4. TodayRoles above the bar
  5. PipelineSaved roles and stages
  6. Kit StudioOne kit per role
Keywords narrow it downThe LLM judges the fit
RoleSearchHQ pipeline with saved roles, ready kits, and a score on each card
Pipeline: saved roles, ready kits, and conversations in motion
RoleSearchHQ Kit Studio with a list of tailored kits ready for review
Kit Studio: one tailored kit per role, waiting for review

The problem

Job hunting means checking several boards, reading long descriptions, and guessing which roles actually fit. Then each application needs its own CV, cover letter, and answers, which is a second job on its own.

The solution

One workspace gathers roles, ranks them against the user's CV and preferences, and explains each match. The roles that clear the bar move into a pipeline, and Kit Studio drafts the application material from the user's own CV, voice guide, and proof points.

How it works

  1. Scan. Roles are collected from multiple job boards into one pool.
  2. Score. A hybrid engine combines keyword matching with an LLM, so the score reflects exact skills and overall fit.
  3. Review. Today shows the roles above the score threshold. Each job opens with a match breakdown and the gaps to address.
  4. Track. Saved roles move through Pipeline stages, from saved and ready to send, to applied, to interview.
  5. Prepare. Kit Studio drafts a CV, cover letter, form packet, talking points, and gap notes for one role. The user can edit the kit and approve it. Nothing is sent from RoleSearchHQ; approval means the kit is ready for the final send.

Engineering highlights

Hybrid scoring

Keywords give a fast first pass and the LLM adds judgement, so results are not just word counts.

Explained matches

Each score comes with a breakdown and a list of gaps, so the user knows what to fix.

Per-role kits

Every application gets its own CV and cover letter instead of one generic copy.

One source of truth

Kits are pulled from the saved CV, voice guide, and proof points, not rebuilt from scratch each time.

Approval gate

Drafts stay in the workspace until the user approves them. The app does not send applications on its own.

Pipeline view

Every saved role keeps its stage, kit status, follow-up date, and interview notes in one place.

Built with

Next.jsSupabaseGroq@react-pdf/rendererpdf-parseResendVercel
← Back to portfolio
Case study

ChessHatch

A chess platform that teaches from the first move and grows with the player.

Full Stack · Chess Learning Platform

ChessHatch: Learn, Practise and Play in One Place

ChessHatch is a learning-first chess platform. Lessons start from zero and build to 50 tactics lessons, a rule-based live coach explains moves, multiplayer is real time with Glicko-2 ratings, and Stockfish runs offline with nine bot levels that unlock as you win.

  1. LessonsFrom zero
  2. Tactics10 series, 50 lessons
  3. Live coachRule-based hints
  4. Bots9 levels, Stockfish
  5. MultiplayerGlicko-2 ratings
Coach rules run in code
Beginner lesson path
Beginner lesson path
Intermediate tactics: 10 series, 50 lessons
Intermediate tactics: 10 series, 50 lessons
Nine bot levels with progression
Nine bot levels with progression

The problem

Many chess sites assume you already know the game. Beginners are dropped into matches or a wall of puzzles with no clear path from the basics to real tactics.

The solution

A structured path: beginner lessons, then tactics in ten series, then bots and live opponents. The coach explains what is happening on the board, so practice teaches something.

How it works

  1. Learn. Beginner lessons start from zero and build step by step.
  2. Train. Intermediate tactics are grouped into 10 series with 50 lessons in total.
  3. Get coached. A rule-based live coach comments on the position as you play.
  4. Play. Face one of nine Stockfish bot levels, which unlock as you win. Bot play works offline.
  5. Compete. Real-time multiplayer uses Glicko-2 ratings to match and rank players.

Engineering highlights

Offline computer play

Stockfish.js runs in the browser, so bot games work without a connection.

Real-time multiplayer

Live games with Glicko-2 ratings, which handle new and returning players more fairly than simple Elo.

Unlockable progression

Bot levels open as you win, which gives players a reason to keep going.

Built with

ReactViteSupabasechess.jsStockfish.jsVercel
← Back to portfolio
Case study

VAULT 01

A Genesis Collection mint where the identity rule lives in the contract.

Full Stack · Web3 · NFT Mint

VAULT 01: A Mint With the Identity Check in the Contract

VAULT 01 is the mint site for the Genesis Collection on Redbelly Network Mainnet. The contract enforces wallet identity verification, and 50 of the 500 tokens are tied to limited-edition mechanical watches that the holder can claim on-chain.

  1. WalletConnect to the site
  2. Contract checkIdentity rule
  3. MintOne of 500
  4. RedbellyMainnet
  5. Watch tokens50 of 500
  6. ClaimOn-chain
VAULT 01 Genesis Collection mint page
Genesis Collection mint page
Watch previews for Onyx, Rose, Green, and Steel
Watch previews: Onyx, Rose, Green, Steel

The problem

A mint page can hide the button when a wallet does not qualify, but that does not stop someone from calling the contract directly. VAULT 01 needed the identity rule to live in the contract, not only in the interface.

The solution

The contract checks wallet identity before it allows a mint. The collection is capped at 500 tokens, and 50 of them are bound to physical watches that the holder claims on-chain. The site handles the wallet connection and shows the collection.

How it works

  1. Connect. A wallet connects to the mint site on Redbelly Network Mainnet.
  2. Verify. The contract checks the wallet's identity status before it allows a mint.
  3. Mint. A qualifying wallet mints from the 500-token Genesis Collection.
  4. Claim. Fifty tokens are bound to limited-edition mechanical watches. The holder claims the watch on-chain.
  5. View. The site shows the collection and the watch previews before the wallet connects.

Engineering highlights

Contract-level gate

The identity check runs in Solidity, so the browser is not the only thing standing between a wallet and the mint.

Fixed supply

The Genesis Collection is capped at 500 tokens.

Physical claim

Fifty tokens carry a watch claim that is settled on-chain.

Typed frontend

Next.js and TypeScript handle the page, with wagmi for wallet state.

Foundry build

The Solidity contracts are built with Foundry.

Built with

Next.jsTypeScriptSolidityFoundrywagmiTailwind CSSVercel
← Back to portfolio
Case study

OZ Handcrafted Footwear

A storefront for a handmade footwear label, with WhatsApp as the checkout.

Full Stack · Brand & E-Commerce

OZ Handcrafted Footwear: A Storefront Built Around WhatsApp

OZ Handcrafted Footwear is a brand storefront for a handmade footwear business. It has a product catalogue, photo galleries, search and filters, a cart, and a wishlist. Checkout hands the shopper to WhatsApp, so the site needs no backend, payment integration, or customer accounts.

  1. HomeBrand and featured pairs
  2. CollectionSearch and filters
  3. ProductColour, size, gallery
  4. CartPairs to order
  5. WishlistSave for later
  6. WhatsAppFinish the order
OZ Handcrafted Footwear home page
Home page: handcrafted for a perfect fit
OZ featured collection with search and filters
Featured collection with search and filters
OZ product page with colour, size, and WhatsApp order
Product page: colour, size, and WhatsApp order

The problem

A small handmade brand needs a product catalogue that looks good on a phone, but a full ecommerce backend adds hosting, payments, and maintenance. The owner already takes orders in WhatsApp conversations.

The solution

A static storefront that shows the collection and product details, lets shoppers save pairs, and then hands the order to WhatsApp. There is no database, no payment form, and no account to create.

How it works

  1. Browse. The home page introduces the brand and shows featured pairs.
  2. Find. The collection page uses search and filters to narrow the catalogue.
  3. Choose. The product page shows the colour, size, and photo gallery.
  4. Save. Shoppers add pairs to the cart or the wishlist.
  5. Order. Checkout hands the shopper to WhatsApp to finish the order.

Engineering highlights

No backend

The catalogue, cart, and wishlist run in the browser, so there is no server or database to maintain.

Product-first pages

Photo galleries and colour and size details sit above the order handoff.

Two ways to save

Shoppers can build a cart for a planned order or keep a wishlist for later.

WhatsApp checkout

The order leaves the site as a WhatsApp conversation, which is where the owner already works.

Built with

HTML5Tailwind CSSJavaScriptVercel
← Back to portfolio
Case study

Redbelly Onboarding Hub

One page for the questions every new Redbelly Discord member asks.

Full Stack · Community Onboarding

Redbelly Onboarding Hub: One Link for New Members

A static reference page for new Redbelly Discord members. It answers the common questions about KYC, network setup, the "$0 balance" confusion, where to trade, staking, and the testnet faucet. A scam warning sits at the top.

  1. New memberOpens the hub
  2. Scam warningBefore anything else
  3. KYCWhat it is for
  4. Network setupMainnet and testnet
  5. Zero balanceWhy it looks empty
  6. Trade, stake, faucetNext steps
Redbelly onboarding hub hero with the scam warning
Hero and scam warning

The problem

New members arrive in Discord with the same questions: what KYC is, how to set up the network, why the balance looks empty, where to trade, how staking works, and where the testnet faucet is. Repeating those answers in chat takes moderator time, and the answers get lost in the scroll.

The solution

One static page with a section for each question and a scam warning at the top. Moderators can send the same link instead of retyping the answers, and new members can read at their own pace.

How it works

  1. Open. A new member opens the hub from a link in Discord.
  2. Read the warning. The top block says every DM is a scam and that staff, support, and giveaways never message first.
  3. Find a section. KYC, network setup, zero balance, buy and trade, staking, and the testnet faucet each have their own section.
  4. Follow the steps. Each section answers one question without sending the reader to another chat.
  5. Share. Moderators send the same link the next time the question comes up.

Engineering highlights

One URL

A single page covers the questions new members ask most.

Scam warning first

The page tells members that staff, support, and giveaways never DM first.

No backend

Static HTML and CSS, so the page loads fast and needs no database.

Simple to update

Content changes are text edits in the page.

What it changed

  • New members get the same answers in one place.
  • Moderators can link to the page instead of retyping the same reply.
  • The scam warning is seen before any trading or wallet advice.

Built with

HTML5CSS3Vercel
← Back to portfolio
Case study

Redbelly Onboarding Hub v2

A rebuild of the onboarding hub, with quick links to the answers people need.

Full Stack · Community Onboarding

Redbelly Onboarding Hub v2: Quick Links for Faster Answers

A rebuild of the Redbelly onboarding hub with quick links under the scam warning. A new member can jump straight to KYC, network setup, zero balance, buy and trade, staking, or the testnet faucet.

  1. New memberOpens the hub
  2. Scam warningBefore anything else
  3. Quick linksJump to a topic
  4. KYCWhat it is for
  5. Network setupMainnet and testnet
  6. Trade, stake, faucetNext steps
Redbelly onboarding hub v2 with the scam warning and quick links
Hero, scam warning, and quick links

The problem

The first hub answered the questions, but a new member still had to scroll through the page to find the one they needed. The answers were there, but there was no shortcut to each section.

The solution

A rebuild with a row of quick links under the scam warning. KYC, network setup, zero balance, buy and trade, staking, and the testnet faucet each jump to their section, while the warning stays at the top.

How it works

  1. Open. A new member opens the hub from a link in Discord.
  2. Read the warning. The scam warning is still the first block after the hero.
  3. Pick a shortcut. The quick links jump to KYC, network setup, zero balance, buy and trade, staking, or the testnet faucet.
  4. Read the answer. Each section stays short and covers one question.
  5. Share. Moderators send the same link the next time the question comes up.

Engineering highlights

Quick navigation

One tap moves a new member from the top of the page to the section they need.

Same trusted answers

The rebuild keeps the KYC, network, balance, trading, staking, and faucet content from the first hub.

Scam warning stays visible

The warning sits above the quick links, so the safety message is not hidden behind a shortcut.

Still static

No backend or database, so the page stays fast and cheap to host.

Built with

HTML5CSS3Vercel
← Back to portfolio
Case study

Auditlynx

A defensive security dashboard with five checks for a fast first pass.

Full Stack · Security Tooling

Auditlynx: Five Security Checks in One Dashboard

Auditlynx is a defensive security toolkit with five modules: security header grading, a phishing analyzer, DNS and domain recon, a code security scanner, and a breach checker. It is built for heuristic triage, so a human analyst can decide what needs a closer look.

  1. Choose moduleOne of five checks
  2. Enter targetDomain, email, or code
  3. Run checkHeuristic scan
  4. Read resultGrade or findings
  5. ReviewWhat stands out
  6. VerifyManual follow-up
Auditlynx module 01, the security headers and config checker
Module 01: Security Headers & Config Checker
The five Auditlynx analysis modules
The five analysis modules

The problem

A first security pass is spread across browser tools, DNS lookups, code scanners, and breach checks. An analyst needs a quick read on several signals without opening five different tools or writing the same notes twice.

The solution

A dashboard with five modules in one place. Each module runs a focused check and returns a grade or a list of findings. The tool is for triage, not a replacement for a full audit, so the results point to what a human should verify.

How it works

  1. Pick. Choose one of the five modules from the sidebar.
  2. Enter the target. The module asks for a domain, email, URL, or code, depending on the check.
  3. Run. The backend runs the check and returns a grade or a set of findings.
  4. Read. The result shows what stands out, without mixing it with the other modules.
  5. Verify. The analyst checks the finding manually before acting on it.

Engineering highlights

Five focused modules

Headers, phishing, DNS and domain recon, code security, and breaches each have their own screen.

Stateless checks

The tool runs a check and returns a result. There is no account or scan history to manage.

Triage first

The results are heuristic. The interface says to verify findings manually, so the tool does not pretend to replace a full audit.

Clear input per module

Each module asks for the target it can actually use, so the user does not have to guess.

Fast frontend

React and Vite keep the module switching and results light.

Built with

PythonFastAPIReactViteTailwind CSSVercel
← Back to portfolio
Case study

UrPassport NG

A travel dashboard for Nigerians, from passport application to boarding gate.

Full Stack · Travel & Immigration · In Progress

UrPassport NG: One Dashboard From Application to Boarding

UrPassport NG is a full-stack dashboard for Nigerians planning a trip. It brings passport application tracking, visa document checklists for the UK, US, Canada, and UAE, an AI trip planner, Naira flight search, and encrypted document storage into one account.

  1. Sign inOne account
  2. PassportTrack the application
  3. Visa checklistsUK, US, Canada, UAE
  4. Trip plannerBuild the itinerary
  5. FlightsPrices in Naira
  6. DocumentsEncrypted storage
UrPassport NG landing page for passport, visa, flight, and document tracking
Landing page: one account for the whole trip

The problem

A Nigerian traveler juggles a passport application, visa checklists for different countries, flight prices in another currency, and a folder of documents. The information is spread across government portals, tabs, and paper, so it is hard to see what is done and what is next.

The solution

One dashboard that groups the trip: passport tracking, country-specific visa checklists, an AI trip planner, Naira flight search, and encrypted document storage behind real authentication. The build is in progress, with the core flow in place.

How it works

  1. Sign in. The user creates an account and signs in.
  2. Track the passport. The passport section keeps the application status and next steps in one place.
  3. Prepare the visa. Choose the UK, US, Canada, or UAE and work through that country's document checklist.
  4. Plan the trip. The AI trip planner turns the destination and dates into an itinerary.
  5. Compare flights. Flight search shows prices in Naira.
  6. Store documents. Travel documents are encrypted and kept behind authentication.

Engineering highlights

One account

Passport, visa, flights, and documents sit behind one login.

Country-specific checklists

The UK, US, Canada, and UAE each have their own visa document list.

Naira-first flight search

Flight prices are shown in Naira, not converted at the last step.

Encrypted documents

Travel documents are encrypted and kept behind authentication.

AI trip planner

The planner builds an itinerary from the trip details instead of starting from a blank page.

Built with

Next.jsTypeScriptTailwind CSSSupabaseVercel
← Back to portfolio
Case study

TravelSleek

A scholarship and work visa tracker that reads the deadline for you.

Full Stack · Opportunity Tracker · Completed

TravelSleek: A Tracker That Reads the Deadline for You

TravelSleek is a scholarship and work visa tracker. It pulls listings from GOV.UK and IRCC Open Data, parses PDFs, and adds curated programs like DAAD, Chevening, Fulbright, Erasmus Mundus, Commonwealth, and Gates Cambridge. Each listing gets a score, tags, and a countdown to its deadline.

  1. Live sourcesGOV.UK and IRCC
  2. PDF parsingRead the documents
  3. Curated programsSix major schemes
  4. Score and tagsSort the list
  5. InboxScholarships and visas
  6. CountdownDays left
TravelSleek inbox with scholarship scores, tags, and deadline countdowns
Inbox: scores, tags, and days left

The problem

Scholarship and visa deadlines are spread across government pages, university PDFs, and program sites. A list that is not updated is worse than no list, because it hides expired opportunities and buries the ones that are still open.

The solution

The app pulls live sources, parses PDFs, and adds curated programs. It scores and tags each listing, shows the days left, and archives listings that have not been touched in 30 days. Nothing is submitted automatically; the app tracks, and the user applies.

How it works

  1. Sync. The app pulls from GOV.UK and IRCC Open Data, and adds curated programs such as DAAD, Chevening, Fulbright, Erasmus Mundus, Commonwealth, and Gates Cambridge.
  2. Parse. PDFs are parsed into structured listings, so the deadline and eligibility details are not trapped in a document.
  3. Score. Each opportunity gets a score and tags such as fully funded or multi-country mobility.
  4. Review. The Inbox separates scholarships and work visas, and the list can be sorted by score.
  5. Watch the clock. Each row shows the days left before the deadline.
  6. Archive. Untouched listings auto-archive after 30 days. Nothing here submits itself.

Engineering highlights

Live plus curated

Government sources and a hand-picked program list meet in one feed.

Deadline first

The days-left label makes urgency visible before the user opens a listing.

Scored and tagged

A score and tags give the list an order, and the Inbox can sort by score.

No auto-apply

The app tracks opportunities. It does not submit applications on the user's behalf.

Stale listings leave

Listings untouched for 30 days archive themselves, so the Inbox does not fill with dead links.

Built with

ReactViteSupabasepdf-parseVercel
← Back to portfolio
My Work

Full Stack Development

Products and client sites, from first commit to live link.