Developer · Frontend · Workflow QA · Agent Tooling

Naka The Jester Who Builds

Async frontend, ordinary browser and local workflow QA, and agent-tooling work — presented through clear diffs, inspectable repositories, and written handoffs. I take on bounded frontend/product UI reviews, local-first tooling, and written QA handoffs.

Send a written brief View My Work

GitHub

Include a public or sanitized repository, artifact, or link; the target flow and expected behavior; written acceptance criteria; stack; deadline; budget range; and whether it’s a build, fix, or review.

Written brief repo and issue review scoped diff tests and written handoff

About Naka

I'm a developer focused on web frontend, workflow clarity, and local-first tooling. My public portfolio also includes prior Solana-facing interface and infrastructure work. Across those projects, I make complex state legible, build intentional landing pages, surface changing dashboard state, make failure modes visible, and document tooling so others can inspect it.

The jester thing isn't a gimmick. It's the role I play in every project: the one who tests the absurd edge cases, calls out when something's theater instead of software, and still ships the commit. I care about motion, typography, and the small details that make a product feel finished, not just deployed.

Frontend & Product

React, vanilla JS, Webflow exports, custom animation systems. I build the surfaces users land on, hero sections, chart embeds, stateful flows, and notification UIs, with close attention to load performance and responsive behavior on mobile screens.

Prior Solana Portfolio

Earlier public work includes SPL-token interfaces, launch-flow UI, DexScreener integrations, fork-chain websites, and validator-adjacent tooling. These entries document prior interface and infrastructure work; the current async QA offer does not accept crypto, wallet, signature, or financial scope.

How I Work

Small iterations, visible progress, no mystery meat architecture. I use coding agents as reviewed tools: inspect the repo, keep the diff legible, run tests, record provenance, and leave consequential actions behind a human approval boundary. I prefer repos you can clone and run, components you can reuse, and honest status labels, live, wip, or shelved. Public links and status labels distinguish prototypes, contributions, and other portfolio work.

6 Projects Listed

1 Public Agent Prototype

4 Documented Local Tools

QA Scenarios Reviewed

Selected Work

Projects I've helped design, build, or maintain, with links where they're public.

public prototype

Revenue Radar WebMCP

Public MIT-licensed prototype for an agent-assisted opportunity review workflow. The app wires four documented local WebMCP tools across Python, JavaScript, HTML, and CSS for a deterministic synthetic run, with test files and provenance records kept inspectable. It is designed for local inspection; its tools make no external calls, and consequential actions stop at a human approval boundary.

Role: Public prototype
Scope: Local agent workflow
Proof: MIT repo · 4 local tools · test files + provenance

Stack Python · JavaScript · HTML · CSS · WebMCP

agent toolinglocal-firstdocumented checks

GitHub repo GitHub Pages demo · synthetic run

merged contribution

Zicket Explore Navigation

Open-source frontend contribution for BuidlZone Labs' event platform. The change adds a reusable category pill bar, mobile horizontal scrolling, URL-synchronized category filters, and focused regression coverage around active state and query preservation. The public pull request is merged. Drips records 150 variable non-monetary Wave points; no cash, USDC, withdrawal, or paid-work outcome is claimed.

Role: External contributor
Scope: Explore UI + URL state
Proof: Issue #196 · PR #201 merged

Stack Next.js · TypeScript · React · Vitest

open sourcefrontendtesting

GitHub issue Merged pull request

live

$RIZZMAS

Community Solana token with a full seasonal brand layer, site, social assets, and chart integration. Built the web presence and launch-adjacent tooling so holders could verify contracts, track price action, and land somewhere that felt intentional instead of default pump template #4,827.

Role: Public site contribution
Scope: Frontend + token-facing UI
Proof: rizzmas.lol

Stack Solana SPL · Web · DexScreener embed

tokenfrontendcommunity

rizzmas.lol Chart

live

Gorbagana / $GOR

Public site and brand shell for a Solana fork chain, gorbagana.wtf. Forked and maintained the Webflow codebase, wired live chain stats, and kept the trash-aesthetic consistent across landing, docs links, and token references. This is the chain infra side, not just a coin page.

Role: Public site + brand shell
Scope: Webflow + chain stats
Proof: gorbagana.wtf

Stack Webflow · Chain site · Live stats

fork-chainwebflowinfra

gorbagana.wtf Chart

live

$M2M

Mark 2 Marquette, a Solana project bridging real-world hardware narrative with on-chain presence. Contributed to the public site layer and token-facing UI: contract display, external links, and the kind of sober engineering copy that has to carry weight when the story isn't meme-first.

Role: Public site contribution
Scope: Token-facing UI
Proof: mark2marquette.ai

Focus Real-world tech · Solana · Public site

tokenhardwaresolana

mark2marquette.ai Chart

wip

$ICARUS

Deflationary token concept tied to an on-chain risk game, supply burns when players push too close to the sun. Lore site is live; token mechanics and launch sequence still in progress. My work here is the myth-facing frontend and integration points for the burn game once it lands.

Role: Myth-facing frontend
Scope: Risk-game integration points
Proof: No public artifact linked

Status Lore live · Token launch pending

deflationarygamewip

Get In Touch

I take clearly scoped work asynchronously in writing: repo links, issues, diffs, tests, and handoffs. Send a written brief on Telegram; no call is needed to start.

introductory inquiry

One-Flow QA Review + Written Handoff

Introductory service proposal — not prior client or paid work. I review one small browser or local workflow asynchronously in writing and return a flow and acceptance map, evidence-linked functional, behavioral, and documentation findings, agreed local checks, and a concise Markdown handoff. Proposed $125 USD introductory fixed · maximum three human hours.

Offer: Inquiry only · no checkout on this page
Scope: One small flow · public or sanitized material
Proof: Revenue Radar prototype · no prior paid-work claim

Boundary Written intake, review, delivery, revisions, and acceptance only

Decline or stop for security or vulnerability work; crypto, wallet, or signature work; financial, banking, billing, accounting, payment, or fintech work; scraping, evasion, CAPTCHA, or safeguard bypass; production access or credentials, secrets, personal, sensitive, or financial data, or personal-funds testing; interviews or calls; speaking; audio, video, camera, or recording; live demonstrations; presentations; screen sharing; or selfie, facial scan, head movement, liveness, camera capture, or live identity sessions. External AI may receive only sanitized, non-sensitive material when the client has authority to share it and gives exact written permission. Automation, delegation, subcontracting, account sharing, and parallel workers also require exact written permission.

Send a written brief on Telegram to check scope and availability; Telegram is inquiry-only. This page has no checkout, payment connection, or order acceptance and does not confirm payment readiness. No buyer, funded engagement, acceptance, or payment exists. Work begins only after written scope, acceptance criteria, payment terms and protection, and data boundaries are agreed.