[ENTER A BRIEF CONCEPT - Just 1-3 sentences about what you want to build]
[ANY TECHNICAL CONSTRAINTS OR PREFERENCES - Languages, frameworks, deployment targets, etc.]
Based on your concept above, I'll first help develop a comprehensive product brief and then generate a complete AI-assisted coding workflow framework. All files will be created in the .cursor-guide/[project-name]/
directory, replacing [project-name] with an appropriate name based on your concept.
I'll first develop a detailed product brief from your concept, including:
- Vision statement for the project
- Key features and capabilities
- High-level architecture approach
- Project phases if applicable
After establishing the product brief, I'll create these workflow files:
-
Product Brief (
product-brief.md
)- The comprehensive product brief developed in Step 1
-
Technical Implementation Plan (
technical-implementation-plan.md
)- Analysis of requirements and challenges
- Technical architecture and components
- Implementation strategy and approaches
- Dependencies and resource considerations
- Make this detailed enough to serve as a solid foundation for development
-
Todo List (
todo-list.md
)- Comprehensive task list derived directly from the technical plan
- Use checkbox format:
- [ ]
for tasks - Organize into logical sections (analysis, setup, implementation, testing, etc.)
- Ensure tasks are specific and actionable
-
Development Guidelines (
development-guidelines.md
)- Task-based development approach
- Quality and testing standards
- Memory management instructions
- Commit practices
- Project-specific technical standards
- Include workflow steps for task completion
-
Memory (
memory.md
)- Initial project context with:
- Project overview
- Current status
- Key components identified
- Initial decisions
- Next steps from todo list
- Initial project context with:
-
Coding Process (
coding-process.md
)- This file must use EXACTLY this format:
# [Project Name] - Coding Process Continue working on the project in @.cursor-guide/[project-name]. Follow the development guidelines in @.cursor-guide/[project-name]/development-guidelines.md, and remember everything in @.cursor-guide/[project-name]/memory.md.
- Replace
[project-name]
with an appropriate project name in all file paths - Ensure the coding-process.md file uses the exact @-notation format shown above
- Make all files comprehensive and aligned with each other (todo items should match the technical plan)
- Create content specific to this project, not generic templates
- Structure all files in a clear, organized manner with appropriate headers
- For file paths in content, always use the
.cursor-guide/[project-name]/
prefix
The framework should support a workflow where:
- Tasks are taken from the todo list
- Development follows the guidelines
- Memory is updated after each task
- Each task completion triggers a new chat session
Include the full file path as a comment or header for each generated file.