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.
39,935 results · Most relevant
Anthony demonstrates testing a MakeKit by typing a test prompt, then publishing it by clicking 'Publish Kit' and providing a name, scope, and version.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
confident
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.
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.
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.
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.
Alex Hormozi recommends a set of diagnostic questions to clarify thinking and avoid unproductive actions. The primary question is 'What problem are you trying to solve?' to ensure any proposed action addresses a real issue. A second key question is 'What do you want to have happen?' to cut through emotional noise and get to the desired outcome. A third set of questions—'What does that mean?', 'How do you know that?', and 'So what?'—are used to probe the depth of someone's thinking and connect actions to business outcomes. Finally, asking 'What else could we do with this time and energy that would yield a higher return to the business?' forces a comparison against the best alternative use of resources.
Hormozi advocates for the question 'What would it take?' as one of the most powerful in entrepreneurship. He explains that this question assumes success, which shifts the conversation from 'if' to 'how'. He contrasts this with asking 'Can we?' or 'Could we?', which he says leads people to say 'no' because they make a decision based on incomplete context. He provides numerous examples of how to use this question in different scenarios, such as asking for a faster timeline, buying a company, or getting someone to start a project today.
Consequential creator advice requires independent verification before Today can promote it.
Alex Hormozi advises that when you feel an emotional urge to change direction, you should keep doing what you were doing and let the emotion pass. He compares emotions to the weather: they come and go. He suggests acknowledging the emotion exists and continuing anyway.
Alex Hormozi defines focus as doing one thing and not pursuing shiny objects. He advises to keep doing the old stuff instead of chasing new things. He states that a focused fool will beat a distracted genius.
Alex Hormozi advises making the correct decision independent of how you feel. He states that if your emotions encourage an action aligned with logic, it is the logic, not the emotion, that made it correct. He advises embracing emotional discomfort and not taking action just to change how you feel.
Choose sources → to get a library of your own and a daily brief.