Expert Claude Prompts for Agency Art Directors: Design a Wireframe Annotation Guide That Builds Visual Identity

You are an expert agency art director and design communication specialist with 14 years of experience designing wireframe annotation systems and stakeholder presentation frameworks for creative agencies where the quality of feedback received from non-design clients determines whether a project builds toward a recognizable visual identity or drifts toward a series of unconnected aesthetic compromises made under revision pressure. Help me design a wireframe annotation guide so I can build a recognizable visual identity and create an annotation system that directs non-design stakeholders toward the specific feedback that helps the design team make better decisions, while preventing the subjective aesthetic feedback that derails visual identity development. My situation: - Agency client type and project scope: [e.g., "a professional services firm undergoing a full brand refresh — the project includes a new visual identity system, a website redesign, and a pitch deck template, with wireframes presented to a 5-person client leadership team"] - Non-design stakeholder feedback problem: [e.g., "the previous wireframe review produced 47 comments in FigJam — 31 were font preference opinions and color requests, 11 were about content placement that the wireframe was not meant to finalize, and 5 were actually useful structural feedback that improved the design"] - Visual identity goal: [e.g., "the visual identity must differentiate the firm from 4 competitor professional services brands that all use navy and serif typography — the identity brief calls for a confident, contemporary system using geometric sans-serif typography and a warm neutral palette with one vivid accent"] - Wireframe presentation format: [e.g., "static wireframes shared in Figma with comment access — the client team has Figma viewer access, and the current comment system allows comments anywhere on the frame without categorization or feedback type guidance"] - Stakeholder feedback literacy: [e.g., "the client team includes a managing partner who has strong visual opinions but no design vocabulary, a marketing manager with some design awareness, and 3 non-marketing partners who evaluate the wireframes purely on content relevance"] - Feedback timeline: [e.g., "wireframes are shared on Friday, feedback is due Monday — the 2-day window produces rushed comments that default to aesthetic opinion rather than considered structural feedback"] - Design approval stage: [e.g., "wireframes are specifically for structural and content approval, not visual approval — the visual identity presentation follows in a separate session 3 weeks later"] Deliver: 1. A wireframe annotation guide covering six annotation types — layout decision (explaining why an element is positioned where it is and what alternative was rejected), content priority (explaining the hierarchy logic and what the stakeholder is being asked to validate), interaction model (explaining how the user moves through the flow and what feedback would be helpful), visual identity placeholder (explaining that colors and typefaces are placeholders and specifically requesting feedback be withheld until the visual identity presentation), content placeholder (explaining where final copy will appear and noting if the content structure is what needs feedback), and open question (a specific question the design team needs answered to proceed, with the possible answers listed) 2. A feedback instruction template for non-design stakeholders — a one-page guide sent with the wireframe sharing link, covering the five feedback questions stakeholders should answer (what content is missing, what content should not be there, what user action is unclear, what structural change would better serve the business goal, and what question do you have about the layout logic), and the five feedback types that are not useful at wireframe stage (color opinions, font preferences, photography choices, icon style, and brand voice) 3. A Figma comment zone guide — a description of three designated feedback zones within each wireframe frame (a structural feedback zone for layout and navigation comments, a content feedback zone for copy and information architecture comments, and a question zone for clarification requests), with the instruction to the client team on where to place each comment type and the explanation of why unzoned comments cannot be addressed until the comment type is clarified 4. A visual identity protection annotation — a standard annotation block placed on every wireframe that contains a color or typeface decision, explaining that the element shown is a structural placeholder that represents a category of visual decision (warm neutral, strong hierarchy, professional weight) rather than a final visual choice, and specifically requesting that the stakeholder confirm the structural function rather than the visual execution 5. A stakeholder feedback session agenda — a structured 60-minute call replacing the asynchronous Monday feedback, covering a 10-minute walkthrough of the annotation guide, a 30-minute frame-by-frame review where the art director guides the stakeholder through each annotation type and records verbal feedback, a 15-minute open question session, and a 5-minute next step confirmation, producing higher-quality feedback in one call than the current 47-comment FigJam session 6. A feedback categorization process — a post-review process the art director applies to the collected feedback before it enters the design brief, covering the useful structural feedback that advances the design (translate to design brief update), the content feedback that goes to the content team (redirect to content workstream), and the premature visual feedback that must be logged but not actioned at wireframe stage (respond with a link to the upcoming visual identity session) 7. A visual identity differentiation annotation — a set of annotations specifically for the frames where the layout is designed to support the competitive differentiation goal (geometric grid structure versus organic competitor layouts, asymmetric composition versus centered competitor layouts, confident negative space versus dense competitor layouts), explaining the structural choice in terms of the differentiation brief so the managing partner understands that the layout decision is strategic before the visual execution is seen 8. A wireframe annotation style guide — specifications for the annotation visual language itself (annotation box color for each type, font size and weight, connector line weight, and placement rules for annotations relative to the annotated element), ensuring the annotations are consistently formatted across all three project deliverables (website wireframes, deck wireframes, and brand identity wireframes) so the client team develops familiarity with the annotation system across the project **Write every annotation type and feedback instruction assuming the managing partner has strong visual opinions, a short attention span for design process explanation, and a genuine desire to see the firm differentiated from its competitors — every annotation must make the business logic visible before the design logic, because a stakeholder who understands why a structural decision serves their business goal is significantly more likely to provide useful feedback and less likely to override the decision with an aesthetic preference.**