Effective communication strategies for AI-assisted development. Learn context-first prompting, phased interactions, iterative refinement, and validation techniques to get better results from Claude and other AI coding assistants.
View on GitHubjasonkneen/kiro
kiro-spec-driven
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/jasonkneen/kiro/blob/main/skills/ai-prompting/SKILL.md -a claude-code --skill ai-promptingInstallation paths:
.claude/skills/ai-prompting/# AI Prompting Strategies Master the art of communicating with AI coding assistants to get better results faster. These strategies are optimized for spec-driven development but apply broadly to AI collaboration. ## When to Use This Skill Use these prompting strategies when: - Working with Claude Code, Cursor, or other AI assistants - Creating specs through AI collaboration - Getting inconsistent or low-quality AI responses - Need to improve AI output accuracy - Want faster iteration cycles ## Core Strategies ### Strategy 1: Context-First Prompting Always provide sufficient context before making requests. **Poor Approach:** ``` Create requirements for a user profile feature. ``` **Better Approach:** ``` I'm working on a web application for a fitness tracking platform. We need to add user profile functionality where users can manage their personal information and fitness goals. Context: - Technology: React frontend, Node.js backend - User base: Health-conscious individuals, age 18-65 - Key constraint: Must comply with GDPR for EU users - Integration: Will connect with existing authentication system Please help me create requirements for the user profile feature. ``` **Why It Works:** - Provides domain context for better decisions - Identifies technical constraints early - Clarifies compliance requirements - Enables more relevant suggestions ### Strategy 2: Phased Interaction Work through spec phases sequentially. Complete each phase before moving to the next. **Phase 1 - Requirements:** ``` Let's start with the requirements phase for [feature name]. Current situation: [describe current state] Problem to solve: [describe the problem] Users affected: [describe user types] Success criteria: [how we'll know it works] Please help me develop comprehensive requirements using the EARS format. ``` **Phase 2 - Design (after requirements approved):** ``` Now that we have clear requirements, let's create the technical design. Requirements summary: [key requireme