/create
My creative work spans technical writing, practical resources, music, talks, community tools, and experiments. The common thread is taking something abstract — an idea, lesson, system, mood, or problem — and giving it a form other people can actually engage with.
Creation is not decoration added after the technical work. It is how the work becomes legible, usable, memorable, and human.
Five create modes
These are creative lenses, not new services or separate business divisions. Most real work uses several at once — the question each one asks is how an idea should reach the person on the other end.
Make the complicated reasoned-about
Technical writing that translates jargon, documents the tradeoffs, and walks through how a system actually works — so a reader can reason about it instead of taking it on faith.
// related
Turn a lesson into something reusable
When a lesson is worth repeating, it gets shaped into a checklist, playbook, or template — practical teaching material someone can pick up and apply without sitting through a course.
// related
Pacing, clarity, and audience
Music as DJ PakkitStorm, and the same instinct applied to talks and interfaces: pacing, transitions, and audience awareness so a set, a demo, or a page lands instead of drags.
Lower the friction to participate
Discord tooling, event helpers, and collaborative systems that make it easier for people to coordinate and take part — plus mentorship that hands the instincts forward.
// related
Sketches, labeled as sketches
Small prototypes, AI experiments, and weekend builds — learning in public. Kept clearly labeled: an experiment is not a public artifact, a production system, or a commercial product, and it may never become any of them.
// related
How the creative work stays grounded
Expression is welcome, but it serves the idea. These are the instincts that keep a creative choice in service of the person it's meant to reach.
Making something easy to understand is design work, not a step you do after the real work.
Who needs this and what they'll do with it decides whether it's a post, a checklist, or a set.
A tight scope, a time limit, or a small canvas forces the decision that a blank page hides.
The write-up ships with the thing. An undocumented tool is half-made, however clever it is.
Bury the takeaway and it doesn't exist. The point should be reachable in seconds, not paragraphs.
Voice and a little fox-flavored character are welcome — until they start hiding what the thing is for.
AI can draft and sketch, but a person stays responsible for what actually goes out the door.
A weekend sketch is called a sketch. Nothing unfinished gets dressed up as a launched product.
When reuse is practical, a template or pattern is worth more than a one-off that vanishes after use.
Contrast, structure, and keyboard reach aren't extras — they decide who actually gets in.
Things I've made
A few real destinations, each one a different answer to the same question: how should this idea meet people?
Technical writing and field notes on building systems and debugging reality.
Helps: Engineers and curious readers who want the real, reasoned version instead of marketing.
Instinct: Explaining a system so someone else can hold it in their head.
openPractical playbooks and checklists pulled straight out of how the work actually gets built.
Helps: Builders who'd rather start from a sane default than a blank page.
Instinct: Packaging a repeated lesson into something reusable.
openThe DJ PakkitStorm music identity — set craft, energy, and the engineering brain pointed at sound.
Helps: Anyone who connects with the creative, expressive side of the Pakkit identity.
Instinct: Shaping pacing and energy so an experience lands as one arc.
openDiscord automation and game-community tooling, written up as a project.
Helps: Communities that want coordination to feel easier and a little more fun.
Instinct: Designing tools people actually want to use, with an obvious off switch.
openAfter-hours creative-tech sketches — small music tools, AI tinkering, and the occasional weird build.
Helps: Anyone curious about low-stakes experiments before they harden into systems.
Instinct: Following a curiosity to its smallest buildable slice, honestly labeled.
openPractical topics and workshop starting points — subjects I'm equipped to talk through.
Helps: Teams, communities, and organizers looking for a grounded technical conversation.
Instinct: Turning hard-won lessons into something a room can follow.
openBrowse the full projects index — Everything, including the work that isn't featured here.
Choose a creative path
Pick the line that sounds like your situation — the links explain where each one goes, in plain language.
Where Build and Play meet
Build brings structure and reliability; Play brings curiosity and energy. Create gives the result a form people can understand and engage with. Same person, three modes — not three companies, teams, or personalities.
Build
Structure, reliability, and the implementation that makes a thing real.
Create
The form that makes the result legible, usable, and worth sharing.
Play
Curiosity, energy, and the experiments that keep the loop running.
A note on visuals and identity
Visual experimentation exists in my creative work, but it's not a standalone production discipline. Think occasional visual loops, AI-assisted sketches, interface experiments, and the cyberpunk, fox-flavored details that give the identity its character. Design here is support for communication — not a claim to professional motion, animation, or art-direction credentials.
Make something worth sharing
You don't need a polished brief. I'm open to: