Useful software.Made for people.

I’m Taako, a developer and community builder. I build Discord tools, web interfaces, and automations that turn messy workflows into something people can actually use.

A friendly robot reading beside a lantern-lit cottage on a tiny floating island, with a garden, a stream, and warm sunlight.

Build.TypeScript & Python

Connect.APIs & PostgreSQL

Keep it running.Linux & Docker

Live products I built and run.

Two Discord products, both in production. I built the web app, API, bot, and deployment for each.

More builds

  • RedPanel

    A self-hosted dashboard for Red-DiscordBot. A small cog connects out over a WebSocket, so the bot token never leaves the bot.

    Go · TypeScript · Python
  • Desktop mod manager

    An offline desktop app for managing game mods, with real file operations, SQLite metadata, and recoverable changes.

    Dart · Flutter · SQLite
  • Desktop tool rewrite

    A work-in-progress rewrite of a Windows modding utility, moving its file parsing and export logic to a typed, memory-safe codebase.

    Rust
  • Discord Bot Operations MCP

    A guarded tool server that inspects a host and a Discord server, builds reviewable plans, takes backups, and validates the result. It has no generic shell access.

    Python
  • HELLBORN Archive

    A multi-page roleplay character archive with owner login and media uploads.

    Next.js · TypeScript · D1 · R2

Shipped a little every week.

Commit activity across my projects over the last six months.

The work behind the tools.

How I approach the problems behind the projects: Discord, web interfaces, and self-hosted services.

01 / Community systems

A calmer way to run a community.

The problem

Staff workflows span commands, roles, channels, and settings. Small mistakes can become confusing for everyone.

How I approach it

Check permissions first, keep actions modular, and make the result clear to the person using the tool.

Technical focus

  • TypeScript & Python bot extensions
  • Permission checks and useful feedback
  • Persistent settings and audit trails
  1. Request
  2. Validate
  3. Action
  4. Record

Try a little of the logic.

A small interactive example, built for this portfolio. Sample data, real interface.

Workflow lab

From request to result.

Try removing access or simulating a failure.

Runs locally. No Discord connection.

Execution trace

Ready
  1. 1Validate
  2. 2Queue
  3. 3Deliver
  4. 4Record

Ready when you are.

Configure a request, then run the workflow.

No request yet

The result will appear here.

Permission checks · State transitions · Error recovery

Permission lab

Who is allowed to do what?

Your roles

Toggle roles and see the same bitwise checks Discord applies, in order.

Runs locally. Sample roles and channels.

Permission trace

Allowed

    Role bitfields · Channel overwrites · Administrator bypass

    Determinism lab

    Same seed, same sky.

    Change any input and the forecast updates. Put it back and you get the exact same forecast.

    A simplified model of the idea behind a roleplay weather bot, not its production tables.

    Forecast

      Seeded randomness · No global state · Reproducible output

      The toolkit, with a purpose.

      Applications

      TypeScript · JavaScript · Python · Go · Dart

      Bots, reusable modules, web interfaces, and desktop apps.

      Data & integrations

      PostgreSQL · SQLite & D1 · Redis · Prisma · REST APIs

      Persistent state, typed data, and services that talk to each other.

      Infrastructure

      Linux · Docker · Cloudflare Workers

      Deploying, moving, and maintaining self-hosted services.

      Delivery

      Git · GitHub Actions · Troubleshooting

      Repeatable changes, useful logs, and a way to recover.

      I build for the
      people on the
      other side.

      Running communities has shaped the way I build software. I care about the handoff: what a moderator sees, what happens when something fails, and whether the next person can understand the tool.

      I work across bots, interfaces, APIs, and deployment. I like following a problem from the first rough idea through the details that make it usable.

      1. 01

        Understand the workflow.

        Learn how people actually use it, what gets in the way, and what matters most.

      2. 02

        Build the useful part.

        Turn the idea into something clear, maintainable, and easy to work with.

      3. 03

        Test the awkward cases.

        Try the edges, handle what can go wrong, and make sure it’s understandable.

      Something worth building?

      I’m open to developer roles and project work. Email is the quickest way to reach me, and the code I can share is on GitHub.