​
Prompting Fundamentals

The quality of your prompts directly impacts the quality of AI responses. Master these core principles to unlock co.dev’s full potential:

Single Focus

Concentrate on one specific feature or task. Multiple requests in one prompt lead to confusion and suboptimal results.

Precise Language

Use clear, specific terminology. Avoid ambiguous words like ‘better’ or ‘fix’ without context.

Break Down Complexity

Divide large features into smaller, actionable steps. This helps AI understand your exact requirements.

​
Real-World Examples

​
Page-Specific Modifications

Always specify the exact page using /page-name format to help co.dev locate the right file. 
Fix the button on the settings page
This prompt is too vague. Which button? What’s wrong with it? What should it do?

​
Feature Scope Management

Focus on one feature at a time for better results and clearer implementation. 
I would like to implement a feature that allows me to download 
the transcript of the conversation. When a user sends a message, 
it should automatically use AI to summarize it. When user accepts 
the agreement, it should display a modal to confirm.
This bundles three separate features together, making it confusing.

​
Advanced Prompting Strategies

​
File Management

File upload and attachment features are coming soon! This will allow you to share code snippets, designs, and documentation directly with co.dev for more contextual assistance.

​
Quick Reference

Do

  • Use /page-name for specific pages
  • Focus on one feature per prompt
  • Provide clear context and requirements
  • Include error messages when debugging
  • Specify technical constraints

Don't

  • Bundle multiple features together
  • Use vague language like “fix this”
  • Assume co.dev knows your project structure
  • Skip error details when reporting bugs
  • Forget to mention existing dependencies
Remember: The more specific and contextual your prompts, the better co.dev can assist you in building exactly what you need.