advanced-prompting-and-adversarial-testing
Based on the research from The Prompt Report (co-authored by OpenAI, Microsoft, and Google), prompt engineering is about "artificial social intelligence"—knowing how to elicit the best performance from a model through specific structural patterns.
Core Prompting Techniques
1. Few-Shot Prompting (The Highest Value Technique)
Do not describe your requirements in prose; provide 3–5 concrete examples of input/output pairs.
- Structure: Use a common format the model recognizes from training data, such as XML tags or
Q: [Input] / A: [Output]. - Placement: Put examples before the final instruction.
- Why it works: It establishes a pattern for the model to follow, which is more effective than descriptive instructions for style or formatting.
2. Task Decomposition
For complex logic, prevent the model from jumping to a conclusion. Force it to map the problem space first.
- The Prompt Phrase: "Before answering, list out the sub-problems that need to be solved first."
- Workflow:
- Ask for sub-problems.
- Have the model solve each sub-problem individually.
- Synthesize the final answer from those components.
3. Self-Criticism (Iterative Refinement)
More from samarv/shanon
agentic-workflow-automation
Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.
63niche-market-opportunity-mapping
A framework for identifying high-margin, low-competition business ideas ("fishing holes") by leveraging personal unfair advantages and avoiding overcrowded markets. Use this when vetting a new startup idea, choosing a niche for a service business, or seeking to pivot an existing product into a more profitable segment.
18b2b-value-negotiation
A framework for defending price and extracting maximum value in B2B sales. Use this skill when a prospect asks for a discount, when transitioning a POC to a commercial deal, or when presenting high-ticket pricing to budget-conscious stakeholders.
18b2b-saas-workflow-strategy
A framework to evaluate the market potential and strategic direction of B2B products based on workflow frequency and organizational breadth. Use it when validating a new startup idea, evaluating a product's "ceiling," or planning a pivot to increase market share.
14agentic-engineering-workflow
Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.
10b2b-category-creation-strategy
A framework for determining when to create a new software category versus winning an existing one, and the tactical steps to define and validate that category. Use this when your product is too disruptive for current labels, when existing categories have negative associations, or when you need to expand your TAM.
9