Stack

The tools I use to build, review, measure, and publish software.

Coding agents

Name Description
Claude Code The coding agent I use for specifications, reviews, and long repository investigations.
Codex The coding agent I use for bounded construction work from a written brief.
GitHub Copilot CLI A coding agent I can run from the terminal for repository work.
Gemini CLI A terminal coding agent available in my multi-agent workspace.
Cursor The editor I use when repository work needs the code, terminal, and browser in one place.
opencode An open coding agent I run from the terminal.
aider A terminal coding agent I keep available for repository changes.
goose An open coding agent available in my terminal workspace.
Amp A coding agent I use from the terminal alongside other agents.
Crush A terminal coding agent in my installed agent set.
Factory Droid A software-development agent available in my coding workspace.
Kimi CLI A terminal coding agent available for delegated repository work.
Pi A small terminal coding agent used by my parallel worker group.
Devin CLI A command-line interface for running Devin tasks.
OpenHands CLI An open coding agent available from the command line.
Grok Build A coding agent available in my terminal agent set.
Hermes An open agent I can run from my terminal workspace.
OpenClaw An open agent runtime available in my installed agent set.

Editors, terminal, browser, and source control

Name Description
Mandeck The macOS workspace where I run coding agents side by side and hand work between them.
GitHub The source, pull request, review, and CI layer for the software I publish.
Visual Studio Code A code editor installed alongside my agent-first workspace.
Zed A native code editor installed on my Mac.
Xcode The build and signing tool for the native macOS apps I ship.
Shell The command-line layer underneath local builds, audits, and automation.
tmux The terminal multiplexer behind my lightweight parallel worker sessions.
SwiftBar The macOS menu-bar host I use for small local utilities.
Google Chrome The browser I use for product checks and web work.
GitHub CLI The command-line interface I use for repositories, pull requests, and checks.
XcodeGen The project generator used to keep native Xcode configuration in source control.

AI and local model apps

Name Description
ChatGPT A desktop AI workspace installed on my Mac.
Claude A desktop AI workspace I use alongside Claude Code.
Grok An AI app installed alongside my coding-agent tools.
Ollama The local model runtime installed in my development environment.

Languages, runtimes, and frameworks

Name Description
TypeScript The language used across site tooling, APIs, and product interfaces.
Python The language behind audits, content tooling, and small automation scripts.
Swift The language used for my native macOS applications.
Node.js The JavaScript runtime used by my web products and automation.
Bun The runtime used by Kyma and Affitor scripts, tests, and tools.
Next.js The web framework used by Kyma and Affitor applications.
React The interface library used across my web products.
Astro The static framework that builds this site from one set of Markdown content.
Strapi The content framework used by the Affitor CMS.
Tailwind CSS The CSS utility framework used in active product interfaces.
Go A compiled language installed in my development toolchain.
Rust A systems language installed in my development toolchain.

Infrastructure, hosting, and delivery

Name Description
Vercel The deployment platform that publishes this static site from its reviewed main branch.
Cloudflare Workers The edge runtime configured for the Kyma API backend.
Railway A deployment platform kept in the Kyma backend configuration.
Docker The container runtime in my local development toolchain.
Docker Compose The tool I use to define local multi-container services.
Colima The local container runtime layer installed on my Mac.
GitHub Actions The CI and scheduled automation layer for my repositories.
Tailscale The private networking tool installed in my local environment.
AWS Cloud services and SDKs used by the Affitor CMS.
Fly.io A deployment CLI kept in my infrastructure toolchain.

Data and storage

Name Description
Supabase The database platform connected to Kyma and Affitor applications.
PostgreSQL The relational database used by active web products.
Redis The key-value store used by Kyma services and local tooling.
DuckDB The local analytical database installed in my data toolchain.
Firebase A data and application service used by Affitor.
Vercel Blob Object storage used by the Kyma application.

Business, payments, CRM, and secrets

Name Description
Stripe The payment platform connected to Kyma and Affitor.
HubSpot A connected CRM tool in my operating stack.
Clay A connected research and go-to-market tool.
Doppler The secrets-management CLI installed in my development toolchain.

Email and communication

Name Description
Resend The email delivery service connected to my products.
AgentMail An email service connected for agent workflows.
Slack A connected communication tool installed on my Mac.

Analytics and SEO

Name Description
PostHog The product analytics and web-performance layer used on this site.
Ahrefs A connected tool for search and site research.
Google Search Console The search-performance source used by Kyma reporting scripts.

Design and content

Name Description
Canva A connected design tool in my content workflow.
Figma A connected interface-design tool.
Gamma A connected tool for producing presentation and document drafts.
v0 A connected interface prototyping tool.
CapCut A desktop editor installed for video work.
Screen Studio A desktop tool installed for recording product demonstrations.
OBS A desktop tool installed for screen recording and streaming.

Planning and knowledge

Name Description
Notion A connected workspace for notes and operating documents.
Linear A connected tool for product and issue planning.
Granola A connected desktop tool for meeting notes.
Obsidian A local notes application installed on my Mac.

Tools and products I built

Name Description
Kyma API The unified AI API I built and use across agent workflows.
Affitor The affiliate platform I built for products and partners.
Build to Own The operating system I built for turning repeatable work into owned products.
Kapt The screenshot tool I use to capture, annotate, and review product changes.
Watch CLI The command-line watcher I built for monitoring agent work.

How these fit together #

Build to Own teaches the whole circuit Mandeck the room the agents run in Kyma API one key, a hundred models What gets built watch-cli, Haynoi, Pheme, Kapt Affitor, open-affiliate tracking, terms, payouts graduates run agents calls for models returns answers needs distribution what works becomes the syllabus
People enter through the program and leave running the stack. The blue arrow is what makes it a loop.

Build to Own teaches the circuit. Mandeck is where the agents run, and Kyma API supplies the models. The things they build need distribution through Affitor and open-affiliate. What works returns to the syllabus.