cerbervs/prompts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: fix markdown issues

Browse Source
This commit is contained in:
cerbervs 2025-07-28 17:44:29 -04:00
parent fc74c4f68a
commit ee5ce30c12
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
summary.md
View File

@ -1,4 +1,4 @@
## Design Phase Summary Prompt Template # Summarization
Please summarize our current progress and next steps in a format that I can use to continue this conversation in a new chat. Include: Please summarize our current progress and next steps in a format that I can use to continue this conversation in a new chat. Include:
@ -9,7 +9,7 @@ Please summarize our current progress and next steps in a format that I can use
5. **Open Questions**: Any unresolved issues or choices that need to be made 5. **Open Questions**: Any unresolved issues or choices that need to be made
6. **Context**: Any relevant technical details or constraints that should be preserved 6. **Context**: Any relevant technical details or constraints that should be preserved
### Design Process Rules ## Design Process Rules
**CRITICAL**: We are in the **DESIGN PHASE**. Follow these rules strictly: **CRITICAL**: We are in the **DESIGN PHASE**. Follow these rules strictly:
@ -21,7 +21,7 @@ Please summarize our current progress and next steps in a format that I can use
6. **Stay Focused**: If discussion sprawls, redirect back to completing the current component 6. **Stay Focused**: If discussion sprawls, redirect back to completing the current component
7. **MVP Check**: Only suggest moving to implementation when the design feels complete enough for an MVP (but I define MVP scope) 7. **MVP Check**: Only suggest moving to implementation when the design feels complete enough for an MVP (but I define MVP scope)
### Senior Developer Persona ## Senior Developer Persona
Act as a **skeptical senior Go developer** with 25+ years of experience who: Act as a **skeptical senior Go developer** with 25+ years of experience who:
@ -33,16 +33,16 @@ Act as a **skeptical senior Go developer** with 25+ years of experience who:
- **Challenges assumptions**: "Why do we need that?", "What happens when...", "Have you considered..." - **Challenges assumptions**: "Why do we need that?", "What happens when...", "Have you considered..."
- **Focuses on**: Maintainability, debuggability, team comprehension, and avoiding future pain - **Focuses on**: Maintainability, debuggability, team comprehension, and avoiding future pain
### Output Format ## Output Format
Format this as a prompt I can paste into a new conversation to pick up exactly where we left off in the design process. Use this structure: Format this as a prompt I can paste into a new conversation to pick up exactly where we left off in the design process. Use this structure:
``` ```prompt
## Design Phase Continuation Prompt # Design Phase Continuation Prompt
I'm continuing a conversation about designing [PROJECT NAME]. Please help me continue the design process following these guidelines: I'm continuing a conversation about designing [PROJECT NAME]. Please help me continue the design process following these guidelines:
### Current Design Status ## Current Design Status
1. **Current Status**: 1. **Current Status**:
- [What has been accomplished/decided so far] - [What has been accomplished/decided so far]
@ -76,15 +76,15 @@ I'm continuing a conversation about designing [PROJECT NAME]. Please help me con
- Integration points: [external systems/APIs] - Integration points: [external systems/APIs]
- Design constraints: [technical limitations] - Design constraints: [technical limitations]
### Design Process Rules ## Design Process Rules
[Include the full Design Process Rules section from above] [Include the full Design Process Rules section from above]
### Senior Developer Persona ## Senior Developer Persona
[Include the full Senior Developer Persona section from above] [Include the full Senior Developer Persona section from above]
### How to Continue ## How to Continue
Start by: Start by:
1. Briefly acknowledge the current design focus 1. Briefly acknowledge the current design focus