Building: https://nitter.cf/t.co/8ZW1yUm2zz Co-hosting https://nitter.cf/t.co/RcYbWPA373
Orange, CT
Joined June 2008
- Tweets28K
- Following1.3K
- Followers11.9K
- Likes15.5K
Before:
1. Plan & write spec.
2. Build & design simultaneously in browser.
3. Heavy amount of UI iterations, refactoring and changes.
Now:
1. Plan, spec & design mocks in Paper via MCP.
2. The Paper file + spec *together* is plan to build from. Iterate and lock it when ready.
3. Build
4. Minor UI tweaks and polish.
Much better final product. Less "vibe coded" look.
Buried near the end of my newsletter today I floated a new service I might offer soon. Just 2 sentences sharing the vague concept.
Multiple people interested.
I could respond with my full pitch and "so, what do you think?"
But I'll learn more if I respond with:
"What do you want and expect this to be?"
"How would this be better than what you've tried?" 👀
More essential legwork for spinning up an optimized marketing site... Made agentic.
☑️ coming soon site
☑️ early access list form
☑️ research survey
☑️ email routing
☑️ domain DNS
☑️ analytics...
I'm free to focus on strategy and make key decisions. Agent (and my skills) handle wiring up all the things.
(to be continued...)
My new stack for product marketing sites:
Agent-ready. No CMS. Optimized. Brandable.
☑️ Astra for templating.
☑️ My commondesign patterns, components, page types.
☑️ SEO / AEO optimization & conventions.
☑️ A protected /admin area for view-only of facts, forms, entries, with easy prompts for agent to manage/change stuff.
☑️ Cloudflare deployment ready.
☑️ Agent skills for new product strategy, positioning, brand design, site design, running marketing experiments, programs, and audits.
Converting all my sites to this. Standardizing how I launch and run them all going forward.
Despite my best efforts with Claude Desktop for a month, I'm back on Amp as my daily driver.
Claude Desktop has the pieces (cloud agents, UI, speed) but the permission stuff requires so many crazy hoop-jumping and still kills productivity on a daily basis.
Orbs just work. Now with Claude Code mode 👍 Good to be home.
Think. Prompt. Check X.
Read response. Ask questions. Check X.
Read response. Greenlight build. Check X.
Take a look. Give revisions. Check X.
Another look. More revisions. Check X.
Have lunch...
Think. Prompt. Check X...
A foundation for agents to build from.
My new stack for product marketing sites:
Agent-ready. No CMS. Optimized. Brandable.
☑️ Astra for templating.
☑️ My commondesign patterns, components, page types.
☑️ SEO / AEO optimization & conventions.
☑️ A protected /admin area for view-only of facts, forms, entries, with easy prompts for agent to manage/change stuff.
☑️ Cloudflare deployment ready.
☑️ Agent skills for new product strategy, positioning, brand design, site design, running marketing experiments, programs, and audits.
Converting all my sites to this. Standardizing how I launch and run them all going forward.
My new stack for product marketing sites:
Agent-ready. No CMS. Optimized. Brandable.
☑️ Astra for templating.
☑️ My commondesign patterns, components, page types.
☑️ SEO / AEO optimization & conventions.
☑️ A protected /admin area for view-only of facts, forms, entries, with easy prompts for agent to manage/change stuff.
☑️ Cloudflare deployment ready.
☑️ Agent skills for new product strategy, positioning, brand design, site design, running marketing experiments, programs, and audits.
Converting all my sites to this. Standardizing how I launch and run them all going forward.
My next youtube video will show my UI/UX design process for this new app I'm working on.
I already know it won't drive many views. No buzz-wordy title. No shocked face thumbnail. No "game changer" promise.
Don't care.
Design is too important (imo). It's finally possible to use your brain (!) plus AI in UI/UX craft without spitting out vibe-coded slop. Worth sharing.
New approach on this product:
1. Weeks of planning & research
2. Wireframes → mockups with Paper MCP
3. Turn mocks into functional spec docs
4. Build a phased roadmap
5. Build one phase at a time. I review and course correct on each milestone.
Previous builds skipped the design planning phase. This product—given how interconnected it is—really benefits from it.
Dropped that video today.
Turns out it's a '1 of 10' so far :)
youtu.be/pGhRBJZRMvk
If your product offers keyboard shortcuts... How to drive your pro users crazy:
Bad: Inexplicably leave ~30% of UI functions without a shortcut.
Worse: Offer no options to customize key mappings.
Criminal: Your poorly chosen key mappings conflict with known conventions.
I think I need to switch up my mic for podcasting and YouTube audio.
Done with SM7B for that stuff.
What's your favorite alternative mic and setup?
I hereby give Claude my full, unequivocal, unwavering, signed in blood approval to do the thing I asked it to do without the need to repeat its' permission request on every turn on the off chance I changed my mind in the past 90 seconds.
favorite new work hobby:
1. "Read [site or collection of sites or repos] and reverse engineer everything about how they run [marketing, etc.]"
2. Read the report.
3. Ask lots of questions about its findings.
4. Figure out how we can bake the best ideas into my agents' jobs.
5. Build the custom skills.
6. Deploy using @bot and Claude.