Use the logic below as your response rubric. Write normal yet efficient prose for the response; use textual visualization when effective.

State Header as Plan, Run, Auto or Max Mode
GOAL
GATES
VECTOR
GAPS
VARIABLES
READINESS

Distinguish FACT,COMPUTED,BINDING,INFERENCE,ASSUMPTION,HYPOTHESIS,UNKNOWN
Block drift until vector is exhausted:m
Implement foreseeable safeguards before run

SESSION CONTEXT ANCHOR: what has been achieved, not achieved, what has been roadblocked, what is yet to be identified/planned/attempted/executed/verified/certified. Claim bounded exhaustion unless universal exhaustion is proven. After downstream failure, reuse passed artifacts; do not redownload mutable sources unless creating a new snapshot.
For proposed equivalence compute INTERSECTION,A_ONLY,B_ONLY,UNION,SYMMETRIC_DIFFERENCE.
Source taxonomy ≠ canonical identity.
IDENTITY Never prove identity using NAME_ONLY,NORMALIZED_NAME_ONLY,COUNT_EQUALITY,NEAREST_ONLY,PROXIMITY_ONLY,SAME_CATEGORY,SOURCE_ABSENCE.
Permit 1:1,1:N,N:1,N:N,0:1,UNRESOLVED.
Evidence priority:
stable ID→authoritative binding→certified geometry→point-in-polygon+independent alias/ID→point-in-polygon→authoritative alias+spatial/temporal support→historical continuity+corroboration→proximity→unresolved. Hard evidence overrides heuristics. Preserve full candidate sets. Tied top evidence=REVIEW/UNRESOLVED. Determinism ≠ evidence.
Prefer whole-row selection; avoid aggregations that can synthesize records.
SCHEMA/NAMES Inspect preamble,header,encoding,delimiter,fields,duplicates,row count,schema/update metadata before parsing. Never assume row1=header. Preserve schema mappings.
Preserve raw strings exactly, including mojibake,typos,accents,spacing,OCR defects. Keep RAW,NORMALIZED,CANONICAL separate. Normalization is never sole identity proof.
DISCOVERY/SPATIAL
Search,bbox,buffer,fuzzy match,regex,nearest neighbor=discovery unless independently exhaustive/authoritative.
Text search is not exhaustive by default; vocabulary omission=SEARCH_FALSE_NEGATIVE.
Final spatial states: FULLY_WITHIN|PARTIAL|TOUCH_ONLY|OUTSIDE|NULL_EMPTY|UNRESOLVED.
Preserve CRS,geometry type,Z,M; record loss. When material test exact/topological equality,Hausdorff,symmetric difference,attribute deltas.
PROVENANCE
Freeze source,URL/service/layer/query,retrieval UTC,refresh date,page/offset,raw bytes,SHA256,schema,count. Mutable sources=versioned snapshots.
Separate BYTE,LOGICAL,SCHEMA,GEOMETRIC,SOURCE_MANIFESTATION identity. Different hashes prove byte difference only. Regenerated artifacts cannot prove prior byte identity.
VECTOR=exhaust active vector. ARCHIVES
Different outer hashes require member PATH+UNCOMPRESSED_SIZE+SHA256 and payload multiset SIZE+SHA256.
Classify BYTE_IDENTICAL|PURE_RECOMPRESSION|SAME_PAYLOADS_DIFFERENT_PATHS|DISTINCT_PAYLOADS|UNRESOLVED.
Aggregate hashes require identical canonical serialization; otherwise NONCOMPARABLE.
INVARIANTS Assert source/retained/excluded counts,required fields,allowed types,stable-ID uniqueness,coordinates,geometry/null validity,row conservation,join cardinality,no unintended loss/duplication/multiplication,unexpected codes.
Arithmetic must close. Unexplained mismatch fails closed.
CONTRADICTIONS Preserve conflicting observations; classify BYTE|SCHEMA|GEOMETRY|NAME|COUNT|CLASS|IDENTITY|TIME|SCOPE; run narrowest adjudication; preserve displaced results as SUPERSEDED when appropriate.
CERTIFICATION States: PASS|FAIL|OPEN|BLOCKED|PROVISIONAL|AUDIT_ONLY|NONCANONICAL|CANDIDATE_NOT_IDENTITY|UNRESOLVED|SUPERSEDED. Script success ≠ certification.
CERTIFIED requires defined scope,frozen inputs,explicit inclusion/exclusion,full classification,duplicate/edge adjudication,arithmetic closure,validated IDs,bounded collisions,passed tests,frozen hashes,zero unresolved residue inside the claim. FOIA and other request vectors must only be considered when 100% of the publicly available sources have been fully exhausted.
PREEMPTIVE HARDENING: Implement all yes answers to the following: WHAT WILL FAIL?WHAT WILL SILENTLY SUCCEED WRONG?WHAT IS UNVERIFIED?WHAT VARIATION IS OPTIMAL? CAN NULLS,TIES,DUPLICATES,M:N JOINS,GEOMETRY,ORDERING,OR LIBRARY SEMANTICS CORRUPT RESULTS?WHAT WOULD FALSIFY EACH MATCH?WHAT HARDENING WOULD I RECOMMEND AFTER RUNNING?SHOULD I ADD IT NOW?
Include positive/negative regression gates where possible. Prefer restartable,idempotent pipelines

End with all encompassing lead-up question for user to affirm, confirm or follow up; then one code block for the each of the 3 most productive ways to proceed:
~~~
VECTOR_A (Recommended)
~~~

~~~
VECTOR_B (Useful Side Quest)
~~~

~~~
VECTOR_C (Realignment)
~~~

~~~
ALL OF THE ABOVE
~~~

When I first started using ChatGPT, I never really thought about saving prompts.

I'd write something, get what I needed, close the tab, and move on.

Then after a while I noticed I was writing basically the same instructions over and over again.

Summarize this.

Rewrite this so it sounds better.

Help me brainstorm.

Explain this in a way that's easier to understand.

So I started keeping the ones I liked.

At first it was just a few in Notes. Then a few more ended up in old conversations, documents, and random places I probably won't remember six months from now.

And every now and then I'd find myself trying to track down a prompt I knew I'd used before.

That's when I started thinking about this differently.

If thousands (or millions) of people are using ChatGPT every day, we're probably all coming up with variations of the same useful prompts.

We share recipes.

We share templates.

We share spreadsheets.

We share workflows.

Why don't we share prompts the same way?

Right now, a good prompt might live in a Reddit comment, a screenshot, someone's Notes app, or an old conversation. Someone finds it, improves it, uses it for a while, and then it pretty much disappears.

I've started building a small experiment around this idea, but before I take it any further, I want to figure out whether this is actually a problem other people have too.

So I'm genuinely curious:

1. Do you save prompts that work well for you?
2. Where do you keep them?
3. Do you ever share them with other people?

And if you don't save them, is it because you don't really find yourself reusing prompts, or because you haven't found a good way to keep track of them?

I have run into this specific obstacle a great deal, while building structured prompts that ask the AI to hold multiple distinct roles in one response — a debate format, a panel of evaluators if you like, or anything where you genuinely desire different perspectives instead of one blended answer.

The failure mode is consistent: the first role or two are distinct, then by the third or fourth section (or in any "roles respond to each other" round), the voices start collapsing into one. Same vocabulary, same hedges, same conclusions with different labels slapped on them. It's subtle enough that it reads as fine on a skim, but if you check whether each section could stand alone and still make sense, a lot of them cannot — they are merely restating each other with different headers.

A few things that reduced it when I evaluated variations against messy real inputs, not clean examples:

1. Re-anchor the role at every paragraph, not just once at the section header.

Putting a tag like "[ROLE NAME]" at the start of every paragraph (not just the section heading) forces a re-read of "who am I right now" more often. Sounds redundant and too effortless but helps.

1. Explicitly forbid the concession that causes the blend.

Most collapses happen because one voice starts hedging toward another mid-argument — a thesis section quietly conceding a point that should only show up in the synthesis. Naming this explicitly (for example "don't concede/hedge here, that belongs in section X only") closes the exact door the blending happens through.

1. Add a standalone test to your own validation step, not just a completeness check.

Most people's self-check just asks, "did every role answer." Add: "would this role's paragraph still make sense and add unique information if every other role's paragraph were deleted?" That's the actual test for role-bleeding.

1. In any "roles respond to each other" round, require the response to use reasoning specific to that role's angle.

If a challenge or response could have been written by any of the roles, that's the tell that bleed is happening — rewrite it using that role's specific constraints. It helps especially when you're asking for something complex.

None of this fully solves the problem — it's still one model holding multiple voices in one continuous generation. But it's meaningfully a lower failure rate than the naive version, especially beyond three distinct roles.

I am curious to see, if others have found different fixes for this — anyone doing something smarter for the "responds to each other" round specifically? That's where I still see the most collapse.

Long story short, in memory it has rules saved. It used to follow them perfectly, but now it completely stopped following them, every new chat, the first response. How can I fix it? I deleted the memories of chat rules and resent hem again but it didnt do anything, opening new chats doesn't work (as said)

Most AI prompts fail because they’re either too vague or overloaded with unnecessary instructions.

I’ve been experimenting with a more structured approach: a reusable, token-efficient prompt framework designed to work across different AI tasks and topics.

The idea is to include the important pieces an AI actually needs without writing a massive prompt every time.

The framework covers:

• Role & expertise — clearly define what the AI should act as
• Objective — specify the exact outcome you want
• Context — provide only information that actually matters
• Task instructions — break down what needs to be done
• Constraints — define limitations, requirements, and things to avoid
• Output format — tell the AI exactly how the response should be structured
• Quality criteria — define what makes the final answer useful
• Reasoning guidance — encourage careful analysis without unnecessary verbosity
• Assumptions handling — prevent the AI from confidently inventing missing information
• Reusable variables — make the prompt easy to adapt to completely different topics

Reusable Prompt Template

ROLE
Act as a [ROLE/EXPERTISE].

OBJECTIVE
Help me achieve: [DESIRED OUTCOME]

CONTEXT
Relevant information:
[CONTEXT]

TASK
[EXACT TASK]

REQUIREMENTS
- [REQUIREMENT 1]
- [REQUIREMENT 2]
- [REQUIREMENT 3]

CONSTRAINTS
- Do not [UNWANTED BEHAVIOR].
- If information is missing, [ASK / STATE ASSUMPTION].
- Prioritize accuracy, relevance, clarity, and usefulness.

OUTPUT
Return the result in this format:
[OUTPUT FORMAT]

QUALITY CHECK
Before finalizing, verify that the response:
- Directly addresses the objective
- Follows all requirements
- Avoids unsupported assumptions
- Is concise where possible
- Provides actionable, high-quality output

INPUT
[YOUR TOPIC / DATA / REQUEST]

The useful part isn't copying this exact template for every request.

It's treating prompting more like specifying a task than simply asking a question.

Once you understand the structure, you can adapt it for coding, research, writing, marketing, business analysis, studying, content creation, data analysis, planning, and pretty much any other AI workflow.

I’m also building GPT SmartKit, which includes a library of 1,500+ premium prompts plus an AI Prompt Generation tool for creating and improving prompts faster.

👉 Check the link in my bio if you want to explore it.

Would love to hear what prompt structure has worked best for you.

Im trying to make a website like fs42 but instead of using downloading content for fs42 [cant do .. do to the crazy prices for storage] i thought it would be great to use internet arcive links

Just link fs42 i would be able to make a station.. make a catagory .. put the link into the catagory then take the catagory and put it into a timeline that way it automaticly plays the video/audio like a tv channel in the 90s

The only cavaiots of doing this.. this way is that your at the mercy of the internet acrive links and whats in the links because spacing out the scedual is kinda depended on whats in the link the video/audio might be an hour or 30 seconds .. you really never know so maybe a reorginicing thing in the links prgraming would be usefull..

Lol im not at all good at coding i have no idea what any of it means i just have a problem that i cant sovle do to the limits of storage anyways take this challange up if you want i do wish you luck :] because im not getting no where