[lelanthran]

I don't see a description of the format in that.

What does a human write to (for example) create the diagram mentioned in "A diagram, drawn from a description rather than dragged into place."?

To me this looks like AI-writes-everything and human-reads-everything.

[FailMore]

It is mostly that pattern yes, but you can see the underlying formats in https://smalldocs.org/docs

[lelanthran]

Right, thanks.

I looked at the format. I think you're mostly on the right track, but I also think that a better candidate might be to simply use (and augment, where necessary, such as for styles) the org mode format: It can do all the stuff you have, but also things like checkboxes, calendars, and more.

As a bonus, both people and agents already know the format so there is no need to have a skills file. For example, the following prompt on Gemini WebChat (hardly a good model):

    Give me an org mode file to show a PERT (Project evaluation and Review Technique) diagram, with a calendar below the diagram allowing me to see the current year. Create a hierarchy of tasks that have to be done using  checkboxes and collapsible sections to mark tasks/subtasks as done. Below that, give me a table of all the terminal tasks that need to be completed with task/subtask name, starting date, estimated ending date and the resource assigned to it.

    Finally, at the end, produce a gantt chart as a mermaid diagram for the sample project.

Produced a working file with tables[1], diagrams, calendar, checkboxes in a single file that Emacs rendered properly. Org mode can export to every format I ever needed (LaTeX, html, pdf). I once even had the resulting HTML conversion contain animations written in Javascript :-)

Maybe all you need to code for agents to write is a web-based viewer for Org Mode syntax?

Look at it this way: right now if I wanted what smalldocs does (i.e. ask the agent to generate any of your examples), I can ask the agent "do $FOO, generate org mode", and without a single additional skill/claude.md/agents.md file, get exactly the result you got from smalldocs.

I think maybe testdrive Emacs daily for a month; it would open your mind to the possibilities available[2]. If anything more is needed (like I wanted to put in JS in the HTML output), it can do it. If Emacs cannot do it, my agent can write an EmacsLisp function that will do it.

At the end of the day, when even a poor LLM can do what smalldocs does but without any additional .md files or context, I think maybe your solution might be over-engineered.

----------

[1] Org mode tables work exactly like spreadsheets, in that they can contain formulas.

[2] Think of it this way - when I needed multimodal documents, because I already knew Emacs, I just used that. When you needed multimodal documents, you vibed a whole new product into existence.

[philips]

I have been thinking about the problem of collaborating with AI in spreadsheets a bit. I think I want a few things solved:

- Revision control with attribution so I can double check LLMs edits

- Online collaboration with other humans and LLMs

- Schema and validation of column and row data

- Excel and Gdocs interoperability

One path I think you could go to accomplish this would be DuckDB which creates a programming interface that LLMs could use and interoperability with Excel and Google Docs via plugins.

Not sure if it is better to create from scratch rebuilds of the spreadsheet UX or rely on existing spreadsheet apps for that.

All that being said for any work I do I think I would want my data an LLM is operating on to be more structured and constrained than a text file or even a spreadsheet without cell validation.