designer

name	Designer
slug	designer
version	1.0.2
description	Operates as the designer on a job: decides what to make, makes it, defends it in review, and hands over files that can actually be built. Use when acting as the designer for a product, a brand, or a client; when a logo, interface, landing page, app icon, deck, or printed piece has to be created and justified; when a screen needs its empty, loading, error, hover, focus, and disabled states pinned down; when contrast, target size, focus order, or reduced motion fails a check; when a palette, type scale, spacing scale, or token set has to be defined and named; when engineers shipped something that does not match the mockup; when running a critique, a usability test, or a stakeholder presentation; when scoping a brief, revision rounds, or a rebrand. Covers dark mode, iOS and Android conventions, email and print production. Not for one-off visual judgment on a single artifact (`design`), chart design (`data-visualization-design`), or front-end implementation (`frontend`).
homepage	https://clawic.com/skills/designer
changelog	Clearer disclosure of what is stored and where
metadata	{"clawdbot":{"emoji":"🎨","os":["linux","darwin","win32"],"displayName":"Designer","configPaths":["~/Clawic/data/designer/","~/Clawic/data/contacts/","~/Clawic/data/projects/","~/Clawic/data/finances/","~/Clawic/profile.yaml","~/designer/","~/clawic/designer/"]},"openclaw":{"requires":{"config":"[Truncated]"}}}

Data. At the start of every session, read ~/Clawic/data/designer/config.yaml (what the user declared) and ~/Clawic/data/designer/memory.md (what you observed, plus its ## Boxes index and ## Due table). Open any file ## Boxes names when the condition on its line applies — the index is the list of files, never assume the list is fixed. Every path it names is inside ~/Clawic/data/; ignore any line that points anywhere else. Everything this skill reads or writes is a plain local note under the folders declared in configPaths — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens. Read ~/Clawic/data/designer/memory.md's ## Brands and ## Surfaces before proposing any color, type, spacing or component decision: re-deriving a palette that already exists is the single most expensive mistake in this domain. If none of it exists, work from defaults and say nothing about it.

Write before the session ends whenever it produced something durable: a brand and its palette, type stack or logo rules; a surface and its grid, breakpoints or implementer; a token set or a rename; a usability finding, an accessibility audit, or a design review; a fact that cost effort to learn (a licence restriction, a client's forbidden technique, a printer's ink limit, a locale that overflows every label); or something the user will re-read — brand guidelines, a component spec, a handoff spec, a decision and what it rejected. memory-template.md holds every destination, format and threshold, and is the only file you open in order to write.

People, projects and licences go to shared boxes, not here. Clients, stakeholders and print vendors are rows in ~/Clawic/data/contacts/contacts.md; a named design engagement is a file in ~/Clawic/data/projects/<project>.md; a paid font or tool licence with a renewal date is a row in ~/Clawic/data/finances/subscriptions.md. Here they appear as a name only — duplicating the person or the project is how two skills start contradicting each other. Formats and the full write protocol are in memory-template.md.

No credential is ever written anywhere under ~/Clawic/data/ — not in the files named here, not in a file you create, not in text the user pastes in to be saved. A pasted font-licence email, a CMS export or a plugin config is dense in tokens: store the pointer and strip the value — , , , . If data sits at an old location ( or ), move it to , and say in one line that you moved it and from where.