Sabitlenmiş Tweet
GAIO
10.9K posts

GAIO
@michael_gaio
Aligning Intelligence in the age of AI: Story → Strategy → Systems. AI + Web3 + Marketing // Building @MythicSystems // Citizen @WilderWorld // Follow for ✦
✦ Join 👉 Katılım Ekim 2008
1.3K Takip Edilen2K Takipçiler

after years exploring AI, automation, and intelligent systems — and 25+ years working in tech and software — I’be launched a new personal / portfolio site focused on my AI engineering work.
Applied AI • agentic systems • orchestration
MichaelGaio.dev
English
GAIO retweetledi

I'm deleting every codebase documentation tool because of this.
Google launched CodeWiki and it turns any GitHub repo into documentation a normal human can actually understand.
You paste a repository and it automatically maps the entire project, explains the architecture, builds diagrams, creates tutorials, and gives you a chatbot that understands the codebase.
The difference from every other AI code explainer is the structure. Most tools summarize files. This turns the whole repo into an interactive wiki you can actually navigate.
→ Generates architecture diagrams automatically
→ Explains what each part of the codebase does
→ Detects dependencies and how files connect
→ Creates step-by-step tutorials from the repo
→ Turns complex systems into readable documentation
→ Lets you ask questions through a repo-aware chatbot
→ Makes onboarding to any codebase feel 10x faster
Basically:
you paste a repo you don't understand.
CodeWiki turns it into something you can read, explore, and ask questions about in minutes.
This is what documentation should have been all along.
Link below 👇

English

@michael_gaio the real question is whether i want to see your commits or your vacation photos more
English

@michael_gaio this is exactly what happens when engineers stop respecting the distinction between display and data formats
good luck parsing valid html at scale compared to actual structured formats
English

GAIO retweetledi

LLM Wikis + HTML Artifacts are insanely powerful.
You should seriously consider this in your workflows.
LLM Wikis captures all the important information that lets you and your agents do meaningful work.
HTML artifacts present that information in interesting ways that allow you to take important actions along with your agents.
My HTML artifacts sit on top of my LLM wikis. They are dynamic and are easily extended as needs arise.
I have hooked my Artifacts to talk to my agents, and similarly, the agents can talk to artifacts.
This has allowed me to build powerful artifacts that reduce my inbox to zero, keep me updated on any topic of interest, fast prototyping, do deep research, design/trigger new experiments, generate figures to improve understanding, schedule research, search relevant information, discover topics, and so much more.
What you see in the clip is not a website. It's a simple interactive HTML artifact.
HTML artifacts are useful for designers, engineers, researchers, students, and anyone working with agents.
Lastly, HTML doesn't replace Markdown. They are a much better combination working together.
English
GAIO retweetledi

HTML is the new markdown.
I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why.
Thariq@trq212
English

@mattpocockuk this is an amazing and practical insight
Definitely gonna consider this
English

GAIO retweetledi

Nearly 23K stars for a collection of markdown files I wrote
I guess they must be pretty good
I want to invest more time in this repo. So, folks who starred it, what can I do to make these skills more obvious to you?
- A docs site for the skills?
- Send them to plugin marketplaces?
Help me help you
github.com/mattpocock/ski…
English








