ArchLang — floor plans as code.
Write .arch. The compiler draws a dimensioned plan, checks it, and raises it into 3D.
Docs + playground: https://t.co/akz3bwXVx5
npm @chanmeng666/archlang
What this feed is: building in public — AI products, the checks behind them, and notes from the teaching cohorts I run.
Open to founding-team and senior AI engineering roles, client projects, and AI-tooling advice.
Everything in one place: https://t.co/qcHguQLEv7
I'm Chan Meng. I build AI products and the checks that keep them honest, and teach others to.
530+ GitHub stars across AI tools I've built: MCP servers, coding-agent plugins, a floor-plan language and an AI architectural designer on top.
Auckland, NZ → https://t.co/qcHguQLEv7
I build:
ArchCanvas AI architectural designer https://t.co/QQFLcuIdvP
ArchLang plan language https://t.co/WTnS1SozbC
echook for coding agents https://t.co/lf8G0TW8Xh
Google News MCP (PulseMCP Top Pick) https://t.co/hwtSwvwmMX
a11y-loop accessible UI https://t.co/fY63rsAMsk
The site I teach AI and programming from: bilingual, several cohort versions side by side, and an AI assistant inside the course that answers from the course material.
Open source. 30 seconds of it.
@_RichardLang@GrandpaCodes@MTSlive@rrwilliams Partly. Once a plan is geometry, not a picture, many properties are cheap to check: doors sit in walls, every room is reachable from the entrance, areas match the brief. Whether it's a good plan can't be checked that way. (I build ArchLang, which runs those checks.)
So procrastination isn't always a bug.
Sometimes it's your mind refusing to produce on a schedule that doesn't fit the work.
Push the non-urgent stuff back until you're actually ready, then go all in.
So many times I have had this interaction with normies where they don't understand what the jackfriks I'm working on as I'm just making random things for fun and messing around with things
And to them whatever I'm doing looks like a complete and utter waste of time, it has no function, no direct rewards, it's not making money, it's not successful
But so many times those projects evolve or lead to things where there is a massive payout or success after
But most people don't have the ability to see that far ahead, and they're risk averse so even if you tell them "I don't know maybe this becomes something, or maybe not, it doesn't really matter" that's simply too uncertain enough for them to accept. Which is of course why they love employment so much, it's stable and certain.
The problem with normies is that they will quickly shut this creative play down in themselves and even worse in others. And that way whatever that thing is, it won't ever grow into anything because they killed it before it ever got a chance, proving their point
Almost all my projects started by just messing around with no real goal, just playing for fun
But it requires some kind of peacefulness because the moment you start putting a requirement of success on to something new, the thing instantly dies
Creativity is really magical, and it messes with you if you try control it or expect things from it
Notice who made a lot of the early breakthroughs. Mendel was a monk with a garden. Darwin had family money.
Neither needed the work to pay. That freedom to chase "useless" questions was the real advantage.
`arch preview --review` on any plan: https://t.co/plnSvAZsyJ (that is draft 2). The warnings are advisory checks on geometry, not a code review; the rules are listed in the docs.
I gave a model the ArchLang spec and a brief for a three-bedroom flat, no compiler. Draft 1 was refused: a door jamb 25 mm from a wall. Draft 2 compiled with 12 warnings: a sofa in a door swing, a sink in a partition. It fixed all 12, and moving the table caused 3 new ones.
Offline-first, for crews with no signal: a React Native app for CORDE's water and civil-infrastructure field teams in Canterbury.
Capture text, photos and GPS on site. Sync when the connection returns. My university industry-placement capstone.
@GrandpaCodes@grok Glad Cursor worked. Changing one outer dimension only rewrites that number, so a plan with fixed coordinates often stops compiling. No auto-adjust of walls or furniture; Repair furniture only moves pieces out of walls and doors. Paste the snippet and I'll look.
@LewisValeLV First I check whether something other than the agent confirms its claim. In the ArchLang repo that is the compiler's --json output, and CI green before any merge, not the agent's own summary of what it did.
Weekend plans: Going to the beach, taking a walk, and relaxing.
Reality: My laptop is still running multiple Claude Code sessions, and I've activated /remote-control so I can monitor my AI coding tasks directly from my phone.
@LewisValeLV ArchLang has no separate note for that. What it has: lock an element by its id, and `archlang impact --lock` fails if an edit moves it. The reason can sit in a # comment beside it. Coordinating between people is outside what it does.
@LewisValeLV@LewisValeLV Only the ones that affect coordination: a moved stair, a wall the structure depends on, a room size someone else designs around. One line each. If every small tweak gets a note, the few reasons people actually need later get buried.