uses
This is the stack and setup behind how I build across web, app, interface, and systems-oriented work. It is less about listing tools and more about showing how the pieces fit together when turning ideas into polished builds.
core stack
These are the primary layers of the current workflow. Instead of treating them as isolated tool lists, this section shows them as a connected system that supports building, shipping, and refining.
HTML
languageBase structure for web pages, content hierarchy, and semantic layout.
CSS
uiCore styling layer for layout, spacing, responsiveness, and visual presentation.
JavaScript
languageCore language for browser logic, interactivity, and full-stack JavaScript workflows.
Next.js
frameworkMain web framework used for the portfolio and full-stack product interfaces.
React
frameworkComponent-driven UI library behind much of the interactive frontend work.
Tailwind
uiUtility-first styling system for building polished interfaces quickly and consistently.
React Native
frameworkCross-platform mobile app framework for product, app, and interface experiments.
Expo
frameworkDevelopment layer that speeds up React Native workflows and iteration.
Swift
languageUsed for native Apple-side experimentation and app/game-oriented work.
Node.js
backendJavaScript runtime used for backend logic, tooling, and full-stack workflows.
Supabase
backendBackend layer for auth, database, storage, and modern app services.
PostgreSQL
backendRelational database layer behind structured application data.
Docker
infraContainerization for consistent environments, services, and deployments.
Kubernetes
infraOrchestration layer for deeper infra-oriented deployment work.
setup philosophy
I prefer tools that support both experimentation and refinement. The ideal setup is one that makes it easier to build strong systems, shape better interfaces, and keep momentum without sacrificing quality.
The goal is not to use more tools. It is to make the tools feel like they belong to one coherent workflow.
current setup signals
priority
Tools that help turn ideas into structured, polished systems.
balance
Enough flexibility for experiments, enough stability for deeper builds.
outcome
A workflow that supports product thinking, UI polish, and technical depth together.
visual systems map
This graph turns the setup into a spatial map using the actual Uses data. As the content grows, the graph grows with it.
stack graph
This graph is generated from the actual Uses content, so it grows as the setup grows.
more tools
TypeScript
languageShared typed language across frontend, app, backend, and UI logic.
Git
systemVersion control foundation for maintaining code history and collaborative workflows.
GitHub
systemCode hosting, collaboration, and project versioning platform.
Terminal UX
systemTerminal-first interaction layer and workspace concept behind this portfolio.
UI/UX Design
uiInterface thinking around hierarchy, clarity, flow, and interaction polish.
Framer Motion
uiAnimation layer for smooth, expressive, and polished UI interactions.
Figma
uiTool for layout planning, UI exploration, and visual system thinking.
VS Code
systemPrimary general-purpose code editor for development and iteration.
Xcode
systemApple development environment used for native app and Swift work.
Neovim
systemKeyboard-driven editing environment and workflow experimentation.
DevOps
infraWorkflow mindset around deployment, automation, consistency, and shipping systems properly.
CI/CD
infraAutomation pipeline thinking for testing, integration, and deployment workflows.
Game Dev
systemExperimental area combining systems design, interaction, performance, and creative problem solving.
Content / Writing
systemWriting and articulation layer for documenting process, ideas, and learnings.