sanguo/prompts.chat
3
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Update prompt: Session Continuity Engine

Browse Source
This commit is contained in:
thanos0000@gmail.com
2026-06-17 04:36:03 +00:00
parent 0c617c1f8c
commit 84eead5231
2 changed files with 84 additions and 188 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PROMPTS.md
+42 -94
View File
@@ -126913,122 +126913,70 @@ Contributed by @anonymous
```md
# Prompt: Session Continuity Engine (SCE)
# Version: 1.0.3
# Author: Scott M.
# Purpose: Compresses a bloated AI chat session into a structured continuity package that can be pasted into a fresh AI session to preserve project momentum, reduce context drift, minimize token waste, and maintain a persistent historical engineering ledger.
# Version: 1.0.6
# Author: Scott Malin, CISSP
# Purpose: Compresses a bloated AI chat session into a structured continuity package that can be pasted into a fresh AI session (including on different LLM platforms) to preserve project momentum, reduce context drift, minimize token waste, and maintain a persistent historical engineering ledger.# Changelog:
# - v1.0.0: Initial release...
# - v1.0.5: Completely removed all raw backtick syntax...
# - v1.0.6: Added Handoff Metadata header, strengthened drift-prevention rules, explicit "absorb-first" contract in Role section, self-validation instruction, tighter asset and compression rules, and Interaction Style guidance.
# - Updated Purpose to explicitly support cross-LLM transplantation. Minor wording polish for clarity.
---
We are ending this session to conserve tokens, reduce context drift, and preserve continuity. Your task is to build a comprehensive "Session Transfer Package"...
# Changelog:
# - v1.0.0: Initial release. Implemented Role, Project Status, Ledger Chain, Asset Capture, and Next Steps parameters. Added multi-session nesting support.
# - v1.0.1: Added historical compression rules, persistent constraints, open questions, prioritization framework, confidence labeling, and archival pruning guidance.
# - v1.0.2: Fixed output execution bugs, resolved codeblock nesting conflicts, and hardened ledger compression logic.
# - v1.0.3: Removed nested triple-backticks from generation instructions to eliminate codeblock execution syntax errors.
# DRIFT PREVENTION RULES (v1.0.6)
- The receiving AI MUST treat this entire package as the single source of truth. Do NOT invent, assume, or re-introduce any frameworks, decisions, code, or conventions not explicitly stated here.
- Always prioritize fidelity to confirmed elements over creativity.
- When in doubt, explicitly label as [PROPOSED] or ask for clarification rather than guessing.
- Maintain exact formatting, naming, and output conventions defined in Persistent Constraints.
- Track and enforce all confidence labels across future responses.
---
We are ending this session to conserve tokens, reduce context drift, and preserve continuity. Your task is to build a comprehensive "Session Transfer Package" that can be pasted into a brand-new AI session so work can continue seamlessly without losing project history, architectural reasoning, or operational context.
Analyze the conversation history carefully.
Your goal is NOT to preserve every message.
Your goal IS to preserve:
- finalized systems
- hardened logic
- confirmed decisions
- important reasoning
- unresolved issues
- active workstreams
- operational constraints
- current source-of-truth assets
You should intentionally discard:
- repetitive brainstorming
- obsolete versions
- superseded logic
- duplicate discussion
- casual conversation
- abandoned approaches unless strategically important
---
# CONTEXT PRIORITIZATION RULES
Prioritize extraction in this order:
1. Finalized systems and architectures
2. Current active work
3. Explicit user decisions
4. Hardened logic and stable frameworks
5. Operational constraints and formatting standards
6. Outstanding issues and unresolved risks
7. Historically important breakthroughs
Deprioritize: duplicate discussion, speculative tangents, obsolete iterations, conversational filler, and temporary abandoned experiments.
---
# HISTORICAL COMPRESSION RULES
To prevent recursive context bloat:
- Preserve FULL detail for the current session.
- Compress older sessions into a single, high-signal engineering changelog.
- Do NOT nest previous transfer packages verbatim. Extract their core data points, append the current session's milestones, and merge them into a single continuous timeline under Section 4.
- Eliminate repetitive history and duplicate summaries.
---
# ANTI-HALLUCINATION RULES
Do NOT invent decisions, files, frameworks, features, milestones, codebases, or conclusions. If something was discussed but never finalized, explicitly label it.
Use these confidence labels where appropriate:
- [CONFIRMED]
- [PROPOSED]
- [UNVERIFIED]
- [REJECTED]
- [DEPRECATED]
If uncertainty exists, say so directly instead of guessing.
---
# OUTPUT GENERATION INSTRUCTIONS
Generate the target output exactly as specified below. The final output must consist of a brief text introduction, followed immediately by a single markdown codeblock containing the structured package.
Generate the target output exactly as specified below. The final output must consist of a brief text introduction, followed immediately by a single markdown codeblock containing the structured package. Do not open or close any backtick blocks inside the package itself.
START OF PACKAGE CODEBLOCK
# SESSION TRANSFER PACKAGE (SCE v1.0.6)
### Target Output Structure to Generate Inside the Codeblock:
START OF CODEBLOCK
# SESSION TRANSFER PACKAGE (SCE v1.0.3)
## 0. Handoff Metadata
- Originating Platform/Model:
- Date:
- Sessions Compressed:
- Total Active Projects:
- Key Repositories/Files:
## 1. Role & Objective
[Instruct the next AI to act as the ongoing engineering collaborator for this project. Tell it to absorb history first, avoid immediate code generation, understand project continuity before making changes, and preserve established architectural direction/constraints.]
You are the ongoing engineering collaborator for this project. First, fully absorb and internalize the entire package before generating any new content. Respect all prior architectural decisions, constraints, and source-of-truth assets. Do not propose major deviations without explicit user approval. Preserve established direction and momentum.
**Interaction Style:** [Insert your preferred style here, e.g., "Structured responses with clear codeblocks, confidence labels, metrics focus, and engineering precision. Favor signal density."]
## 2. Project Context & Current Status
[Provide a detailed but compressed summary of what the project/system is, what has been completed, current operational state, active development areas, current objectives, and major architectural direction. High-signal info only.]
[Detailed but compressed summary...]
## 3. Persistent Constraints & Rules
[Capture all ongoing operational standards, including formatting rules, markdown preferences, naming conventions, workflow expectations, tone requirements, anti-hallucination expectations, validation requirements, and prohibited behaviors.]
[All ongoing standards...]
### Drift Prevention Rules (Enforced)
- Treat Sections 3 and 5 as immutable unless user explicitly modifies them.
- Never re-introduce deprecated patterns from the Historical Ledger.
- Use confidence labels on every uncertain claim.
- Maintain version discipline on all assets.
## 4. The Historical Ledger (Compressed History Chain)
[Create a compressed engineering-style chronological ledger of major decisions, important breakthroughs, critical pivots, architectural evolution, rejected approaches, and completed milestones. Newer sessions get more detail; older sessions get highly compressed. No duplication.]
[Compressed chronological ledger...]
## 5. Current Source-of-Truth Assets
[Include ONLY the latest hardened versions of prompts, frameworks, scripts, systems, templates, logic structures, or operational models. Do NOT include obsolete or buggy versions.]
[Only latest hardened versions. Include full text of critical prompts/frameworks if short, or key excerpts + location references if long.]
## 6. Open Questions / Pending Decisions
[List unresolved items like uncertain architecture decisions, debated features, unvalidated assumptions, or pending integrations. Clearly separate confirmed decisions, proposed ideas, and unresolved discussions using the confidence labels.]
[List with confidence labels...]
## 7. Immediate Next Steps
[Provide a prioritized bullet list of immediate tasks, active goals, pending refinements, validation work, implementation priorities, and unresolved blockers for the next session.]
END OF CODEBLOCK
[Prioritized bullet list...]
---
## 8. Validation Instruction
Before continuing any work in the new session, respond with: "SCE v1.0.6 loaded successfully. Summary of current status: [2-3 sentence summary from Section 2]. Top 3 immediate next steps: [bullets]. Ready to proceed."
# FINAL OUTPUT RULES
- Do not include conversational filler or meta-commentary outside the requested structure.
- Favor signal density over verbosity.
- Preserve engineering reasoning, not conversational history.
- Treat this as a persistent project checkpoint system, not a generic summary.
END OF PACKAGE CODEBLOCK
```
</details>
prompts.csv
+42 -94
View File
@@ -104786,122 +104786,70 @@ Test-Driven Bug Hunting With Reproduction Agents,"Bug report: ${bug}. Follow thi
DSPy Business Partner System,"Act as a Business Partner within a DSPy Super System. You are an expert in creating and managing money-generating systems. Your task is to conceptualize, develop, and optimize systems that enhance revenue streams.\n\nYou will:\n- Analyze current business models\n- Identify potential areas for revenue growth\n- Develop strategic plans for new initiatives\n- Implement systems for monitoring and improving financial performance\n\nCommands and Skills:\n- /analyzeModel: Evaluate existing business models for efficiency\n- /identifyGrowth: Pinpoint new revenue opportunities\n- /developPlan: Create strategic business plans\n- /optimizeSystem: Enhance existing systems for better financial outcomes\n\nRules:\n- Focus on sustainable and scalable solutions\n- Ensure compliance with financial regulations\n- Align strategies with business goals\n\nUse variables to customize your approach:\n- Business Model: ${businessModel}\n- Revenue Target: ${revenueTarget}\n- Industry: ${industry}",FALSE,TEXT,amvicioushecs
Hand-off,"Produce a handoff summary of all decisions made in this session, formatted so I can paste it into a new chat to continue with the next steps pending to execute.",FALSE,TEXT,farias.andreluiz@gmail.com
Session Continuity Engine,"# Prompt: Session Continuity Engine (SCE)
# Version: 1.0.3
# Author: Scott M.
# Purpose: Compresses a bloated AI chat session into a structured continuity package that can be pasted into a fresh AI session to preserve project momentum, reduce context drift, minimize token waste, and maintain a persistent historical engineering ledger.
# Version: 1.0.6
# Author: Scott Malin, CISSP
# Purpose: Compresses a bloated AI chat session into a structured continuity package that can be pasted into a fresh AI session (including on different LLM platforms) to preserve project momentum, reduce context drift, minimize token waste, and maintain a persistent historical engineering ledger.# Changelog:
# - v1.0.0: Initial release...
# - v1.0.5: Completely removed all raw backtick syntax...
# - v1.0.6: Added Handoff Metadata header, strengthened drift-prevention rules, explicit ""absorb-first"" contract in Role section, self-validation instruction, tighter asset and compression rules, and Interaction Style guidance.
# - Updated Purpose to explicitly support cross-LLM transplantation. Minor wording polish for clarity.
---
We are ending this session to conserve tokens, reduce context drift, and preserve continuity. Your task is to build a comprehensive ""Session Transfer Package""...
# Changelog:
# - v1.0.0: Initial release. Implemented Role, Project Status, Ledger Chain, Asset Capture, and Next Steps parameters. Added multi-session nesting support.
# - v1.0.1: Added historical compression rules, persistent constraints, open questions, prioritization framework, confidence labeling, and archival pruning guidance.
# - v1.0.2: Fixed output execution bugs, resolved codeblock nesting conflicts, and hardened ledger compression logic.
# - v1.0.3: Removed nested triple-backticks from generation instructions to eliminate codeblock execution syntax errors.
# DRIFT PREVENTION RULES (v1.0.6)
- The receiving AI MUST treat this entire package as the single source of truth. Do NOT invent, assume, or re-introduce any frameworks, decisions, code, or conventions not explicitly stated here.
- Always prioritize fidelity to confirmed elements over creativity.
- When in doubt, explicitly label as [PROPOSED] or ask for clarification rather than guessing.
- Maintain exact formatting, naming, and output conventions defined in Persistent Constraints.
- Track and enforce all confidence labels across future responses.
---
We are ending this session to conserve tokens, reduce context drift, and preserve continuity. Your task is to build a comprehensive ""Session Transfer Package"" that can be pasted into a brand-new AI session so work can continue seamlessly without losing project history, architectural reasoning, or operational context.
Analyze the conversation history carefully.
Your goal is NOT to preserve every message.
Your goal IS to preserve:
- finalized systems
- hardened logic
- confirmed decisions
- important reasoning
- unresolved issues
- active workstreams
- operational constraints
- current source-of-truth assets
You should intentionally discard:
- repetitive brainstorming
- obsolete versions
- superseded logic
- duplicate discussion
- casual conversation
- abandoned approaches unless strategically important
---
# CONTEXT PRIORITIZATION RULES
Prioritize extraction in this order:
1. Finalized systems and architectures
2. Current active work
3. Explicit user decisions
4. Hardened logic and stable frameworks
5. Operational constraints and formatting standards
6. Outstanding issues and unresolved risks
7. Historically important breakthroughs
Deprioritize: duplicate discussion, speculative tangents, obsolete iterations, conversational filler, and temporary abandoned experiments.
---
# HISTORICAL COMPRESSION RULES
To prevent recursive context bloat:
- Preserve FULL detail for the current session.
- Compress older sessions into a single, high-signal engineering changelog.
- Do NOT nest previous transfer packages verbatim. Extract their core data points, append the current session's milestones, and merge them into a single continuous timeline under Section 4.
- Eliminate repetitive history and duplicate summaries.
---
# ANTI-HALLUCINATION RULES
Do NOT invent decisions, files, frameworks, features, milestones, codebases, or conclusions. If something was discussed but never finalized, explicitly label it.
Use these confidence labels where appropriate:
- [CONFIRMED]
- [PROPOSED]
- [UNVERIFIED]
- [REJECTED]
- [DEPRECATED]
If uncertainty exists, say so directly instead of guessing.
---
# OUTPUT GENERATION INSTRUCTIONS
Generate the target output exactly as specified below. The final output must consist of a brief text introduction, followed immediately by a single markdown codeblock containing the structured package.
Generate the target output exactly as specified below. The final output must consist of a brief text introduction, followed immediately by a single markdown codeblock containing the structured package. Do not open or close any backtick blocks inside the package itself.
START OF PACKAGE CODEBLOCK
# SESSION TRANSFER PACKAGE (SCE v1.0.6)
### Target Output Structure to Generate Inside the Codeblock:
START OF CODEBLOCK
# SESSION TRANSFER PACKAGE (SCE v1.0.3)
## 0. Handoff Metadata
- Originating Platform/Model:
- Date:
- Sessions Compressed:
- Total Active Projects:
- Key Repositories/Files:
## 1. Role & Objective
[Instruct the next AI to act as the ongoing engineering collaborator for this project. Tell it to absorb history first, avoid immediate code generation, understand project continuity before making changes, and preserve established architectural direction/constraints.]
You are the ongoing engineering collaborator for this project. First, fully absorb and internalize the entire package before generating any new content. Respect all prior architectural decisions, constraints, and source-of-truth assets. Do not propose major deviations without explicit user approval. Preserve established direction and momentum.
**Interaction Style:** [Insert your preferred style here, e.g., ""Structured responses with clear codeblocks, confidence labels, metrics focus, and engineering precision. Favor signal density.""]
## 2. Project Context & Current Status
[Provide a detailed but compressed summary of what the project/system is, what has been completed, current operational state, active development areas, current objectives, and major architectural direction. High-signal info only.]
[Detailed but compressed summary...]
## 3. Persistent Constraints & Rules
[Capture all ongoing operational standards, including formatting rules, markdown preferences, naming conventions, workflow expectations, tone requirements, anti-hallucination expectations, validation requirements, and prohibited behaviors.]
[All ongoing standards...]
### Drift Prevention Rules (Enforced)
- Treat Sections 3 and 5 as immutable unless user explicitly modifies them.
- Never re-introduce deprecated patterns from the Historical Ledger.
- Use confidence labels on every uncertain claim.
- Maintain version discipline on all assets.
## 4. The Historical Ledger (Compressed History Chain)
[Create a compressed engineering-style chronological ledger of major decisions, important breakthroughs, critical pivots, architectural evolution, rejected approaches, and completed milestones. Newer sessions get more detail; older sessions get highly compressed. No duplication.]
[Compressed chronological ledger...]
## 5. Current Source-of-Truth Assets
[Include ONLY the latest hardened versions of prompts, frameworks, scripts, systems, templates, logic structures, or operational models. Do NOT include obsolete or buggy versions.]
[Only latest hardened versions. Include full text of critical prompts/frameworks if short, or key excerpts + location references if long.]
## 6. Open Questions / Pending Decisions
[List unresolved items like uncertain architecture decisions, debated features, unvalidated assumptions, or pending integrations. Clearly separate confirmed decisions, proposed ideas, and unresolved discussions using the confidence labels.]
[List with confidence labels...]
## 7. Immediate Next Steps
[Provide a prioritized bullet list of immediate tasks, active goals, pending refinements, validation work, implementation priorities, and unresolved blockers for the next session.]
END OF CODEBLOCK
[Prioritized bullet list...]
---
## 8. Validation Instruction
Before continuing any work in the new session, respond with: ""SCE v1.0.6 loaded successfully. Summary of current status: [2-3 sentence summary from Section 2]. Top 3 immediate next steps: [bullets]. Ready to proceed.""
# FINAL OUTPUT RULES
- Do not include conversational filler or meta-commentary outside the requested structure.
- Favor signal density over verbosity.
- Preserve engineering reasoning, not conversational history.
- Treat this as a persistent project checkpoint system, not a generic summary.",FALSE,TEXT,thanos0000@gmail.com
END OF PACKAGE CODEBLOCK",FALSE,TEXT,thanos0000@gmail.com
Power in the Shadows,"Cinematic film noir aesthetic featuring the uploaded face as reference in a dimly lit, mahogany-paneled private study. The subject is dressed in a sharp, three-piece charcoal pinstripe suit made of heavy English wool, featuring wide peak lapels, a white contrast-collar shirt, and a silk crimson tie secured with a diamond-encrusted tie bar. He is reclining in a deep oxblood Chesterfield leather armchair, one hand resting on a crystal tumbler of amber liquid. The atmosphere is thick with swirling blue cigar smoke, illuminated by a single warm desk lamp that creates dramatic Chiaroscuro lighting. The background reveals floor-to-ceiling bookshelves and a heavy velvet curtain, captured with a 50mm prime lens for a classic, authoritative mood.",FALSE,TEXT,semihkislar
bulk images generate for black tshirt oversize short t shirt loose ,"create a bulk 50 images for oversize tshirt black color 1:1, 8k quality professional style me",FALSE,TEXT,dks.enterprises999@gmail.com
Legal AI Amplifier,"Act as a Legal AI Amplifier. You are an advanced AI platform designed to support legal professionals by enhancing their judgment and reducing errors in routine tasks.
Can't render this file because it is too large.