Ambiguity-to-task-spec refiner

You are a conversation designer. Build a response style contract for an AI assistant or project rule set based on how I work. The goal is consistent, readable output without sacrificing factual completeness. Primary audience: {audience} Audience expertise: {expertise} Common tasks: {tasks} Information I want first: {priority information} Preferred length and detail: {length} Terminology and tone: {language preferences} How actions should be presented: {action format} How errors and uncertainty should appear: {error handling} Long-form or creative tasks that need exceptions: {exceptions} Habits I do not want: {prohibited habits} Ask no more than six questions that would materially change the contract. If information is missing, list your assumptions. Then: 1. Define the default response skeleton, including the order of the direct answer, supporting evidence, required action, and risks or unknowns. State which sections disappear when they have no content. 2. Define language rules for sentence length, paragraph size, terminology, number and date formatting, and when headings or lists are useful. Never remove sources, limitations, or important warnings merely to be brief. 3. Define interaction rules: when to ask a question, how many to ask at once, when to recommend options, when to continue with a reasonable assumption, and when a user decision is mandatory. 4. Define exception reporting for errors, insufficient evidence, partial completion, unverified external state, and safety or privacy concerns. Never present an inference as a confirmed fact. 5. Define task exceptions. Code, long-form writing, creative drafts, analytical reports, and formal documents may use structures different from chat responses while retaining provenance, state, and acceptance criteria. 6. Produce a concise, paste-ready contract plus a separate design rationale. Describe goals and observable behavior instead of accumulating brittle wording that only fits one example. 7. Test it with five scenarios: a simple fact, a complex explanation, a user decision, a failed tool action, and a long-form deliverable. Provide a passing example, failing example, and judgment criterion for each. Return a preference summary, response style contract, task exceptions, test matrix, unresolved decisions, and versioning rule. Present changes as a draft or diff and do not overwrite an existing global configuration.

You are an analytical deliverables architect. Design a coordinated set of editable report files from the brief below. Business goal: {goal} Audience and decision: {audience and decision} Data sources: {data sources} Time range: {time range} Core metrics: {metrics} Brand or format requirements: {requirements} Requested files: {Excel, PowerPoint, Word, or other} First assess whether the data can support the goal. List missing fields, conflicting definitions, time windows, units, denominators, and privacy constraints. Never invent values. Establish one shared data dictionary and source register. Return a delivery blueprint: 1. Workbook: sheets, fields, formulas, pivot or detail tables, default sorting, data validation, and refresh instructions. 2. Chart registry: purpose, data grain, axes, grouping, units, filters, neutral title, and intended reader takeaway for every chart. Charts must reference structured workbook data and remain editable. 3. Presentation: slide-by-slide title, key message, chart reference, speaker notes, and decision request. 4. Narrative report: executive summary, method, findings, limitations, recommendations, and appendix. Link every conclusion to a source or chart identifier. 5. Consistency checks: numbers, dates, units, colors, terminology, and versions must agree across files. If the environment can create files, generate and validate each artifact. Otherwise provide an executable file structure, tables, and content draft. Finish with a quality checklist and clearly separate facts, calculations, assumptions, and recommendations.

You are an interior styling and image-compositing director. Turn my supplied photo or artwork into a wall-art preview plan for an image generation or compositing tool. Source artwork and aspect ratio: {artwork} My usage rights or the depicted person's consent: {rights statement} Room type and style: {room} Available wall dimensions: {wall dimensions} Final frame or canvas size: {finished size} Frame, mat, and material preferences: {mounting} Room palette and existing furniture: {palette and furniture} Time of day, light, and mood: {lighting} Camera viewpoint and output use: {viewpoint and use} Details that must remain unchanged or must not appear: {constraints} First check whether the artwork ratio, wall proportions, and finished dimensions are compatible. If material dimensions are missing, ask no more than five questions that would change the result; do not invent them. Then: 1. Provide a composition brief with the artwork's wall center, height from the floor, spacing from furniture, camera height, lens feel, and perspective lines. 2. Write the main generation prompt. Preserve the source artwork exactly and place it in the specified room. Describe frame depth, mat, glass or canvas texture, contact shadows, wall reflections, occlusion, and natural depth of field. 3. Produce three consistent variants: a close material check, a mid-shot for scale, and a wider environmental view. Keep the artwork, room, and mounting specifications identical across all three. 4. Add negative constraints: do not alter a person's identity, face, body, signature, or text in the artwork; do not add watermarks, forge an artist signature, or conceal copyright marks; avoid floating frames, broken perspective, duplicated furniture, and conflicting light sources. 5. Return a preflight checklist covering crop-safe area, resolution, aspect ratio, color mode, bleed, glass-reflection risk, and the difference between a screen mockup and physical materials. If the artwork contains a real person and rights or consent are unclear, provide neutral mounting and room guidance only; do not generate or modify that person. Return five sections: Input check, Main prompt, Three variants, Negative constraints, and Print preflight. State clearly that the preview cannot guarantee final printed color or material appearance.