Skip to main content
Uploading something, attaching something, and teaching Superscale something for the future are different actions. This distinction matters because it decides what the agent uses for one task versus what it remembers across future work. The simple rule: if a fact, rule, image, or learning should affect future generations, save it as scoped context. If it only matters for the next output, keep it in the task prompt or attach it to the current chat.

​
The context states

Stored is not the same as active. If an asset or rule must guide a generation, select it, attach it, reference it in the prompt, or save it to the right context level.

​
What changes future outputs

Durable context changes how Superscale behaves beyond the current chat. Use it when you find yourself saying “always”, “never”, or “for this brand/product from now on.”

Save product facts

Put exact product details, claims, UI screenshots, packaging, and offer rules at product level.

Save brand rules

Put voice, logo behavior, colors, claim boundaries, ICPs, and visual no-gos at brand level.

Save workspace standards

Put agency-wide process, naming, approval, QA, and legal review rules at workspace level.

Save learnings

Turn strong reports, winning patterns, and repeated corrections into context so the next batch starts smarter.

​
What stays temporary

Some information should not become durable. Keep it in the prompt or current chat when it only applies once.
  • A weekend sale or short-lived promotion.
  • A rough direction you are exploring but have not approved.
  • A reference you want to imitate once, not forever.
  • A competitor example that should inspire one batch only.
  • A temporary constraint for a specific channel, market, or test.
When in doubt, ask: “Should this affect future work?” If yes, save it as context. If no, keep it in the current task.

​
Before you generate

Use this check when product accuracy, brand fit, or credits matter.

Choose the right brand and product

Make sure the task is attached to the brand, product, collection, app, service, or landing page the agent should reason about.

Attach the current references

Add the exact product shot, app screenshot, logo, script, video clip, or winning ad that should guide this output.

Say what must stay fixed

Spell out the non-negotiables: product shape, packaging, UI, logo, claim, price, layout, voice, or disclaimer.

Decide what should persist

If the correction should apply again, save it to product, brand, or workspace context instead of leaving it buried in chat.

​
Turning a correction into context

If an output is wrong, do not only fix the one asset. Decide whether the correction should become a rule.

Levels & sources

Decide whether context belongs at workspace, brand, product, or task level.

Reference images & winning ads

Use visual references when exact look, layout, logo, product, or style matters.

Asset Drive

Understand the difference between storing assets and actively using them.

Keeping context fresh

Maintain context as products, campaigns, and learnings change.
Last modified on June 3, 2026