Anthropic-slop-mastery
Claude 101
Yes, this is undoubtedly AI slop but mfs on Linkedln eat this up. All of this should be common sense, but if not, then you might be cooked.
Prompt engineering
What makes a good prompt
- Setting the stage: What is your role and what are your objectives? Is there context about your work that Claude should know about?
- Defining the task: What action do you want Claude to take? Do you want Claude to write, analyze, build, or something else?
- Specifying rules: What's the style or tone you want Claude to use? Are there examples that you can attach to show Claude what you're looking for?
Prompt troubleshooting
| Challenge | What's happening | Try this |
|---|---|---|
| Claude's response is too generic | Your prompt didn't include enough context about your specific situation | Add details about your audience, role, or constraints. Instead of "Write an email about the project delay," try "Write an email to our enterprise client explaining that the software integration will be delayed by two weeks. They've been patient so far but this is the second delay. Keep it professional but apologetic." |
| The response is too long (or too short) | Claude is guessing at appropriate length | Be explicit: "Give me a two-paragraph summary" or "Keep this under 100 words" or "I need a comprehensive analysis—length isn't a concern." |
| Claude didn't follow my format | Claude understood what you want but not how you want it presented | Show, don't just tell. Provide an example of the format, or describe the structure explicitly: "Use bullet points with bold headers for each section." |
| I got confident-sounding information that turned out to be wrong | Claude occasionally generates plausible but incorrect information, especially with specific facts or niche topics | For high-stakes work, verify key facts independently. Ask Claude to cite sources or indicate confidence level. Enable web search to ground responses in current information. |
| The tone isn't right | Claude defaults to helpful and professional, which may not match your needs | Describe the tone in plain language: "Make this more conversational" or "This should sound authoritative and formal." Provide an example of writing in the style you want. |
The 6-part prompt framework
- Give context: Be specific about what you want, why you want it, and relevant background
- Show examples: Demonstrate the output style or format you're looking for
- Specify constraints: Clearly define format, length, and other output requirements
- Break complex tasks into steps: Guide the AI through multi-step reasoning
- Ask the AI to think first: Give space for the AI to work through its process
- Define the AI's role or tone: Specify how you want the AI to communicate
4D framework for AI fluency
three ways people engage with AI:
- Automation: The AI completes specific tasks based on your instructions.
- Augmentation: You and AI collaborate as creative thinking and task execution partners.
- Agency: You configure AI to work independently on your behalf, establishing its knowledge and behavior patterns rather than just giving it specific tasks.
The 4D Framework for AI Fluency, developed through research collaboration between Professor Rick Dakan (Ringling College of Art and Design) and Professor Joseph Feller (University College Cork), identifies four core competencies that, when combined, can help you make the most of your AI interactions:
- Delegation: Deciding on what work should be done by humans, what work should be done by AI, and how to distribute tasks between them. Includes understanding your goals, AI capabilities, and making strategic choices about collaboration.
- Description: Effectively communicating with AI systems. Includes clearly defining outputs, guiding AI processes, and specifying desired AI behaviors and interactions.
- Discernment: Thoughtfully and critically evaluating AI outputs, processes, behaviors and interactions. Includes assessing quality, accuracy, appropriateness, and determining areas for improvement.
- Diligence: Using AI responsibly and ethically. Includes making thoughtful choices about AI systems and interactions, maintaining transparency, and taking accountability for AI-assisted work.
Delegation
Delegation is about making thoughtful decisions about what work to do yourself, what to do together with AI, or what to let AI handle independently, and how to distribute those tasks. It's the thoughtful approach about deciding where and when to use AI.
To Delegate well, you need to do these three things:
- Understand your goal and the problems you are trying to solve
- Know what AI systems can and can't do well.
- Decide how to divide the work between you and AI.
There are three types of delegation and what questions you need to ask to use them effectively:
- Problem Awareness: Understanding your goals and the work involved to achieve it
- What does success look like? What's the thinking and type of work needed to get there?
- How can I rely on my domain expertise to delegate to the AI effectively?
- Platform Awareness: Knowing what different AI systems can do, their capabilities and limitations.
- What's the best AI system for this specific task?
- Which systems prioritize speed, accuracy, and creativity?
- Task Delegation: Strategically dividing work between you and AI
- What could be usefully automated?
- Where would augmentation create more value than working separately?
- What should be done by a human alone?
- What can an agent do on your behalf?
Description
A good description describes the following:
- What you want the final output to be
- How you want the AI to approach the task
- How exactly you want the AI to behave (tone and style)
There are three components that make up a good description:
- Product Description involves clearly defining what you want in terms of outputs, format, audience, and style
- Process Description guides how the AI approaches your request, which can be as important as specifying the end goal
- Performance Description defines behavioral aspects like whether the AI should be concise or detailed, challenging or supportive
Discernment
Discerning what's good vs bad concernign AI outputs hinges on three key questions:
- Is the output useful and correct?
- Is AI taking the correct approach?
- Is the AI behaving as desired?
There are hree types of Discernment:
- Product Discernment: Evaluating the quality of AI outputs
- Process Discernment: Assessing how the AI approached the task
- Performance Discernment: Evaluating how the AI behaved during the interaction itself
Product Discernment:
- Which explanation contains the most accurate information?
- Are there any factual errors or misconceptions?
- Is the level of detail appropriate for someone learning about this topic?
Process Discernment:
- Does Claude follow logical reasoning in each explanation?
- Are there gaps in its analysis or thinking process?
- Does Claude make appropriate connections between concepts?
Performance Discernment:
- Was Claude attentive to your specific question and responsive to feedback and direction?
- Is terminology used appropriately for the topic?
- How does the tone and style affect the clarity of the explanation?
Diligence
Can you stand behind your outputs and verify them as correct and take responsibility for them?
- Creation Diligence: Being thoughtful about which AI systems you choose and how you work with them
- Transparency Diligence: Being open about AI's role in your work
- Deployment Diligence: Taking ownership for AI-assisted outputs you share with others
Personalizing Claude
There are two features that help Claude work better for you over time to increase the power of your prompts.
- Memory automatically saves key context from your conversations — your role, preferences, past decisions, and working style — so you don't have to repeat yourself every time you start a new chat. For example, if you tell Claude you work in marketing at a B2B company, it'll remember that context going forward. You can review, edit, or delete anything Claude remembers anytime in Settings, and memory syncs across all your devices.
- Styles let you customize how Claude communicates. Choose from preset options — like concise, formal, or explanatory — or create your own custom style by describing exactly how you want Claude to write. Once set, your style applies across all conversations automatically.
Evals
Evals (short for evaluations) are a way to develop intuition for assessing Claude's outputs on the tasks that matter to you. They're systematic ways to test how well Claude performs on specific types of tasks that matter to you.
Running simple evals helps you:
- Understand where Claude adds the most value in your workflow
- Identify tasks where you'll need to provide more context or examples
- Build confidence in Claude's outputs for recurring tasks
Simple eval approach
You don't need complex infrastructure to evaluate Claude. Here's a practical approach:
- Gather examples.