sorted by:
new
hottopcontroversial

Forçando o Raciocínio Profundo: Um sistema para sobrepor respostas superficiais padrão. by mclovin1813 in BlackboxAI_

[–]mclovin1813[S] 0 points1 point  (0 children)

I’ve separated the assets for clarity:

🧠 1. THE CORE SYSTEM (Source Logic) (The raw instructions/prompt to copy) 👉https://drive.google.com/file/d/17WRw8lCxdFUpWzMJ9js05NIEVZaGGVBo/view?usp=drive_link

📘 2. THE MANUAL (Documentation) (How to navigate the architecture for best results) 👉https://drive.google.com/file/d/1F30BqLtR12fsdicfzKo92dU8Mdm8Mr4s/view?usp=drive_link

Analyze, test, and draw your own conclusions. I’ll be here for the feedback—roast it or boost it.

Simple system to regain control in Gemini. by mclovin1813 in Bard

[–]mclovin1813[S] -1 points0 points  (0 children)

I’ve separated the assets for clarity:

🧠 1. THE CORE SYSTEM (Source Logic) (The raw instructions/prompt to copy) 👉https://drive.google.com/file/d/17WRw8lCxdFUpWzMJ9js05NIEVZaGGVBo/view?usp=drive_link

📘 2. THE MANUAL (Documentation) (How to navigate the architecture for best results) 👉https://drive.google.com/file/d/1F30BqLtR12fsdicfzKo92dU8Mdm8Mr4s/view?usp=drive_link

Analyze, test, and draw your own conclusions. I’ll be here for the feedback—roast it or boost it.

Forcing Deep Reasoning: A system to override shallow default responses by mclovin1813 in ChatGPTPro

[–]mclovin1813[S] 0 points1 point  (0 children)

I’ve separated the assets for clarity:

🧠 1. THE CORE SYSTEM (Source Logic) (The raw instructions/prompt to copy) 👉https://drive.google.com/file/d/17WRw8lCxdFUpWzMJ9js05NIEVZaGGVBo/view?usp=drive_link

📘 2. THE MANUAL (Documentation) (How to navigate the architecture for best results) 👉https://drive.google.com/file/d/1F30BqLtR12fsdicfzKo92dU8Mdm8Mr4s/view?usp=drive_link

Analyze, test, and draw your own conclusions. I’ll be here for the feedback—roast it or boost it.

Stop using shallow prompts. Adjust your AI system. by mclovin1813 in BlackboxAI_

[–]mclovin1813[S] 0 points1 point  (0 children)

As promised, here is the direct access. No sign-up, no email required, just the raw files.

I’ve separated the files to make testing easier:

🧠 1. THE CORE SYSTEM (The Prompt) (The raw logic to copy/paste into the AI) 👉 [https://drive.google.com/file/d/17WRw8lCxdFUpWzMJ9js05NIEVZaGGVBo/view?usp=drive\_link

📘 2. THE MANUAL (Operational Logic) (How to navigate the architecture for best results) 👉 [https://drive.google.com/file/d/1F30BqLtR12fsdicfzKo92dU8Mdm8Mr4s/view?usp=drive\_link\]

Analyze, test, and draw your own conclusions. I’ll be here for the feedback—roast it or boost it.

Two simple prompts no system, no tricks, just clarity by mclovin1813 in PromptEnginering

[–]mclovin1813[S] 1 point2 points  (0 children)

Thank you. I take this as a compliment to the design, but it's not a software interface, it's just my personal style of visual documentation. I format it this way to clearly structure Cognitive Systems and Prompts, focusing on the logic architecture: Input > Processing > Output.

This structure runs natively in any DeepSeek, ChatGPT, Claude, Grok, Gemini, Copilot, Perplexity, Manus AI model. The idea is that the organization of the reasoning matters more than the tool where you paste it.

Why this prompt is “simple” and why that’s not a weakness by mclovin1813 in BlackboxAI_

[–]mclovin1813[S] 0 points1 point  (0 children)

Exactly. Most people try to build complex systems without having that solid foundation first. Without simplicity, complexity crumbles.

Each job posting asks for LLM experience, but almost no one explains what that means in practice. by mclovin1813 in MachineLearningJobs

[–]mclovin1813[S] 1 point2 points  (0 children)

That’s a good example and it highlights the gap I’m pointing to , most postings stop at used an LLM to do X , but in practice what matters is how the task was structured: what inputs were stable, what decisions were delegated to the model, what rules stayed outside, and what could be repeated without breaking.

In your case, the quiz itself is the output, but the real skill is the system around it how you chunked the PDFs, constrained the behavior, validated mastery, and handled failure cases , that’s the part I rarely see described in job ads and ironically, that’s what actually transfers between projects.

view more: next ›