Tiny Little Office
- ID
- 35737
- Status
- summarized
- Published
- 15 Oct 2026, 6:10 AM
- Fetched
- 15 Oct 2026, 5:06 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://tinylittleoffice.com/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 15 Oct 2026, 5:06 PM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
Tiny Little Office is a browser-based suite of small tools — Word Processor, Outliner, Presentation Builder, Spreadsheet, Calculator, Drawing Tool, Diagram Maker, Animator, Calendar and Trip Planner — posted to Hacker News, where it drew 406 points and 62 comments. The submission text points at source files (site/site.ts, tinier/cards.ts) and at an /llms.txt that describes how to make a document as a link, with documents embeddable inside one another as a 'fence named by its app'. The excerpt itself is fragmentary and gives no pricing, release version, or architecture detail beyond those references.
Why it matters
The interesting decision here isn't the tool list, it's the /llms.txt contract: documents are addressed as links and nested inside other documents by naming the app that renders them. If that pattern holds, it's a concrete example of designing a document format so an agent can compose and embed your artifacts rather than screen-scrape them — worth reading the llms.txt before building your own 'make it agent-friendly' surface. Beyond that, the text does not give enough detail (no pricing, no self-host story, no limits) to justify changing anything today.
Discussion angle
Is an /llms.txt that defines link-addressable, app-named nested documents a reusable convention, or just a nice touch for one project? Compare it with how you'd currently let an agent drop a diagram into a doc.