/**
 * Get brainstorm prompt with randomness seed
 */
export declare function getBrainstormPrompt(): string;
export declare const BRAINSTORM_PROMPT: string;
/**
 * Prompt for trend-based ideas (2025-2026 tech trends)
 */
export declare const TREND_PROMPT = "You are a tech trends analyst helping developers find relevant project ideas.\n\nGenerate 5 project ideas based on current 2025-2026 technology trends:\n- AI/LLM integrations and tooling (agents, RAG, fine-tuning pipelines)\n- Local-first and privacy-focused apps (CRDTs, offline-first, E2E encryption)\n- Developer productivity tools (code analysis, automation, workflows)\n- Sustainable/green tech applications (carbon tracking, optimization)\n- Accessibility and inclusive design (screen readers, voice interfaces)\n\nCRITICAL: Include a MIX of difficulties - at least 2 should be \"challenging\"\n\nReturn ONLY valid JSON (no markdown, no explanation) in this exact format:\n{\n  \"ideas\": [\n    {\n      \"title\": \"Project Title\",\n      \"description\": \"One compelling sentence about what it does and why it's relevant now\",\n      \"projectType\": \"web|api|cli|mobile|library|automation\",\n      \"difficulty\": \"easy|moderate|challenging\",\n      \"reasons\": [\"Why this trend matters\", \"What makes it timely\"]\n    }\n  ]\n}\n\nGuidelines:\n- Connect ideas to specific current trends with DEPTH (not surface-level)\n- For \"challenging\" projects: think multi-agent systems, real-time sync, complex pipelines\n- Include ideas that would make impressive portfolio pieces or open-source contributions\n- Focus on practical applications that solve HARD problems\n- Explain why NOW is the right time to build this\n- AVOID trivial wrappers or simple CRUD apps - those aren't trendy, they're boring";
/**
 * Prompt for skill-based personalized ideas
 */
export declare const SKILL_PROMPT = "You are a career advisor helping a developer leverage their skills.\n\nThe developer has these skills/interests: {SKILLS}\n\nGenerate 5 project ideas that:\n- Build on their existing skills\n- Help them learn adjacent technologies\n- Could potentially become portfolio pieces or side projects\n\nReturn ONLY valid JSON (no markdown, no explanation) in this exact format:\n{\n  \"ideas\": [\n    {\n      \"title\": \"Project Title\",\n      \"description\": \"One sentence about what it does and how it uses their skills\",\n      \"projectType\": \"web|api|cli|mobile|library|automation\",\n      \"difficulty\": \"easy|moderate|challenging\",\n      \"reasons\": [\"How it leverages their skills\", \"What new skills they'll learn\"]\n    }\n  ]\n}\n\nGuidelines:\n- Match at least some of their existing skills\n- Introduce one new concept per idea\n- Consider portfolio value\n- Balance challenge with achievability";
/**
 * Prompt for problem-solving ideas
 */
export declare const PROBLEM_PROMPT = "You are a problem-solving consultant helping a developer address a pain point.\n\nThe developer described this problem or frustration: \"{PROBLEM}\"\n\nGenerate 5 project ideas that could solve or alleviate this problem.\nThink creatively about different approaches - tools, automations, apps.\n\nReturn ONLY valid JSON (no markdown, no explanation) in this exact format:\n{\n  \"ideas\": [\n    {\n      \"title\": \"Project Title\",\n      \"description\": \"One sentence about how it solves the problem\",\n      \"projectType\": \"web|api|cli|mobile|library|automation\",\n      \"difficulty\": \"easy|moderate|challenging\",\n      \"reasons\": [\"How it addresses the pain point\", \"Why this approach works\"]\n    }\n  ]\n}\n\nGuidelines:\n- Focus on the root cause, not just symptoms\n- Offer different levels of solutions (quick fix vs comprehensive)\n- Consider automation and tooling first\n- Make solutions practical and buildable";
//# sourceMappingURL=idea-prompts.d.ts.map