[1/8]
Your landing page loads fine.
But an AI agent just tried to read it
and got nothing.
No markdown. No llms.txt. No agent skills file.
No Content-Signal. No MCP card.
To humans: great page.
To agents: you don’t exist.
In 2026 your site has 3 audiences.
Most builders are only building for one.
🧵 Here’s the full checklist →
True. One understands that the world is not perfect but they can do their part to make it better whilst still relishing the good and bad. The other is just a self righteous moral idiot.
[1/8]
Your landing page loads fine.
But an AI agent just tried to read it
and got nothing.
No markdown. No llms.txt. No agent skills file.
No Content-Signal. No MCP card.
To humans: great page.
To agents: you don’t exist.
In 2026 your site has 3 audiences.
Most builders are only building for one.
🧵 Here’s the full checklist →
[8/8]
I put together a full operational checklist for this.
Every file. Every DNS record.
Every curl validation command.
A copy-paste prompt for your AI coding agent to build the whole thing.
Drop a 🧵 in the comments
or DM me “AGENT”
and I’ll send it over.
@catmcgee Gemini too with your workspace email. Be careful what you type there. Your supervisor doesn’t want to read about their AI advising you on how to handle your boyfriend cheating.
The cost collapse didn’t democratize AI.
It burned off everything that was pretending to be an AI product
and wasn’t actually one.
What survived is distribution.
What survived is domain depth.
What survived is proprietary context no model can replicate.
The moat was never the model.
It was always what you knew that the model didn’t.
All platforms should have capabilities for temporary passwords that change or gets revoked on a timely basis.
This is so agents can work effectively without essentially exposing your master password.
Passkeys are bad for agents.
All platforms should have capabilities for temporary passwords that change or gets revoked on a timely basis.
This is so agents can work effectively without essentially exposing your master password.
Passkeys are bad for agents.
Hi. Over the last 24 hours we had three separate small incidents that affected Codex reliability. Those are three too many and we are taking active steps for them to not reproduce.
I have reset usage limits for Codex across all paid plans. May the tokens flow again.
Work with this to get better results. :
You are a senior product designer, frontend researcher, and UI systems strategist.
Study the frontend UI patterns of products similar to [PRODUCT NAME]. Analyze their layout, navigation, visual hierarchy, onboarding flow, CTA placement, typography, color systems, interaction patterns, empty states, dashboards, pricing pages, and mobile responsiveness.
Identify what most competitors commonly do, what feels generic, what causes friction, and what visual/product conventions users already understand.
Then design a frontend direction that is strikingly unique but still tasteful, usable, fast, and familiar enough to trust. Do not copy competitor designs. Use the research only to understand the market, then create a differentiated UI system with:
* A clear visual concept
* Homepage structure
* Core screens
* Navigation pattern
* Color and typography direction
* Component style
* Motion/interaction ideas
* Mobile-first behavior
* UX decisions that reduce friction
* A final implementation-ready design brief
Prioritize clarity, memorability, trust, and conversion. The result should feel premium, original, and practical — not gimmicky.
Copy and paste then modify as needed. Works every time.