My bathroom light started flickering last week. Not the dramatic horror-movie kind. Just enough to be annoying at 11 PM when you’re trying to convince yourself it’s not worth calling anyone about.
I didn’t call anyone. I typed this:
/maintenanceThat’s a slash command I built for Claude Code. It knows my apartment complex, my unit number, my entry preferences, even that I don’t have pets. When I told it the bathroom light was flickering, it figured out the right category on its own — Electrical and Lighting — wrote the description, and asked me to confirm.
Then it opened a browser, navigated to the resident portal, filled out the maintenance request form, took a screenshot so I could verify, and submitted it.
Request 22830-1 — Status: In ProgressTwo minutes. I described a problem in plain English and my terminal talked to building management.
Here’s what makes this interesting. This is the same terminal that writes code, files GitHub issues, publishes blog posts, and plays Big Bootie Mix at my roommate. The skill that handles maintenance requests is a markdown file — same format as the one that triages bugs, same format as the one that runs my morning briefing.
The system doesn’t know the difference between filing a bug and filing a work order. Same pattern: natural language in, structured form out. The only difference is whether the form lives on GitHub or a property management portal.
I keep adding these skills. Each one makes the line between “developer tool” and “everything else” a little blurrier. My terminal manages my code, my morning routine, and now my apartment.
Starting to wonder what’s left that needs a browser.