A Brief Account
Support is the work and inspiration, building tools to solve problems and reduce friction.
I am Skyler Halisky.
By day, I’m a senior technical-support specialist: the escalation point for enterprise accounts, and I train and coach teammates. I came to software through problems I wanted to solve. Most of them involved accessibility: tools that should have been better but weren’t. I decided to make some that were.
Accessibility is not an add-on. It is where you begin.
I work from Canada. Mostly on AI-assisted tooling, accessibility infrastructure, and community software. I prefer learning in public.
I keep a written record of how each thing was made. The documentation is part of the deliverable, not an afterthought.
Right now: an accessibility map. A multi-agent system that ships real commits. A local-first prompt manager. A command-line trainer. All of them documented in the open.
Method
How the work gets made is written down once.
There is one account of my method on this site, and it is on the front page: the governance system the agents work inside, the constraints that make the output reviewable, a case where the system blocked something it should have, and the limit I have not solved.
I would rather it exist once, accurately, than three times in three shortened forms.
Read how the work gets madePrinciples
Accessibility. Privacy. No shortcuts.
Flagstone is built and tested against WCAG 2.2 AA, with the methods and limitations documented in its case study. Flagstone exists because disabled people deserve navigation tools designed for them, not adapted for them.
The user’s data is theirs. Prompt Library stores everything locally: no backend of mine, no account, no telemetry. Runs go directly from the browser to Anthropic with the user’s own key; nothing passes through a server I control. If the data is not necessary, do not collect it.
I would rather take longer and do it correctly than ship fast and apologise. This is not a principle from a book. It came from shipping things that were not ready.
Currently
Learning in public. Shipping on purpose.
I am not a trained software engineer. I came to coding through building: I had ideas I wanted to exist. That is still how this works.
Right now: TypeScript, React Native, and multi-agent systems that stay inside their rules when I am not watching. Each project teaches something the last one did not.
The work I am aimed at is senior technical and product support: escalation, support tooling, support operations. Adjacent to it, and evidenced by the projects above: QA, accessibility, and privacy-aware systems work.
I am looking for collaborators and clients who read the documentation, ask good questions, and care how things turn out. Write to me if that sounds like you.
The Work