Web experiences
Responsive sites with strong hierarchy, expressive motion, and content that remains easy to find.
Development / Web & Systems
Make the idea
click.
Web experiences, prototypes, and small digital systems where the interface, the story, and the handoff all agree.
// one portfolio, three perspectives const experience = choose({ desktop: "V0 / Vanilla", mobile: "V1 / Classic", curious: "V2 / SIGNAL" }); ship(experience, { routes: 22, qa: "continuous", handoff: "documented" });
// different minds, one reviewed outcome delegate([ "Codex", "Claude", "ZCode", "Goose", "Hermes" ]); observe(); compare(); humanReview(true);
// context is useful when provenance survives capture(session); trace(decision); verify(destination); return { canon: "preserved", state: "recoverable" };
Build the right
kind of useful.
The stack changes with the problem. The standard stays the same: clear structure, responsive behavior, and a path for the next person to keep going.
Prototypes
Clickable experiments that make a direction tangible while there is still time to change it.
AI-assisted systems
Purpose-built workflows where models help with the work without becoming the whole story.
CMS & handoff
Organized content, documented decisions, and a launch path that does not strand the next person.
Systems you can touch
Proof lives
in the interaction.
These are not mockups. They are different working views into the same evolving portfolio.
A working constellation
More than one way
to make a page sing.
This is a working set used across design, development, AI collaboration, orchestration, and delivery—not a shelf of certifications.
Languages + browser
HTML / CSSJavaScriptTypeScriptPythonPHPRubyRustReactThree.jsViteBabelLenisTailwind CSSFramer MotionNode.js
AI collaborators
ClaudeCodexZCodeDeepSeekGooseHermesGeminiZ.aiOpenAIAnthropicOpenRouterOllamallama.cppvLLMUnslothAGY / Antigravity
Systems + delivery
WordPressBreakdanceBase44WebflowShopifyGit / GitHubDockern8nSupabaseSQLite / PostgresMCPMemtraceherdrBrowser HarnessChrome DevToolsFigmaOpenClawBodhiruNAS
From brief to browser
The system should support
the feeling.
01
FrameDefine the audience, the job, and the feeling.
02
PrototypePut the idea on screen early enough to change it.
03
BuildMake the visual language and the underlying system agree.
04
Stress-testCheck the edges: small phones, motion, accessibility, and handoff.
05
ShipRelease a useful thing with a way back and a path forward.
The next screen
Have something that should
exist on the internet?
Bring the sketch, the broken link, or the sentence you cannot stop thinking about.