mirror of
https://github.com/AutoMaker-Org/automaker.git
synced 2026-02-02 08:33:36 +00:00
ff281e23d0
- Introduced a new IdeationService to manage brainstorming sessions, including idea creation, analysis, and conversion to features. - Added RESTful API routes for ideation, including session management, idea CRUD operations, and suggestion generation. - Created UI components for the ideation dashboard, prompt selection, and category grid to enhance user experience. - Integrated keyboard shortcuts and navigation for the ideation feature, improving accessibility and workflow. - Updated state management with Zustand to handle ideation-specific data and actions. - Added necessary types and paths for ideation functionality, ensuring type safety and clarity in the codebase.
392 lines
15 KiB
TypeScript
392 lines
15 KiB
TypeScript
/**
|
|
* Guided prompts for ideation sessions
|
|
* Static data that provides pre-made prompts for different categories
|
|
*/
|
|
|
|
import type { IdeaCategory, IdeationPrompt, PromptCategory } from '@automaker/types';
|
|
|
|
export const PROMPT_CATEGORIES: PromptCategory[] = [
|
|
{
|
|
id: 'feature',
|
|
name: 'Features',
|
|
icon: 'Zap',
|
|
description: 'New capabilities and functionality',
|
|
},
|
|
{
|
|
id: 'ux-ui',
|
|
name: 'UX/UI',
|
|
icon: 'Palette',
|
|
description: 'Design and user experience improvements',
|
|
},
|
|
{
|
|
id: 'dx',
|
|
name: 'Developer Experience',
|
|
icon: 'Code',
|
|
description: 'Developer tooling and workflows',
|
|
},
|
|
{
|
|
id: 'growth',
|
|
name: 'Growth',
|
|
icon: 'TrendingUp',
|
|
description: 'User engagement and retention',
|
|
},
|
|
{
|
|
id: 'technical',
|
|
name: 'Technical',
|
|
icon: 'Cpu',
|
|
description: 'Architecture and infrastructure',
|
|
},
|
|
{
|
|
id: 'security',
|
|
name: 'Security',
|
|
icon: 'Shield',
|
|
description: 'Security and privacy improvements',
|
|
},
|
|
{
|
|
id: 'performance',
|
|
name: 'Performance',
|
|
icon: 'Gauge',
|
|
description: 'Speed and optimization',
|
|
},
|
|
{
|
|
id: 'accessibility',
|
|
name: 'Accessibility',
|
|
icon: 'Accessibility',
|
|
description: 'Inclusive design for all users',
|
|
},
|
|
{
|
|
id: 'analytics',
|
|
name: 'Analytics',
|
|
icon: 'BarChart3',
|
|
description: 'Data insights and tracking',
|
|
},
|
|
];
|
|
|
|
export const GUIDED_PROMPTS: IdeationPrompt[] = [
|
|
// Feature prompts
|
|
{
|
|
id: 'feature-missing',
|
|
category: 'feature',
|
|
title: 'Missing Features',
|
|
description: 'Discover features users might expect',
|
|
prompt:
|
|
"Analyze this codebase and identify features that users of similar applications typically expect but are missing here. Consider the app's domain, target users, and common patterns in similar products.",
|
|
},
|
|
{
|
|
id: 'feature-automation',
|
|
category: 'feature',
|
|
title: 'Automation Opportunities',
|
|
description: 'Find manual processes that could be automated',
|
|
prompt:
|
|
'Review this codebase and identify manual processes or repetitive tasks that could be automated. Look for patterns where users might be doing things repeatedly that software could handle.',
|
|
},
|
|
{
|
|
id: 'feature-integrations',
|
|
category: 'feature',
|
|
title: 'Integration Ideas',
|
|
description: 'Identify valuable third-party integrations',
|
|
prompt:
|
|
"Based on this codebase, what third-party services or APIs would provide value if integrated? Consider the app's domain and what complementary services users might need.",
|
|
},
|
|
{
|
|
id: 'feature-workflow',
|
|
category: 'feature',
|
|
title: 'Workflow Improvements',
|
|
description: 'Streamline user workflows',
|
|
prompt:
|
|
'Analyze the user workflows in this application. What steps could be combined, eliminated, or automated? Where are users likely spending too much time on repetitive tasks?',
|
|
},
|
|
|
|
// UX/UI prompts
|
|
{
|
|
id: 'ux-friction',
|
|
category: 'ux-ui',
|
|
title: 'Friction Points',
|
|
description: 'Identify where users might get stuck',
|
|
prompt:
|
|
'Analyze the user flows in this codebase and identify potential friction points. Where might users get confused, stuck, or frustrated? Look at form submissions, navigation, error states, and complex interactions.',
|
|
},
|
|
{
|
|
id: 'ux-empty-states',
|
|
category: 'ux-ui',
|
|
title: 'Empty States',
|
|
description: 'Improve empty state experiences',
|
|
prompt:
|
|
"Review the components in this codebase and identify empty states that could be improved. How can we guide users when there's no content? Consider onboarding, helpful prompts, and sample data.",
|
|
},
|
|
{
|
|
id: 'ux-accessibility',
|
|
category: 'ux-ui',
|
|
title: 'Accessibility Improvements',
|
|
description: 'Enhance accessibility and inclusivity',
|
|
prompt:
|
|
'Analyze this codebase for accessibility improvements. Consider keyboard navigation, screen reader support, color contrast, focus states, and ARIA labels. What specific improvements would make this more accessible?',
|
|
},
|
|
{
|
|
id: 'ux-mobile',
|
|
category: 'ux-ui',
|
|
title: 'Mobile Experience',
|
|
description: 'Optimize for mobile users',
|
|
prompt:
|
|
'Review this codebase from a mobile-first perspective. What improvements would enhance the mobile user experience? Consider touch targets, responsive layouts, and mobile-specific interactions.',
|
|
},
|
|
{
|
|
id: 'ux-feedback',
|
|
category: 'ux-ui',
|
|
title: 'User Feedback',
|
|
description: 'Improve feedback and status indicators',
|
|
prompt:
|
|
'Analyze how this application communicates with users. Where are loading states, success messages, or error handling missing or unclear? What feedback would help users understand what is happening?',
|
|
},
|
|
|
|
// DX prompts
|
|
{
|
|
id: 'dx-documentation',
|
|
category: 'dx',
|
|
title: 'Documentation Gaps',
|
|
description: 'Identify missing documentation',
|
|
prompt:
|
|
'Review this codebase and identify areas lacking documentation. What would help new developers understand the architecture, APIs, and conventions? Consider inline comments, READMEs, and API docs.',
|
|
},
|
|
{
|
|
id: 'dx-testing',
|
|
category: 'dx',
|
|
title: 'Testing Improvements',
|
|
description: 'Enhance test coverage and quality',
|
|
prompt:
|
|
'Analyze the testing patterns in this codebase. What areas need better test coverage? What types of tests are missing? Consider unit tests, integration tests, and end-to-end tests.',
|
|
},
|
|
{
|
|
id: 'dx-tooling',
|
|
category: 'dx',
|
|
title: 'Developer Tooling',
|
|
description: 'Improve development workflows',
|
|
prompt:
|
|
'Review the development setup and tooling in this codebase. What improvements would speed up development? Consider build times, hot reload, debugging tools, and developer scripts.',
|
|
},
|
|
{
|
|
id: 'dx-error-handling',
|
|
category: 'dx',
|
|
title: 'Error Handling',
|
|
description: 'Improve error messages and debugging',
|
|
prompt:
|
|
'Analyze error handling in this codebase. Where are error messages unclear or missing? What would help developers debug issues faster? Consider logging, error boundaries, and stack traces.',
|
|
},
|
|
|
|
// Growth prompts
|
|
{
|
|
id: 'growth-onboarding',
|
|
category: 'growth',
|
|
title: 'Onboarding Flow',
|
|
description: 'Improve new user experience',
|
|
prompt:
|
|
"Analyze this application's onboarding experience. How can we help new users understand the value and get started quickly? Consider tutorials, progressive disclosure, and quick wins.",
|
|
},
|
|
{
|
|
id: 'growth-engagement',
|
|
category: 'growth',
|
|
title: 'User Engagement',
|
|
description: 'Increase user retention and activity',
|
|
prompt:
|
|
'Review this application and suggest features that would increase user engagement and retention. What would bring users back daily? Consider notifications, streaks, social features, and personalization.',
|
|
},
|
|
{
|
|
id: 'growth-sharing',
|
|
category: 'growth',
|
|
title: 'Shareability',
|
|
description: 'Make the app more shareable',
|
|
prompt:
|
|
'How can this application be made more shareable? What features would encourage users to invite others or share their work? Consider collaboration, public profiles, and export features.',
|
|
},
|
|
{
|
|
id: 'growth-monetization',
|
|
category: 'growth',
|
|
title: 'Monetization Ideas',
|
|
description: 'Identify potential revenue streams',
|
|
prompt:
|
|
'Based on this codebase, what features or tiers could support monetization? Consider premium features, usage limits, team features, and integrations that users would pay for.',
|
|
},
|
|
|
|
// Technical prompts
|
|
{
|
|
id: 'tech-performance',
|
|
category: 'technical',
|
|
title: 'Performance Optimization',
|
|
description: 'Identify performance bottlenecks',
|
|
prompt:
|
|
'Analyze this codebase for performance optimization opportunities. Where are the likely bottlenecks? Consider database queries, API calls, bundle size, rendering, and caching strategies.',
|
|
},
|
|
{
|
|
id: 'tech-architecture',
|
|
category: 'technical',
|
|
title: 'Architecture Review',
|
|
description: 'Evaluate and improve architecture',
|
|
prompt:
|
|
'Review the architecture of this codebase. What improvements would make it more maintainable, scalable, or testable? Consider separation of concerns, dependency management, and patterns.',
|
|
},
|
|
{
|
|
id: 'tech-debt',
|
|
category: 'technical',
|
|
title: 'Technical Debt',
|
|
description: 'Identify areas needing refactoring',
|
|
prompt:
|
|
'Identify technical debt in this codebase. What areas are becoming hard to maintain or understand? What refactoring would have the highest impact? Consider duplicated code, complexity, and outdated patterns.',
|
|
},
|
|
{
|
|
id: 'tech-security',
|
|
category: 'technical',
|
|
title: 'Security Review',
|
|
description: 'Identify security improvements',
|
|
prompt:
|
|
'Review this codebase for security improvements. What best practices are missing? Consider authentication, authorization, input validation, and data protection. Note: This is for improvement suggestions, not a security audit.',
|
|
},
|
|
|
|
// Security prompts
|
|
{
|
|
id: 'security-auth',
|
|
category: 'security',
|
|
title: 'Authentication Security',
|
|
description: 'Review authentication mechanisms',
|
|
prompt:
|
|
'Analyze the authentication system in this codebase. What security improvements would strengthen user authentication? Consider password policies, session management, MFA, and token handling.',
|
|
},
|
|
{
|
|
id: 'security-data',
|
|
category: 'security',
|
|
title: 'Data Protection',
|
|
description: 'Protect sensitive user data',
|
|
prompt:
|
|
'Review how this application handles sensitive data. What improvements would better protect user privacy? Consider encryption, data minimization, secure storage, and data retention policies.',
|
|
},
|
|
{
|
|
id: 'security-input',
|
|
category: 'security',
|
|
title: 'Input Validation',
|
|
description: 'Prevent injection attacks',
|
|
prompt:
|
|
'Analyze input handling in this codebase. Where could input validation be strengthened? Consider SQL injection, XSS, command injection, and file upload vulnerabilities.',
|
|
},
|
|
{
|
|
id: 'security-api',
|
|
category: 'security',
|
|
title: 'API Security',
|
|
description: 'Secure API endpoints',
|
|
prompt:
|
|
'Review the API security in this codebase. What improvements would make the API more secure? Consider rate limiting, authorization, CORS, and request validation.',
|
|
},
|
|
|
|
// Performance prompts
|
|
{
|
|
id: 'perf-frontend',
|
|
category: 'performance',
|
|
title: 'Frontend Performance',
|
|
description: 'Optimize UI rendering and loading',
|
|
prompt:
|
|
'Analyze the frontend performance of this application. What optimizations would improve load times and responsiveness? Consider bundle splitting, lazy loading, memoization, and render optimization.',
|
|
},
|
|
{
|
|
id: 'perf-backend',
|
|
category: 'performance',
|
|
title: 'Backend Performance',
|
|
description: 'Optimize server-side operations',
|
|
prompt:
|
|
'Review backend performance in this codebase. What optimizations would improve response times? Consider database queries, caching strategies, async operations, and resource pooling.',
|
|
},
|
|
{
|
|
id: 'perf-database',
|
|
category: 'performance',
|
|
title: 'Database Optimization',
|
|
description: 'Improve query performance',
|
|
prompt:
|
|
'Analyze database interactions in this codebase. What optimizations would improve data access performance? Consider indexing, query optimization, denormalization, and connection pooling.',
|
|
},
|
|
{
|
|
id: 'perf-caching',
|
|
category: 'performance',
|
|
title: 'Caching Strategies',
|
|
description: 'Implement effective caching',
|
|
prompt:
|
|
'Review caching opportunities in this application. Where would caching provide the most benefit? Consider API responses, computed values, static assets, and session data.',
|
|
},
|
|
|
|
// Accessibility prompts
|
|
{
|
|
id: 'a11y-keyboard',
|
|
category: 'accessibility',
|
|
title: 'Keyboard Navigation',
|
|
description: 'Enable full keyboard access',
|
|
prompt:
|
|
'Analyze keyboard accessibility in this codebase. What improvements would enable users to navigate entirely with keyboard? Consider focus management, tab order, and keyboard shortcuts.',
|
|
},
|
|
{
|
|
id: 'a11y-screen-reader',
|
|
category: 'accessibility',
|
|
title: 'Screen Reader Support',
|
|
description: 'Improve screen reader experience',
|
|
prompt:
|
|
'Review screen reader compatibility in this application. What improvements would help users with visual impairments? Consider ARIA labels, semantic HTML, live regions, and alt text.',
|
|
},
|
|
{
|
|
id: 'a11y-visual',
|
|
category: 'accessibility',
|
|
title: 'Visual Accessibility',
|
|
description: 'Improve visual design for all users',
|
|
prompt:
|
|
'Analyze visual accessibility in this codebase. What improvements would help users with visual impairments? Consider color contrast, text sizing, focus indicators, and reduced motion.',
|
|
},
|
|
{
|
|
id: 'a11y-forms',
|
|
category: 'accessibility',
|
|
title: 'Accessible Forms',
|
|
description: 'Make forms usable for everyone',
|
|
prompt:
|
|
'Review form accessibility in this application. What improvements would make forms more accessible? Consider labels, error messages, required field indicators, and input assistance.',
|
|
},
|
|
|
|
// Analytics prompts
|
|
{
|
|
id: 'analytics-tracking',
|
|
category: 'analytics',
|
|
title: 'User Tracking',
|
|
description: 'Track key user behaviors',
|
|
prompt:
|
|
'Analyze this application for analytics opportunities. What user behaviors should be tracked to understand engagement? Consider page views, feature usage, conversion funnels, and session duration.',
|
|
},
|
|
{
|
|
id: 'analytics-metrics',
|
|
category: 'analytics',
|
|
title: 'Key Metrics',
|
|
description: 'Define success metrics',
|
|
prompt:
|
|
'Based on this codebase, what key metrics should be tracked? Consider user acquisition, retention, engagement, and feature adoption. What dashboards would be most valuable?',
|
|
},
|
|
{
|
|
id: 'analytics-errors',
|
|
category: 'analytics',
|
|
title: 'Error Monitoring',
|
|
description: 'Track and analyze errors',
|
|
prompt:
|
|
'Review error handling in this codebase for monitoring opportunities. What error tracking would help identify and fix issues faster? Consider error aggregation, alerting, and stack traces.',
|
|
},
|
|
{
|
|
id: 'analytics-performance',
|
|
category: 'analytics',
|
|
title: 'Performance Monitoring',
|
|
description: 'Track application performance',
|
|
prompt:
|
|
'Analyze this application for performance monitoring opportunities. What metrics would help identify bottlenecks? Consider load times, API response times, and resource usage.',
|
|
},
|
|
];
|
|
|
|
export function getPromptsByCategory(category: IdeaCategory): IdeationPrompt[] {
|
|
return GUIDED_PROMPTS.filter((p) => p.category === category);
|
|
}
|
|
|
|
export function getPromptById(id: string): IdeationPrompt | undefined {
|
|
return GUIDED_PROMPTS.find((p) => p.id === id);
|
|
}
|
|
|
|
export function getCategoryById(id: IdeaCategory): PromptCategory | undefined {
|
|
return PROMPT_CATEGORIES.find((c) => c.id === id);
|
|
}
|