Unexpected benefit when an LLM uses the same markdown as your public docs site: Claude seems to almost always keep docs up to date automatically 🤖 indiepub.dev/docs is powered by @astro.build 's Starlight. With chisel pointed at the same markdown files every new features gets docs right away

Don't bother building an #mcp server for your CLI tool Build good `--help` documentation or a man page and call it a day! Do it right once and it doesn't matter who/what the end user is

The future of software development, or the history of online poker The future of software development is unknown, but the history of online poker has some pretty clear hints...and it doesn't look great. 🔗 https://tonysull.co/articles/the-future-of-software-development

Stop building for #llms Build for humans and understand that, if useful, LLMs will figure out how to read your docs and run `--help`

`chisel planning new` incoming 👀 Go from idea to plan to issues to final docs, all in a TUI powered by local markdown files Using an LLM? They can use the exact same files and APIs to keep everything in sync

#llms sure seem happy with XML... Coming soon: `chisel context create "app routing"` Leverage SQLite FTS5 indexing of your own docs and issues to build a complete picture of the feature area you're working on

Write (on your) Own Site, Syndicate Everywhere. WOSSE - the #posse for docs?

Write once, document everywhere #posse meets #wode docs?

Hello, World. We're building Chisel — terminal-native tools for organizing your work. Crafted for developers, structured for AI. Public alpha is live: chisel.build #rust #terminal #tui #buildinpublic