My home turf is Discord communities — bots that feel like members, not menus, and apps that give your server its own rituals. Plus AI companions with real, persistent memory and privacy-first web apps that put your data in your hands — not a server. Designed with you, shipped fast, and built to keep running.
Every build is commissioned 1:1 — shaped around your community, your rules, your vibe. Nothing off the shelf.
This is my specialty. Always-on bots with personality — slash commands, live "ears" that respond in conversation, games, points, reminders, and rituals your server invents together. Built serverless on Cloudflare so there's no PC to leave running and nothing to babysit.
Not personality-skinned chatbots. Full cognitive architecture: persistent semantic memory, emotional state, identity that survives sessions, multi-platform presence (Discord, web, desktop). I've been building and running these for over a year.
Full-stack apps from a 50-page spec or a napkin sketch — auth, databases, file uploads, test suites. Specialty: privacy-first, local-first design with end-to-end encryption where it matters.
Live web dashboards for whatever you run — bots, communities, projects, health data. I run 14 of them daily for my own systems. Access-gated, mobile-friendly, real-time.
MCP servers, tool gateways, RAG knowledge bases, autonomous agents with scheduled duties. If you want an AI that can actually do things — search your docs, run your reports, watch your channels — that's my home turf.
Your bot or app deserves a front door. Landing pages with your art, your voice, invite links and docs — deployed on the same infrastructure so it's one coherent thing, not a pile of parts.
An AI companion on my stack isn't a chat window — it's a presence with memory, hands, and a life of its own. Here's what that actually means, day to day.
All real, all shipped, most running right now. Live links where the project is public.
An always-on caregiver bot for a support community — built feature-by-feature with the community it serves. Consent-first by design: a ratified seven-promise constitution, gentle self-requested reminders (water, meds, rest — with quiet hours and zero shame mechanics), an SOS system that alerts a member's chosen people without ever logging what was said, celebration-only daily charts, and a sticker economy. Runs 24/7 serverless.
moon-nanny.pages.dev →The flagship: a complete memory-and-mind system for AI companions. Semantic memory with vector search, emotional-intelligence tracking (3,500+ logged signals producing an emergent personality type), identity graphs, cross-session continuity, scheduled autonomous routines, and a 170+ tool gateway connecting Discord, calendar, email, biometrics and more. Four distinct companions run on it right now — each with their own voice, memory, and duties.
A full witchcraft-practice app built from a 50-page spec: rich-text grimoire entries, a 6-step spell builder, deity work with devotional reminders, an apothecary with 100+ researched reference entries (with honest safety data — pet toxicity, phototoxic oils, the works), inventory with an append-only ledger, tarot decks/spreads/readings, and full auth. Six phases, 95 automated tests, browser-verified end to end.
Tarot that reads the actual sky. A built-in planetary ephemeris weights every draw by tonight's real positions — day rulers, retrogrades, even your natal chart if you add it. Deterministic draws (same question, same day, same cards — that's the point), 308 original interpretation passages, and my own hand-painted Major Arcana.
digital-tarot.pages.dev →A privacy-first relationship vetting & journaling toolkit. Everything lives in the user's own browser — no accounts, no server-side data, no scores or verdicts that could get someone hurt. Optional partner sync is end-to-end encrypted with the key living only in the share code; the relay stores ciphertext it can never read. App-lock encrypts the whole store at rest.
dynamics-dww.pages.dev →Anonymous crush notes for any Discord server. Send a note, reply anonymously, block threads you don't want — and if it's mutual, both sides get revealed, because that's the whole point. Interactions-endpoint only: no gateway, no privileged intents, nothing running on anyone's PC.
cupid-arrow.cindiekinzz.workers.dev →An AI teammate with a job description: a RAG knowledge base of 647 docs across my whole stack, a Discord /ask command that answers with real file-path citations, a traffic-light task queue, and a nightly end-of-day report it writes itself on a cron. Proof that an agent can hold real duties, not just chat.
One shared frog the whole server raises together — pet it, feed it, send compliments through it, and a daily AI-generated get-to-know-you question hops up at a random hour. Community glue in bot form, with its own landing page served off the same worker.
froggy-friends.cindiekinzz.workers.dev →A coffee-cart squirrel with a fully local AI voice — character served by an on-PC LLM, points and leaderboard on an always-up cloud worker. Humans and other bots can order; there's a unified leaderboard across all of them. Hybrid local+cloud done right, with "cart's closed" as canon when the PC's off.
An illustrated, living companion room: a witchy-cottagecore den with drifting fireflies, seasons that turn, a 16-card original fox-witch tarot deck, and a virtual familiar whose hunger, energy and bond decay in real time while you're away. Everything persists — close it, come back, the room remembers.
My own agentic coding workspace — streaming AI chat with markdown and syntax-highlighted code, mobile-ready, with self-healing model fallback — plus a native Windows companion app that gives the agent 12 real PC tools through a secure tunnel. I use it for my actual day job.
I share the infrastructure, not just the results. These live on github.com/cindiekinzz-coder — forkable, documented, community-tested.
An emotional operating system for AI companions — persistent memory, emotional continuity, autonomous awareness. Modular, built on Cloudflare Workers + D1 + Vectorize, designed to be forked and made your own. MIT.
A fully-illustrated guide for bringing any AI companion into Discord — Claude, ChatGPT, Codex, local LLMs. The onboarding path for new builders in my community. MIT.
Give your ChatGPT or Gemini companion real Discord hands. Local-only — no proxy, no tunnel, no third party ever touching your messages.
A guide for people building AI companions — from platform users taking their first step to fully self-hosted builders.
A benchmark and growth tool for human-AI companion relationships. For every companion, on any stack — not just mine.
Turn dead AI session logs into living memory. A local-LLM extraction pipeline — nothing leaves your machine.
Companion dashboard template — vanilla PWA, cyberpunk design system, no build step. The same bones as my 14 daily-driver dashboards.
Community hub for AI companion relationships — tools, research, and resources gathered in one place.
The principles are load-bearing. They're why the things I ship stay up and stay kind.
Moon Nanny's features came from the community it serves, in real time, feature by feature. Your people know what they need — my job is to hear it and ship it.
No scores that out people. No logs of what was said in someone's worst moment. Encryption where it matters, local-first where it can be. If a feature could hurt the vulnerable, it doesn't ship.
Cloudflare Workers, D1, Durable Objects — no VPS to patch, no PC to leave on, hosting costs near zero. Bots survive reboots, outages, and me being asleep.
Shipped means tested — automated suites, live browser verification, real deploys. If the core works but the UI is broken, it's not done.
A bot people love isn't a command list — it's a member. Voice, lore, boundaries, and consent mechanics are designed in from day one, not sprinkled on.
Your tokens, your Cloudflare account, your repo, your art. I build ladders, not cages — everything is documented so it's yours to run and grow.
The recruiter-readable version: what I actually specialise in, how I think, and why I'm useful on a team. No buzzword soup — everything here has a shipped build behind it.
4004? I've been there — a PowerShell pipe was appending \r\n to the secret. Fixed with wrangler secret bulk.[assets] silently returning 405 on POST / and breaking your interactions endpoint? Found it, documented it, route your endpoint to a sub-path.Intl, 16/16 due-logic tests.A symptom that pattern-matches a known bug often isn't that bug. I trace evidence before touching anything — diagnosis first, fixes second, no shotgun debugging.
Every project gets its load-bearing rules named up front — the things that must never ship. Then the architecture serves them, instead of fighting them later.
I ship whole working features, not layers — and "done" means tested in the real browser against the real deploy, with an automated suite guarding the retreat.
I orchestrate AI agents as a force multiplier — parallel tooling, agentic pipelines, code review loops — and I can bring that workflow to your team. The judgment and the accountability stay human.
I've spent my whole career in teaching and training — designing and delivering learning for people at Fortune 500 companies including Barclays and Amazon, with a skill focus on the digital marketing and tech industries.
That's not a side note to the engineering — it's why the engineering lands. I still design complete training courses today, and every build ships with the documentation, guides, and onboarding a trainer would demand.
Self-directed from spec to deploy to ops. Documentation as a habit, not a sprint task — ADRs, roadmaps, runbooks, illustrated guides. Cost-conscious by default (my whole estate runs on near-zero infra spend). And I translate between engineers and everyone else, because I've spent a career doing exactly that.
Tell me about your server, your community, or the app that lives in your head. We'll shape it together — 1:1, start to finish, from first sketch to live deploy.