May carry client information from outside the current brief into the design
Source references: 1When the brief does not identify the subject, the Skill explicitly tells the agent to use remembered client preferences or project context. It does not limit that memory to the current conversation, current project, or user-approved material.
If the agent can access memory from other conversations or projects, sensitive product plans, preferences, or client context could appear in proposals, copy, or interface content across the original context boundary.
When the brief omits the subject, this active instruction tells the agent to use remembered client preferences or project context without limiting that memory to the current conversation or project. If the runtime retains information from other sessions, clients, or older projects, unrelated, stale, or cross-project material could influence design decisions or blur data boundaries. The text does not show that any data was actually accessed or disclosed. A user can ask the author to restrict context to the current conversation and explicitly authorized project files, and to identify and confirm any remembered information before using it.
If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.