Real Transformation Examples

❌ Vague Original Prompt

"Fix the login bug"

Issues:
• Lacks specific problem context
• No targeted investigation area
• Generates extensive clarification cycles
• Token cost: ~$4.20 per resolution

✅ WordLink Optimized

# Goal
Fix authentication system where users cannot login despite having valid credentials. Issue appears to be in JWT token validation logic - tokens are being rejected with 'invalid signature' errors even when credentials are correct. Users report successful login attempts resulting in immediate redirects back to login page.

# Files to change
- auth.js
- login.js
- middleware/auth.js

# Expected outcome
1. Complete root cause analysis of authentication failure
2. Specific JWT library version compatibility check
3. Step-by-step fix implementation with error handling
4. Security audit of token validation changes
5. Comprehensive test suite for all auth scenarios
6. Migration strategy for existing user sessions

Advantages:
✓ Pinpointed issue and exact location
✓ Actionable debugging pathway
✓ Single-request resolution
✓ Token cost: ~$0.85 (79% reduction)

❌ Simple Request

"Add dark mode"

Limitations:
• Absent technical specifications
• No architectural considerations
• Ambiguous feature boundaries
• Produces generic template responses

✅ WordLink Optimized

# Goal
Add dark mode

# Constraints
- Keep diffs minimal
- Modify only listed files
- Add or update tests for touched functions
- Use existing design system
- Maintain consistent spacing

# Files to change
- src/components/Header.tsx
- src/context/ThemeContext.tsx
- src/styles/globals.css

# Tests
Add or update tests for touched functions

# Workflow
Think step by step, plan your approach, then implement changes carefully.

# Output
Return a unified diff patch only, no extra commentary.

Improvements:
✓ Detailed implementation roadmap
✓ Honors current system design
✓ Explicit technical constraints
✓ Immediate successful deployment

❌ Unclear Request

"Make it faster"

Problems:
• What needs to be faster?
• No performance metrics
• Vague optimization target
• Generic suggestions

✅ WordLink Optimized

[ROLE]
You are an expert in performance optimization.

[CONTEXT]
Here is the relevant context:
Files to modify: ProductList.tsx, routes/index.tsx, components/ImageLoader.tsx
Constraints: Target load time under 2 seconds, maintain existing functionality

[INSTRUCTIONS]
Do: Make it faster, keep changes minimal and focused, maintain existing code style and patterns, follow these constraints: Target load time under 2 seconds, maintain existing functionality.
Do not: make unrelated changes, break existing functionality, ignore the specified constraints.

[OUTPUT FORMAT]
Respond in a unified diff patch format with clear, focused changes. Keep concise.

Benefits:
✓ Specific performance targets
✓ Actionable optimization steps
✓ Current baseline metrics
✓ Measurable success criteria

❌ Generic Request

"Connect to Stripe API"

Problems:
• No integration context
• Missing current setup details
• Unclear requirements
• Generic documentation dumps

✅ WordLink Optimized

# Goal
Connect to Stripe API

# Constraints
- Keep diffs minimal
- Modify only listed files
- Add or update tests for touched functions
- Use existing cart context
- Handle payment errors

# Files to change
- components/Cart.tsx
- pages/api/stripe/webhook.ts
- lib/stripe.ts
- types/payment.ts

# Tests
Add or update tests for touched functions

# Workflow
Think step by step, plan your approach, then implement changes carefully.

# Output
Return a unified diff patch only, no extra commentary.

Benefits:
✓ Specific integration scope
✓ Works with existing architecture
✓ Clear technical requirements
✓ Handles edge cases upfront