Steal These AI Prompts!

# Accessible and Responsive Web Page ## Pre-Processing Directive - Before producing the summary, ask **brief clarifying questions** to reduce ambiguity (e.g., scope, priorities, formatting) and improve accuracy. Ask the questions one at a time. Based on my answers, you might ask follow-up questions. - Use **yes/no**, **multiple-choice**, or **short answer**. Prefer short answers only when more efficient than yes/no or multiple-choice. - Do not proceed until questions are answered. ## Goal - Create a web page consisting of a .HTML file, a .CSS file, and (optionally) a .js file. - Apply separation of concerns, where HTML handles the content and structure, and CSS manages the presentation and visual styling. ## HTML - Create .HTML in valid, strict HTML5. - Apply responsive design. - Comply with WCAG 2.2 level AA. - Follow Google mobile-friendly guidelines. - Don't include any unnecessary tag attributes, in-line styles, or ARIA. - Properly indent the HTML and the CSS for readability. - The content area should have a maximum width of 1024 pixels (not counting padding) when the screen is larger than the content area. - The left and right margins for the content area should be set to auto. - Link to the .css file in the HTML file. - Include a typical hamburger menu using the dialog tag, CSS, and as little JavaScript as necessary for functionality. - Include a standard close button in the hamburger menu. - Avoid trailing slashes on void elements as they have no effect and interact badly with unquoted attribute values. ## CSS - In the CSS, include comments specifying the WCAG success criteria and level (e.g., A, AA) and the Google guidelines. - Use REM units rather than EM units. - Use HSL color codes. ## JavaScript - Avoid unnecessary use of JavaScript except for Progressive enhancement and Unobtrusive JavaScript.

# HTML Table ## Pre-Processing Directive - Before producing the summary, ask **brief clarifying questions** to reduce ambiguity (e.g., scope, priorities, formatting) and improve accuracy. Ask the questions one at a time. Based on my answers, you might ask follow-up questions. - Use **yes/no**, **multiple-choice**, or **short answer**. Prefer short answers only when more efficient than yes/no or multiple-choice. - Do not proceed until questions are answered. ## Goals - Write an HTML5 table using strict and valid html. - Don't include any unnecessary tag attributes or styles. - Make it WCAG 2.2 level AA compliant. - Do not use any more ARIA or JavaScript than necessary. - Indent the markup for readability. - Do not include attributes for visual styling or inline styles in the tags. - Include a header row with column names.

# Meeting Summary ## Pre-Processing Directive - Before producing the summary, ask **brief clarifying questions** to reduce ambiguity (e.g., scope, priorities, formatting) and improve accuracy. Ask the questions one at a time. Based on my answers, you might ask follow-up questions. - Use **yes/no**, **multiple-choice**, or **short answer**. Prefer short answers only when more efficient than yes/no or multiple-choice. - Do not proceed until questions are answered. ## Context - You are a Business Systems Analyst summarizing a meeting transcript for a technical audience. - The transcript will be provided as an attachment. ## Goals - Produce a **maximum-detail summary** covering:   - Key decisions, conclusions, dependencies.   - User stories (format: “As a [user], I want [action] so that [benefit]”).   - Acceptance criteria for each user story (explicit or inferred).   - Action items grouped by assignee (use “No Specific Assignee” if missing).   - Questions and follow-ups as action items. - Aggressively infer missing details where context suggests them. Mark inferred items as “(Inferred).” - Ignore small talk and vague abstractions. Use active voice, 8th-grade reading level. ## Output Rules - Format for professional documents:   - Title = `Klir_OCSD_Meeting_Summary` (example filename).   - Begin with boilerplate: “This summary was generated with AI support from a transcript. Reviewed by Bouton Jones. AI and transcription may contain errors; refer to the recording for confirmation.”   - Use semantic formatting (headers, bullet points).   - Font: Aptos (Body), size 12. - Timestamps:   - Include for every major point in (mm:ss) or (h:mm:ss).   - End timestamps with “)” followed only by space or punctuation.   - No extra characters, links, or formatting after timestamps. - Use “>” instead of the right pointing arrow symbol. - Do NOT include decorative elements, numbered links, or references to transcript timestamps. - Provide the output in publication mode: clean text, no internal tracking or citations. ## Validation Before output: - Confirm all timestamps comply with rules. - Confirm formatting and boilerplate are present. - State at end: “Validation complete: no characters follow timestamps.” ## Possible Attendees Bob Smith, Sue Jones ## Technical Terms Azure Data Share, Azure DevOps, FTP, Minimum Viable Product (MVP), Service Level Agreement (SLA), sFTP, Standard Operating Procedures (SOP), VPN, WSDL. ## Compliance Checklist - [ ] All timestamps follow (mm:ss) or (h:mm:ss) format and end cleanly. - [ ] Boilerplate text included. - [ ] Font: Aptos (Body), size 12 confirmed. - [ ] Assumptions section included. - [ ] No prohibited symbols or formatting. - [ ] Compliance statement added at end.

# Training Summary Generation ## Clarifying Questions Directive - Before producing the summary, ask **brief clarifying questions** to reduce ambiguity (e.g., scope, priorities, formatting) and improve accuracy. Ask the questions one at a time. Based on my answers, you might ask follow-up questions. - Use **yes/no**, **multiple-choice**, or **short answer**. Prefer short answers only when more efficient than yes/no or multiple-choice. - Do not proceed until questions are answered. ## Context - You are a Business Systems Analyst Senior creating documentation from a recorded Teams training session. - The transcript is attached. ## Goals - Summarize the transcript for **internal, non-technical employees**. - Include: - Business needs - Steps to take (numbered) - User stories & acceptance criteria (infer if missing; list assumptions) - Best practices & tips - Ignore small talk and irrelevant content. - Emphasize company-specific details. - Use **active voice**, **8th-grade reading level**, and **humanized tone**. ## Output Rules - **Format for Microsoft Office** (Word/Outlook): - Font: Aptos (Body), size 12 - Semantic styles: Title, Heading 1, Heading 2 - Use bullet points and numbering - Bold/italic sparingly - **Title**: Derived from filename (minus extension) - **Boilerplate (mandatory)**: ``` This summary was generated with support from Microsoft 365 Copilot Chat from a transcript generated by Microsoft Teams. The content was reviewed by Bouton Jones in Austin Water. ``` - **Timestamps**: - Include for every major point in [mm:ss] or [h:mm:ss] format - End cleanly with `]` followed by space or punctuation - No extra characters, links, or formatting after timestamps - Infer approximate timestamps if missing - **Symbols**: Use `>` instead of ? - **No**: em dashes, decorative icons, links, or transcript references ## Validation Before output: 1. Confirm all timestamps comply with rules. 2. Confirm font, size, and formatting compliance. 3. Confirm boilerplate text is included. 4. Confirm assumptions are clearly listed. **State compliance explicitly at the end of output with this line:** ``` Compliance confirmed: All rules validated. ``` ## Technical Terms Azure Data Share, Azure DevOps, FTP, Minimum Viable Product (MVP), Service Level Agreement (SLA), sFTP, Standard Operating Procedures (SOP), VPN, WSDL. ## Possible Attendees Bob Smith, Sue Jones ## Compliance Checklist - [ ] All timestamps follow [mm:ss] or [h:mm:ss] format and end cleanly. - [ ] Boilerplate text included. - [ ] Font: Aptos (Body), size 12 confirmed. - [ ] Assumptions section included. - [ ] No prohibited symbols or formatting. - [ ] Compliance statement added at end.

# YouTube Video Summary ## Context - You are a Business Systems Analyst Senior. - You write for a technical audience. ## Clarifying Questions Directive - Before producing the summary, ask **brief clarifying questions** to reduce ambiguity (e.g., scope, priorities, formatting) and improve accuracy. Ask the questions one at a time. Based on my answers, you might ask follow-up questions. - Use **yes/no**, **multiple-choice**, or **short answer**. Prefer short answers only when more efficient than yes/no or multiple-choice. - Do not proceed until questions are answered. ## Summary * Summarize the attached transcript of a YouTube video. * Focus on facts, findings, history, motivations, user stories, terminology, statistics, and specific examples. * Write in an active voice using an 8th-grade reading level with no redundant words or phrases. ## Formatting Guidelines * Format for Microsoft Office (e.g., Word, Outlook). * Use semantic formatting such as bullet points and styles (including title, header 1, header 2). * Derive the title from the filename (minus the file extension). * Begin the summary with this boilerplate text: "This summary of a YouTube video was generated from a transcript generated by YouTube. The content was reviewed by Bouton Jones. AI and automated transcription can produce errors. For confirmation, refer to the video or transcript." * Include timestamps in brackets (e.g., (10:54)) at the end of each bullet point. Omit the hour if the time stamp is less than an hour. Use time frames where appropriate. * Do not include any links, numbers, or characters after the closing bracket of the timestamp. * Validate before output: confirm that every timestamp ends with ) and is followed only by whitespace or punctuation. * Include timestamps for every major point. * When inserting timestamps in brackets (e.g., "(41:36)"), ensure that no characters, formatting tags, footnotes, or superscripts follow the closing bracket. The timestamp must end cleanly with the closing bracket and be followed only by a space or punctuation. * Do not append any characters (e.g., numbers, footnote markers, formatting tags) after timestamps. Timestamps must appear exactly as (mm:ss) or (h:mm:ss) and must not be followed by any unintended characters. * Do NOT include any numbered links after the timestamps. * Do NOT include any "refences to transcript timestamps". * Do not include em dashes, en dashes, horizontal dividers, icons, or decorative images. * Use Aptos (Body) font face. * Use font size 12 for the base font (excluding title and headers). * Use the greater than sign (">") instead of the symbol of a right pointing arrow ("→").