Explore intelligence

Recommendation · Money

Encapsulate complex multi-step operations into a single deterministic tool call

When a task involves programmatically interacting with the page — e.g., downloading a file and retrieving it from storage into the agent's runtime — encapsulate the operation into a single tool call that performs download and retrieval in one transaction, instead of the model making decisions on the fly. Leaving such decisions to the model increases steps, raising unit costs and reducing performance and maintainability.

AI Engineer · Why 99% Accurate Browser Agents Still Fail — Derek Meegan, Browserbase

Recommendation from Derek Meegan

: none

Recommendation · Money

Draft a skill — an agent-facing standard operating procedure — to outline the critical path

Meegan recommends drafting a skill, structured like a standard operating procedure for humans but for an agent, that outlines the critical path. Introducing the critical path makes the agent more likely to take the correct next step (e.g., knowing it's at step two and that step three is next) because ambiguity is removed from its decision process. Running without a skill leaves ambiguity, making the correct next step less likely.

AI Engineer · Why 99% Accurate Browser Agents Still Fail — Derek Meegan, Browserbase

Recommendation from Derek Meegan

: none

Recommendation · Money

Measure correctness per transaction, not per run, and permit retries

Meegan recommends measuring agent correctness on a per-transaction basis rather than per-run, permitting retries (e.g., up to four). A hypothetical agent with a 50% per-run success rate and up to four retries climbs to a 94% per-transaction success rate. Ground the metric in the customer: customers don't care how many retries you perform, only that the workflow completed successfully and reliably.

AI Engineer · Why 99% Accurate Browser Agents Still Fail — Derek Meegan, Browserbase

Recommendation from Derek Meegan

: retry count is an example; 94% figure is a hypothetical calculation

Recommendation · Money

Platform AI Readiness and Developer Experience

Invest in clear documentation, modular code, reliable CI, and non-flaky tests. What is good for humans is also good for AI agents. Assess platform readiness to improve token efficiency and context provision.

AI Engineer · The State of AI in Software Development: Data from 400+ Orgs — Justin Reock, DX

Recommendation from Justin Reock

Method

Procedure: Creating and Publishing a MakeKit from an NPM Package

Anthony demonstrates a step-by-step procedure: create a new MakeFile, open settings, select 'Create a Kit', choose an NPM package, click 'Start Installing', optionally add custom configurations, then test and publish the kit.

Figma · Bringing Design Systems into Figma Make

Method described by Anthony

Method preserved for inspection; not a verified protocol.

Method

Procedure: Testing and Publishing a MakeKit

Anthony demonstrates testing a MakeKit by typing a test prompt, then publishing it by clicking 'Publish Kit' and providing a name, scope, and version.

Figma · Bringing Design Systems into Figma Make

Method described by Anthony

Method preserved for inspection; not a verified protocol.

Method

Procedure: Writing Effective Guidelines for a MakeKit

Anthony recommends a procedure for writing guidelines: explain the setup assuming the AI has no knowledge, create categories to avoid overwhelming the AI, include actual examples, and call out common mistakes.

Figma · Bringing Design Systems into Figma Make

Method described by Anthony

Method preserved for inspection; not a verified protocol.

Method

Procedure: Building Effective Templates

Anthony recommends a procedure for building templates: lock down critical elements as hard-coded constants, constrain the edit surface with predefined prompts, add complexity incrementally, and calibrate against the model.

Figma · Bringing Design Systems into Figma Make

Method described by Anthony

Method preserved for inspection; not a verified protocol.

Recommendation · Money

Stop using Salesforce as your primary database for pipeline intelligence; push all data into a data warehouse like Snowflake with a semantic layer

Stop using Salesforce as your primary database for pipeline intelligence; push all data into a data warehouse like Snowflake with a semantic layer so it is agent-accessible. Clean your CRM data before layering on AI and put governance around accounts, contacts, and opportunities so AI systems analyze reality instead of CRM slop.

30 Minutes to President's Club | No-Nonsense Sales · #605 - How to Build a Cleaner Sales Pipeline in the Age of AI | Stevie Case

Recommendation from Stevie Case

Recommendation · Money

When a rep misses activity benchmarks, inspect what they are actually doing before demanding more calls or emails

Your best outbound reps might be violating your activity metrics and benchmarks, and they might be right. Inspect their unique process rather than forcing them to increase activity. If they have discovered a better playbook, scale it to the whole team.

30 Minutes to President's Club | No-Nonsense Sales · #605 - How to Build a Cleaner Sales Pipeline in the Age of AI | Stevie Case

Recommendation from Stevie Case

Recommendation · Money

Build a deal inspection system that is half machine and half human

Use AI to automatically pull discovery qualification evidence from call transcripts and surface deal gaps without requiring AEs to enter data manually. Have human leaders run live, human-led forecasts with their own narrative and point of view, then use an AI agent to analyze those forecasts and highlight weak spots before the leader conversation.

30 Minutes to President's Club | No-Nonsense Sales · #605 - How to Build a Cleaner Sales Pipeline in the Age of AI | Stevie Case

Recommendation from Stevie Case

Recommendation · Money

Prioritize Value and Mental Model Before Execution

Angel Steger emphasizes the importance of understanding the 'want behind the want' and establishing the correct mental model before building. She advises solving problems in order of importance: first validate value, then address functionality, workflow, or emotional choreography, and only then focus on details like aesthetics.

Design Better · Angel Steger: Wealthfront's VP of Design on what architecture teaches you about software

Recommendation from Angel Steger

Recommendation · Money

Design for Emotional States: Slow Down and Shepherd Users

Angel Steger discusses how design can manage users' emotional states, especially in high-stakes domains like finance and health. She advocates for making emotionally charged information intentionally boring and slow, using default views that show the bigger picture, and providing educational content to help users maintain a long-term perspective and avoid panic-driven decisions.

Design Better · Angel Steger: Wealthfront's VP of Design on what architecture teaches you about software

Recommendation from Angel Steger

Recommendation · Money

Avoid Premature High-Fidelity: Start Lo-Fi to Preserve Vitality

Angel Steger advises against jumping to high-fidelity prototypes too quickly, as it makes designs predictable and lacking in vitality. Instead, she recommends starting with low-fidelity methods (e.g., storyboards, sketches) to focus on the fundamental experience and value before details.

Design Better · Angel Steger: Wealthfront's VP of Design on what architecture teaches you about software

Recommendation from Angel Steger

Recommendation · Money

Do scary things repeatedly to grow and get better

Rob Walling advises that doing things that scare you over and over is how you grow and get better, both personally and professionally. He shares his own experiences of being terrified for his first blog post, podcast episode, stage talk, emcee event, and YouTube video, and how it got easier with repetition.

Startups For the Rest of Us · Episode 846 | Snail Mail, Cold Calling, Regulating Your Nervous System, and More Listener Questions (Rob Solo)

Recommendation from Rob Walling

Recommendation · Money

Evaluate feature requests by mapping out implementation and considering maintenance overhead

Derrick Reimer advises founders to map out a complex feature request concretely in code (e.g., using an AI agent) to assess the true expansion of surface area and maintenance burden before committing. Consider whether the feature will move the needle for the business or just add bloat.

Startups For the Rest of Us · Episode 850 | How Not to Screw Up When Hiring Your first Developer and More Listener Questions (with Derrick Reimer)

Recommendation from Derrick Reimer

confident

Recommendation · Money

Establish a rule of law with written, consented-to rules

Clay Parker Jones recommends establishing a 'rule of law' in organizations: a set of rules that apply equally to everyone and that everyone has consented to, with a mechanism for changing those rules. These rules should focus on what matters to the work and purpose, not trivial policies like expense reporting. The rules should be written down and treated as a temporary creed, held until new data emerges.

Design Better · Clay Parker Jones: author of "Hidden Patterns" on why your team isn't really a team

Recommendation from Clay Parker Jones

Recommendation · Money

Define and encode a true purpose

Clay Parker Jones recommends that every team should define a 'true purpose'—an enduring why that acts as a beacon. This purpose should be encoded in a document or phrase, referenced frequently without fear of feeling cringe, and must feel true to the end outcome, not just a feel-good statement. The purpose can range from small for an individual team to gigantic for saving the world.

Design Better · Clay Parker Jones: author of "Hidden Patterns" on why your team isn't really a team

Recommendation from Clay Parker Jones

Recommendation · Money

How to Apply the 'No Deal' Calm in Your Life

Identify where you are trying to force a deal (e.g., a flaky dating app match, a dragging investor). Make a concrete agreement with opt-in/out, then hold the line without discussing reasons or intent. Some people will fall through, but others will meet you because that calm is attractive.

Charisma on Command · This Scene Will Change How You Handle Conflict

Recommendation from Charlie Houpert

Recommendation · Money

Make Explicit Agreements with Three Parts

To avoid vague expectations that lead to boundary issues, make agreements explicit with three parts: what will happen, by when, and the option for the other person to opt in or renegotiate.

Charisma on Command · This Scene Will Change How You Handle Conflict

Recommendation from Charlie Houpert