As a hobby I run https://smalldocs.org / https://github.com/espressoplease/smalldocs an agent agnositc artifact layer, so I'm looking for feedback on artifact use in general.
Here are some sample scientific SmallDoc artifacts:
Palmer penguins: body mass, flipper length and species - https://smalldocs.org/s/YrJDCfCD8-6j_uRE0pNCbI#k=odJRxWOIySV...
AlphaFold 3: capabilities, evidence and operational limits - https://smalldocs.org/s/rRRuByQhmhZNBH_4RNCx1t#k=S0Jhyf72Q6M...
[–] theptip 1 day ago
[–] FailMore 1 day ago
Also, what are your main use cases for artifacts? Do SPAs and HTML pages work best for them?
[–] theptip 1 day ago
Main use by far is what I used to have Claude Code put in ./docs/feature-plan.md.
Second use is writing KB / explainers / research logs to share with folks, eg distilling the results of a chat thread into a durable artifact I can search/read later.
Hosted interactive explainers are nice sometimes, that’s where you get into SPA territory. Eg a lite Vercel app. This one is a bit more niche.
The missing feature for docs is now GDrive, ie organizing and cataloging your artifacts to build a coherent long-lived KB. But for that you can still export.
Anthropic added a while back the ability to let clients provide their own API key, again I think that’s under-explored and will become more relevant as AI gets more penetration.
Building out quick SPAs, HTML pages, etc is a great use, I think the innovation will be making these things supportable and usable for more than one-shot single-user artifacts. Eg user login, analytics, etc.