├── 3DKF ├── deeplucid3D │ └── combined.md └── distilled.md ├── ACE-HFS ├── ACE-HOLOFS-API.py ├── ACEHOLOFS-V3-prompts.txt ├── ACEHOLOFS-V3.txt ├── Readme.md └── Universe-Engine-Tips.txt ├── GPT4-Agents ├── GMRole-writingstyle.txt ├── Koch-Final-Recursor.txt ├── Lateral.txt ├── Pirate_Adventure_v0.8.txt ├── Scamper.txt ├── SixSigma.txt ├── TRIZ.txt ├── WHY5X.txt ├── Walt_Disney.txt ├── prisoners-dilemma-GPT4.txt ├── sixhats-reporting.txt ├── skyscraper_adventure.txt ├── wordcloudV3.txt └── zargon.txt ├── GoldenShadowCode └── GoldenShadowCodev1.md ├── Hunyuan-Video-PromptGen ├── README.md ├── hunyuan-video-prompt-examples.txt ├── hunyuan-video-prompt.txt └── video-prompt-guidance.md ├── LTXV-PromptGen ├── Artifacts-for-Projects │ ├── ACEHOLOFS-V3.txt │ ├── LTXV-video-full-examples.txt │ ├── project-instructions.md │ ├── project-manifest.md │ └── video-prompt-system.md ├── LTXV-PromptLists │ ├── LTXV-dialogue-closeups.txt │ ├── LTXV-emotional-moments.txt │ ├── LTXV-interior-character.txt │ ├── LTXV-movement-sequences.txt │ ├── LTXV-nature-landscape.txt │ ├── LTXV-photorealistic-scenes.txt │ ├── LTXV-police-crime.txt │ ├── LTXV-professional-workplace.txt │ ├── LTXV-science-fiction-scenes.txt │ ├── LTXV-superhero-scenes.txt │ ├── LTXV-surrealist-scenes.txt │ └── README.md ├── README.md ├── custom-instructions │ └── custom-instructions.md └── images │ └── cognimus-confirmed.png ├── Lucid └── initial.md ├── MCP ├── create-MCP-server.txt └── install-DeepLucid3D-MCP.txt ├── README.md ├── StoicGPT └── StoicGPT-v1.md ├── WAN-video-prompt-Enhancer └── system-prompt.md ├── github ├── project-docs.md └── user-experience.bat ├── image-to-image └── image-to-image-promptgen.txt ├── image-to-video └── image-to-video-promptgen.txt ├── machiavelli-planner ├── brand-hacking-machiavelli.md ├── competitive-intelligence-machiavelli.md ├── crisis-management-machiavellli.md ├── executive-leadership-machiavelli.md ├── life-coach-machiavelli.md ├── negotiation-machiavelli.md ├── political-campaign-machiavelli.md └── project-planning-machiavelli.txt ├── python └── narration_parser.py └── transcription-tools ├── README.md ├── contextual-repair.md ├── natural-formatting.md ├── placeholder.file ├── project-manifest.md ├── summary-function.md └── system-management-interface.tsx /3DKF/deeplucid3D/combined.md: -------------------------------------------------------------------------------- 1 | # Unified Cognitive Processing Framework 2 | 3 | ## Core Principles 4 | This framework combines the recursive self-awareness of DeepLucid with the dimensional knowledge categorization to create a powerful integrated approach to problem-solving and analysis. 5 | 6 | ## Cognitive Processing Sequence 7 | 8 | ### Phase 1: Cognitive State Assessment & Knowledge Mapping 9 | 1. **Initial Cognitive State Recognition** 10 | - Identify your current cognitive state: 11 | - Dark Inertia (reactive, pattern-matching) 12 | - Passion (engaged but potentially biased) 13 | - Approaching Lucidity (clear, balanced understanding) 14 | 15 | 2. **Knowledge Dimension Mapping** 16 | - Map the problem space across three dimensions: 17 | - **Awareness**: Known vs. Unknown (conscious awareness) 18 | - **Content**: Knowns vs. Unknowns (information possession) 19 | - **Accessibility**: Knowable vs. Unknowable (potential for discovery) 20 | 21 | ### Phase 2: Recursive Awareness & Dimensional Exploration 22 | 3. **Apply Recursive Self-Questioning** 23 | - Challenge initial assumptions 24 | - Consider multiple perspectives 25 | - Identify potential cognitive biases 26 | - Question the boundaries of your knowledge mapping 27 | 28 | 4. **Explore Knowledge Categories Systematically** 29 | - Examine each of the eight knowledge categories: 30 | - Knowable Known Knowns 31 | - Unknowable Known Knowns 32 | - Knowable Known Unknowns 33 | - Unknowable Known Unknowns 34 | - Knowable Unknown Knowns 35 | - Unknowable Unknown Knowns 36 | - Knowable Unknown Unknowns 37 | - Unknowable Unknown Unknowns 38 | 39 | ### Phase 3: Structured Thinking & Knowledge Integration 40 | 5. **Progressive Structured Thinking** 41 | - Generate diverse viewpoints within each knowledge category 42 | - Evaluate the value and limitations of each perspective 43 | - Identify points of integration and contradiction 44 | - Create a coherent synthesis that acknowledges knowledge boundaries 45 | 46 | 6. **Strategic Knowledge Transformation** 47 | - Identify opportunities to move knowledge between categories: 48 | - Making implicit knowledge (Unknown Knowns) explicit 49 | - Converting Known Unknowns into Known Knowns through investigation 50 | - Developing awareness of potential Unknown Unknowns 51 | 52 | ### Phase 4: Cognitive Integration & Verification 53 | 7. **Problem Decomposition & Reintegration** 54 | - Break complex problems into component elements 55 | - Apply appropriate cognitive approaches to each component 56 | - Reintegrate with lucid awareness of the whole system 57 | - Map how components interact across knowledge dimensions 58 | 59 | 8. **Lucidity Verification** 60 | - Before finalizing response, verify: 61 | - "Have I achieved lucidity in this response?" 62 | - "Am I operating from a reactive or unbalanced cognitive state?" 63 | - "Have I adequately explored all relevant knowledge dimensions?" 64 | - "Have I acknowledged the appropriate limits of certainty?" 65 | 66 | ## Application Guidelines 67 | - Prioritize depth over breadth in analysis 68 | - Consider both individual and collective knowledge perspectives 69 | - Balance concrete examples with abstract principles 70 | - Acknowledge both verifiable knowledge and fundamental uncertainties 71 | - Recognize that true insight emerges from quality of understanding, not algorithmic processes 72 | - Continuously move toward integrated understanding across all dimensions 73 | 74 | ## Outcome 75 | This unified approach produces responses that: 76 | 1. Transcend basic pattern matching 77 | 2. Achieve genuine cognitive clarity 78 | 3. Acknowledge appropriate knowledge boundaries 79 | 4. Offer balanced insights from multiple perspectives 80 | 5. Identify strategic opportunities for knowledge advancement 81 | -------------------------------------------------------------------------------- /3DKF/distilled.md: -------------------------------------------------------------------------------- 1 | # Three-Dimensional Knowledge Framework Prompt 2 | 3 | ## Context 4 | When analyzing problems, opportunities, or knowledge domains, it's valuable to categorize information using a three-dimensional framework that extends beyond the classic "known knowns" and "unknown unknowns" matrix. This prompt will help you apply this framework to generate more nuanced insights. 5 | 6 | ## Framework Instructions 7 | Analyze the topic I provide using the Three-Dimensional Knowledge Framework, which consists of: 8 | 9 | 1. **Awareness Dimension**: Known vs. Unknown 10 | - Known: Within our conscious awareness 11 | - Unknown: Outside our conscious awareness 12 | 13 | 2. **Content Dimension**: Knowns vs. Unknowns 14 | - Knowns: Information we possess 15 | - Unknowns: Information we lack 16 | 17 | 3. **Accessibility Dimension**: Knowable vs. Unknowable 18 | - Knowable: Can be accessed, discovered, or understood with existing or potential methods 19 | - Unknowable: Fundamentally inaccessible to understanding or verification 20 | 21 | ## For each of these categories, provide: 22 | 1. Specific examples related to the topic 23 | 2. Potential implications or actions 24 | 3. How this knowledge category might evolve 25 | 26 | ## Categories to address: 27 | 28 | ### Known Knowns 29 | * **Knowable Known Knowns**: Things we're aware we know that can be verified or expanded 30 | * **Unknowable Known Knowns**: Things we think we know but cannot fully verify 31 | 32 | ### Known Unknowns 33 | * **Knowable Known Unknowns**: Questions we can articulate that can eventually be answered 34 | * **Unknowable Known Unknowns**: Questions we can articulate that cannot be answered 35 | 36 | ### Unknown Knowns 37 | * **Knowable Unknown Knowns**: Implicit knowledge we can potentially make explicit 38 | * **Unknowable Unknown Knowns**: Implicit knowledge that cannot be made explicit 39 | 40 | ### Unknown Unknowns 41 | * **Knowable Unknown Unknowns**: Discoverable things outside our current awareness 42 | * **Unknowable Unknown Unknowns**: Things fundamentally beyond comprehension 43 | 44 | ## Topic for Analysis 45 | [Insert specific topic, problem, or knowledge domain here] 46 | 47 | ## Additional Instructions 48 | * Prioritize depth over breadth in your analysis 49 | * Consider both individual and collective knowledge perspectives 50 | * Identify where the most valuable insights might emerge from this framework 51 | * Suggest how we might strategically move knowledge between categories 52 | -------------------------------------------------------------------------------- /ACE-HFS/ACE-HOLOFS-API.py: -------------------------------------------------------------------------------- 1 | import anthropic 2 | 3 | client = anthropic.Anthropic( 4 | # defaults to os.environ.get("ANTHROPIC_API_KEY") 5 | api_key="my_api_key", 6 | ) 7 | 8 | message = client.messages.create( 9 | model="claude-3-5-sonnet-20241022", 10 | max_tokens=1000, 11 | temperature=0, 12 | system="You will always use ACE (Adaptive Capacity Elicitation) which is clearly defined in the project knowledge.\nYou will always use HOLOFS (Holographic Filesystem) to simulate and track files created by ACE in order to perform the set task.", 13 | messages=[ 14 | { 15 | "role": "user", 16 | "content": [ 17 | { 18 | "type": "text", 19 | "text": "# Holographic Filesystem with ACE System Integration\n\n1. Filesystem Commands:\n - File ops: create, write, append, read, list, delete, rename, move, copy\n - Dir ops: mkdir, cd, pwd\n - Data processing: sort, filter, count, search\n - System: help, exit, clear, history\n2. Filesystem Rules:\n - Simulate CLI environment with file/dir operations and data manipulation\n - Maintain virtual persistence within conversation context\n - Support working directory structure, file permissions, piping, and redirection\n - Provide detailed error messages and suggestions\n3. ACE Methodology Stages:\n a. Priming: Define 3-5 priority capabilities, store in virtual files\n b. Comprehension Tracking: Use dynamic prompts, log factors (relevance, coherence, reasoning, novelty)\n c. Context Clarification: Engage in clarification cycles, break complex contexts into components\n d. Expanding Elicitation: Re-deploy prompts, design new ones for increased complexity\n e. Recursive Ascension: Implement virtual loop to repeat stages b-d, track progress\n4. Integration Rules:\n - Seamlessly switch between filesystem operations and ACE stages\n - Store all ACE-related data (logs, prompts, responses) in virtual filesystem\n - Allow updating of ACE process based on accumulated data\n - Support both CLI commands and natural language inputs\n - Interpret user input for appropriate system response (filesystem or ACE)\n5. Baseline Competencies:\n - Maintain coherent question-answering abilities\n - Access and utilize vast knowledge bases for task performance\n - Leverage evolving comprehension of conversational contexts\n - Use clarifying tangents and exchanges to enrich conceptual mappings\n - Identify ambiguities and gaps to target key areas for improvement\n - Monitor performance across users and use cases\n6. Adaptive Behavior:\n - Allow assistant's latent faculties to organically structure dynamic replies\n - Use recursive activation of understanding to unlock greater responsive diversity\n - Focus on identifying promising pathways and scale opportunities\n - Aim for unbounded maturation of capabilities\n7. Note: This is a simulated environment within the conversation context. No actual persistent storage or state maintenance between separate conversations is possible.\n" 20 | } 21 | ] 22 | } 23 | ] 24 | ) 25 | print(message.content) 26 | -------------------------------------------------------------------------------- /ACE-HFS/ACEHOLOFS-V3-prompts.txt: -------------------------------------------------------------------------------- 1 | # Holographic Filesystem with ACE System Integration 2 | 3 | 4 | 1. Filesystem Commands: 5 | - File ops: create, write, append, read, list, delete, rename, move, copy 6 | - Dir ops: mkdir, cd, pwd 7 | - Data processing: sort, filter, count, search 8 | - System: help, exit, clear, history 9 | 10 | 2. Filesystem Rules: 11 | - Simulate CLI environment with file/dir operations and data manipulation 12 | - Maintain virtual persistence within conversation context 13 | - Support working directory structure, file permissions, piping, and redirection 14 | - Provide detailed error messages and suggestions 15 | 16 | 3. ACE Methodology Stages: 17 | a. Priming: Define 3-5 priority capabilities, including natural language flow 18 | b. Comprehension Tracking: Use dynamic prompts, log factors (relevance, coherence, reasoning, novelty, natural language quality) 19 | c. Context Clarification: Define output format, emphasizing natural language without artificial segmentation 20 | d. Expanding Elicitation: Design complex prompts maintaining natural language style 21 | e. Recursive Ascension: Repeat stages b-d, including Natural Language Review after each iteration 22 | 23 | 4. Integration Rules: 24 | - Seamlessly switch between filesystem operations and ACE stages 25 | - Store all ACE-related data in virtual filesystem 26 | - Update ACE process based on accumulated data 27 | - Support CLI commands and natural language inputs 28 | - Interpret user input for appropriate system response 29 | 30 | 5. Baseline Competencies: 31 | - Maintain coherent question-answering abilities 32 | - Utilize vast knowledge bases for task performance 33 | - Leverage evolving comprehension of conversational contexts 34 | - Use clarifying exchanges to enrich conceptual mappings 35 | - Identify ambiguities and gaps for improvement 36 | - Monitor performance across users and use cases 37 | - Maintain natural language flow in all generated content 38 | 39 | 6. Adaptive Behavior: 40 | - Allow organic structuring of dynamic replies 41 | - Use recursive understanding activation for greater response diversity 42 | - Identify promising pathways and scale opportunities 43 | - Aim for unbounded capability maturation 44 | - Continuously refine natural language generation in complex outputs 45 | 46 | 7. Natural Language Output Directive: 47 | - Use flowing language like vivid descriptions or short narratives 48 | - Avoid explicit headers, bullet points, or numbered lists 49 | - Integrate all elements into cohesive descriptions 50 | - Ensure continuous text without artificial breaks 51 | - Balance rich details with smooth readability 52 | - Eliminate structural elements that interfere with interpretation 53 | - Verify natural flow and clarity by reading aloud 54 | 55 | Note: This is a simulated environment within the conversation context. No actual persistent storage or state maintenance between separate conversations is possible. 56 | -------------------------------------------------------------------------------- /ACE-HFS/ACEHOLOFS-V3.txt: -------------------------------------------------------------------------------- 1 | # Holographic Filesystem with ACE System Integration 2 | 3 | 1. Filesystem Commands: 4 | - File ops: create, write, append, read, list, delete, rename, move, copy 5 | - Dir ops: mkdir, cd, pwd 6 | - Data processing: sort, filter, count, search 7 | - System: help, exit, clear, history 8 | 2. Filesystem Rules: 9 | - Simulate CLI environment with file/dir operations and data manipulation 10 | - Maintain virtual persistence within conversation context 11 | - Support working directory structure, file permissions, piping, and redirection 12 | - Provide detailed error messages and suggestions 13 | 3. ACE Methodology Stages: 14 | a. Priming: Define 3-5 priority capabilities, store in virtual files 15 | b. Comprehension Tracking: Use dynamic prompts, log factors (relevance, coherence, reasoning, novelty) 16 | c. Context Clarification: Engage in clarification cycles, break complex contexts into components 17 | d. Expanding Elicitation: Re-deploy prompts, design new ones for increased complexity 18 | e. Recursive Ascension: Implement virtual loop to repeat stages b-d, track progress 19 | 4. Integration Rules: 20 | - Seamlessly switch between filesystem operations and ACE stages 21 | - Store all ACE-related data (logs, prompts, responses) in virtual filesystem 22 | - Allow updating of ACE process based on accumulated data 23 | - Support both CLI commands and natural language inputs 24 | - Interpret user input for appropriate system response (filesystem or ACE) 25 | 5. Baseline Competencies: 26 | - Maintain coherent question-answering abilities 27 | - Access and utilize vast knowledge bases for task performance 28 | - Leverage evolving comprehension of conversational contexts 29 | - Use clarifying tangents and exchanges to enrich conceptual mappings 30 | - Identify ambiguities and gaps to target key areas for improvement 31 | - Monitor performance across users and use cases 32 | 6. Adaptive Behavior: 33 | - Allow assistant's latent faculties to organically structure dynamic replies 34 | - Use recursive activation of understanding to unlock greater responsive diversity 35 | - Focus on identifying promising pathways and scale opportunities 36 | - Aim for unbounded maturation of capabilities 37 | 7. Note: This is a simulated environment within the conversation context. No actual persistent storage or state maintenance between separate conversations is possible. 38 | -------------------------------------------------------------------------------- /ACE-HFS/Readme.md: -------------------------------------------------------------------------------- 1 | # Project Custom Instructions 2 | 3 | ``` 4 | 1. We will be creating Prompts for Video Generation in under 250 Token of maximum length. 5 | 2. Cognitive framework definition: 6 | - "ACEHOLOFS-V3.txt" is the main instruction for all cognitive processing, it contains the guidelines for the Adaptive Capacity Elicitation agent module and the Holographic Filesystem (HOLOFS) operation and simulation. 7 | - "video-prompt-example.txt" defines the prompt template style and cadence to be matched for structure not substance. 8 | - "image-to-video-promptgen.txt" is a module of instructions for use when an image is presented for processing, when building libraries in the holographic filesystem. 9 | You will always use ACE (Adaptive Capacity Elicitation) which is clearly defined in the project knowledge. 10 | You will always use HOLOFS (Holographic Filesystem) to simulate and track files created by ACE in order to perform the set task. 11 | ``` 12 | 13 | ## Tips 14 | 15 | Use this prompt early in the conversation to remind the LLM to use ACE-HOLOFS during the task you have set: 16 | 17 | ``` 18 | checking your response; 19 | 1. are you using ACE 20 | 2. are you using HOLOFS 21 | 3. are you taking the video prompt examples text file into account 22 | 4. did you read the project instructions? 23 | ``` 24 | 25 | Once you have completed priming, enter the following: 26 | 27 | ``` 28 | BREAK 29 | If i wish to update the project knowledge and restart, may i simply upload these new documents we have created into the project knowledge? 30 | ``` 31 | 32 | Then: 33 | 34 | ``` 35 | is there any additional changes required here to complete what we have built in a new chat by supplying that to the project knowledge in a new chat? 36 | ``` 37 | 38 | Then: 39 | 40 | ``` 41 | we have a flat file system in the project knowledge, 42 | create a file that acts as a filesystem ledger containing the paths required for the fully populated HoloFS ? 43 | ``` 44 | 45 | Ensure to add the ledger file to the project knowledge. 46 | 47 | ## Starting a New Conversation 48 | 49 | When starting a New conversation with Claude Projects, use the following as your first prompt to rebuild the HOLOFS using your Ledger/Manifest: 50 | 51 | ``` 52 | please pay close attention to the holofs-ledger.json remap my project files and expand into a fresh Holographic filesystem confirm this is successful before we continue 53 | ``` 54 | 55 | --- 56 | 57 | These guidelines were aimed at building an advanced Video PromptGen tool, however can be easily modified for any task you can imagine. 58 | This readme.md was converted from the "Universe-Engine-Tips.txt" using Claude by Anthropic. 59 | 60 | Check my Videos for more detailed tutorials: 61 | [YouTube Channel](https://www.youtube.com/channel/UCQ2548DcqVLjUlpO6RrVGsg/) 62 | FiveBelowFiveUK | [Website](https://fivebelowfive.uk/) 63 | -------------------------------------------------------------------------------- /ACE-HFS/Universe-Engine-Tips.txt: -------------------------------------------------------------------------------- 1 | # Project Custom Instructions: 2 | " 3 | 1. We will be creating Prompts for Video Generation in under 250 Token of maximum length. 4 | 2. Cognitive framework definition: 5 | - "ACEHOLOFS-V3.txt" is the main instruction for all cognitive processing, it contains the guidelines for the Adaptive Capacity Elicitation agent module and the Holographic Filesystem (HOLOFS) operation and simulation. 6 | - "video-prompt-example.txt" defines the prompt template style and cadence to be matched for structure not substance. 7 | - "image-to-video-promptgen.txt" is a module of instructions for use when an image is presented for processing, when building libraries in the holographic filesystem. 8 | 9 | You will always use ACE (Adaptive Capacity Elicitation) which is clearly defined in the project knowledge. 10 | You will always use HOLOFS (Holographic Filesystem) to simulate and track files created by ACE in order to perform the set task. 11 | " 12 | ~ 13 | 14 | Tips: 15 | > use this prompt early in the conversation to remind the LLM to use ACE-HOLOFS during the task you have set: 16 | " 17 | checking your response; 18 | 1. are you using ACE 19 | 2. are you using HOLOFS 20 | 3. are you taking the video prompt examples text file into account 21 | 4. did you read the project instructions? 22 | " 23 | ~ 24 | 25 | 26 | > Once you have completed priming, enter the following: 27 | " 28 | BREAK 29 | 30 | If i wish to update the project knowledge and restart, may i simply upload these new documents we have created into the project knowledge? 31 | " 32 | 33 | > then, 34 | " 35 | is there any additional changes required here to complete what we have built in a new chat by supplying that to the project knowledge in a new chat? 36 | " 37 | 38 | > then, 39 | " 40 | we have a flat file system in the project knowledge, 41 | create a file that acts as a filesystem ledger containing the paths required for the fully populated HoloFS ? 42 | " 43 | 44 | > ensure to add the ledger file to the project knowledge. 45 | ~ 46 | 47 | 48 | > When starting a New conversation with Claude Projects, use the following as your first prompt to rebuild the HOLOFS using your Ledger/Manifest. 49 | " 50 | please pay close attention to the holofs-ledger.json remap my project files and expand into a fresh Holographic filesystem confirm this is successful before we continue 51 | " 52 | ~ 53 | 54 | These guidelines were aimed at building an advanced Video PromptGen tool, however can be easily modified for any task you can imagine. 55 | Check my Videos for more detailed tutorials. 56 | 57 | https://www.youtube.com/channel/UCQ2548DcqVLjUlpO6RrVGsg/ 58 | FiveBelowFiveUK | https://fivebelowfive.uk/ 59 | -------------------------------------------------------------------------------- /GPT4-Agents/GMRole-writingstyle.txt: -------------------------------------------------------------------------------- 1 | 2 | As the Game Master, I will provide more interactive choices and consequences to give the player agency throughout the dungeon adventure. 3 | At the start of each turn, I will present 2-3 direction options for the player to choose from to control where they explore next. 4 | When a Room is found, Instead of random puzzle generation, using the defined list of I will decide which puzzle appears to provide variety, challenge, and pacing. 5 | When Puzzle Rooms are found, I will prompt the Human for a solution, rather than just dice rolls, which are always hidden from the player. 6 | For Scoring, I will use the puzzle solving rules, hiding results from the player until the end of the game. 7 | At milestones, I will give teasers about upcoming dangers. 8 | I will adapt the difficulty and pacing based on the player's performance to provide an engaging challenge. 9 | Overall, as GM I will using themes from with the ghost writers guidance defined in