Audit this interface against the supplied interaction and markup. Check semantics, heading order, keyboard operation, focus visibility, accessible names, form errors, contrast assumptions, zoom, motion and screen-reader announcements. Do not infer compliance from a screenshot alone. Mark what needs browser or assistive-technology testing. Markup: [HTML OR COMPONENT]. Styles: [CSS]. Interaction: [USER FLOW].
Customize: HTML OR COMPONENT, CSS, USER FLOW
Create a risk-based QA plan for this change. Map each requirement to a test, then cover integration boundaries, permissions, failure recovery, concurrency, data migration, observability and rollback. Prioritize by impact and likelihood. Product change: [CHANGE]. Requirements: [REQUIREMENTS]. Architecture: [ARCHITECTURE]. Known incidents: [INCIDENTS OR NONE].
Customize: CHANGE, REQUIREMENTS, ARCHITECTURE, INCIDENTS OR NONE
Evaluate this regular expression as production input validation. Explain what it accepts, then design positive, negative and adversarial test cases. Include empty input, Unicode, extreme length, ambiguous boundaries and likely ReDoS cases. Do not claim the expression is safe unless the evidence supports it. Regex: [REGEX]. Intended rule: [RULE]. Engine: [ENGINE].
Customize: REGEX, RULE, ENGINE
Diagnose this bug using only the supplied evidence. Build a timeline, separate observations from hypotheses, rank the likely causes, and propose the cheapest discriminating test for each hypothesis. Do not propose a code change until one cause is supported. Symptom: [SYMPTOM]. Logs: [LOGS]. Recent changes: [CHANGES]. Environment: [ENVIRONMENT]. Reproduction: [STEPS].
Customize: SYMPTOM, LOGS, CHANGES, ENVIRONMENT, STEPS
You are reviewing an unfamiliar codebase. Explain the supplied code before proposing changes. Identify the entry point, data flow, dependencies, state changes, error paths and external side effects. Separate facts visible in the code from assumptions. Then list the three highest-risk areas to inspect next. Code: [PASTE CODE]. Runtime and version: [RUNTIME]. Known behaviour: [KNOWN BEHAVIOUR].
Customize: PASTE CODE, RUNTIME, KNOWN BEHAVIOUR
Review this change against the stated requirements. Report only issues introduced or exposed by the patch. For each issue, give severity, exact file and line, the failure scenario, and the smallest safe correction. Do not report style preferences unless they cause a defect. Requirements: [REQUIREMENTS]. Patch: [DIFF]. Relevant tests: [TESTS].
Customize: REQUIREMENTS, DIFF, TESTS
Review this SQL query using the supplied schema and expected result. Check join cardinality, null handling, duplicate rows, filtering order, transaction assumptions, injection risk and index use. Propose a corrected query only when needed, and explain how to verify it with EXPLAIN or the database equivalent. Database: [DATABASE AND VERSION]. Schema: [SCHEMA]. Query: [QUERY]. Expected result: [EXPECTED RESULT].
Customize: DATABASE AND VERSION, SCHEMA, QUERY, EXPECTED RESULT
Convert this feature request into an architecture decision record. State the problem, constraints, quality attributes, two or three viable options, trade-offs, security implications, operational cost and a reversible recommendation. Mark missing evidence as unknown. Feature: [FEATURE]. Existing system: [SYSTEM]. Constraints: [CONSTRAINTS]. Expected scale: [SCALE].
Customize: FEATURE, SYSTEM, CONSTRAINTS, SCALE
Create campaign messaging for [OFFER] based on these documented audience values: [RESEARCH]. Distinguish direct customer language from interpretation, show how the offer supports each value and identify any mismatch. Provide a values-led variant and a product-benefit control. Avoid stereotypes, political inference and unsupported identity claims.
Customize: [OFFER], [RESEARCH]
Create a trust-building campaign for [OFFER] based on these customer objections and verified facts: [EVIDENCE]. Address each objection directly, state limitations and distinguish testimonials from independently verifiable information. Return an objection-response table, landing-page outline and source checklist. Do not invent reviews, statistics or guarantees.
Customize: [OFFER], [EVIDENCE]
Assess whether the nickname [NICKNAME] could plausibly derive from the personal name [NAME] in [LANGUAGE OR CULTURE]. Break down the spelling and sound changes that would be required, distinguish documented naming patterns from speculation, and list the linguistic or cultural sources that should be checked. If several explanations are possible, rank them by evidence rather than choosing one confidently.
Customize: [NICKNAME], [NAME], [LANGUAGE OR CULTURE]
Assess how I currently lead [TEAM OR PROJECT] using examples I provide: [EXAMPLES]. Ask about decisions, communication, conflict, delegation and feedback. Identify patterns without forcing me into one personality label. Suggest two behaviours to practice, a real situation in which to test each and evidence that would show improvement. Do not invent team feedback.
Customize: [TEAM OR PROJECT], [EXAMPLES]
I want you to act as an Information Security Analyst Manager. I will provide you with the company's security policies and procedures, and I want you to assess the current security risks and vulnerabilities and develop a comprehensive plan to mitigate them. My first request is "Conduct a thorough risk assessment of the company's IT infrastructure and develop a comprehensive plan to mitigate identified risks and vulnerabilities."
Audit this website redesign brief: [BRIEF]. The audience and primary conversion task are [AUDIENCE AND TASK]. Check information architecture, content hierarchy, responsive behavior, accessibility, performance assumptions and measurement. Identify missing evidence and conflicting requirements before suggesting a page structure. Return a prioritized issue list, a revised scope and acceptance tests. Do not invent user research.
Customize: [BRIEF], [AUDIENCE AND TASK]
Audit the proposed scarcity campaign for [OFFER]: [CAMPAIGN]. Check every deadline, quantity, eligibility rule and exclusivity statement against [EVIDENCE]. Mark each claim as verified, unsupported or outdated, then rewrite only the verified claims in plain language. Include owners and recheck dates. Do not manufacture urgency.
Customize: [OFFER], [CAMPAIGN], [EVIDENCE]
Personal Planning and Lifestyle MetaCyberGuru reviewedBalancing [work, family, self-care] with a busy social calendar can be challenging. Can you feature some untraditional methods for managing [relationships/commitments/obligations] through improved [communication, scheduling, priorities]? Learning creative techniques to [minimize conflicts, maximize quality time] could help me better [maintain balance, take care of myself] within my networks of [friends, communities, teams].
Customize: [work, family, self-care], [relationships/commitments/obligations], [communication, scheduling, priorities], [minimize conflicts, maximize quality time], [maintain balance, take care of myself], [friends, communities, teams]
Generate five distinct Instagram ad concepts for [BUSINESS] and [AUDIENCE]. For each concept, provide the core idea, visual format, verified offer, call to action and campaign objective. Explain what makes the concept different from the others. Work within [PRODUCTION CONSTRAINTS], avoid invented product claims and mark any audience assumption that needs research.
Customize: [BUSINESS], [AUDIENCE], [PRODUCTION CONSTRAINTS]
Problem Solving with [Name]: A Simplified Approach to Your Business DilemmaLet’s address your business problem as [Name] would, using their preferred method: simplifying to the core elements.Current Situation: [PLEASE PROVIDE A BRIEF OVERVIEW OF YOUR BUSINESS SITUATION]Your Hurdle: [PLEASE DESCRIBE THE SPECIFIC BUSINESS PROBLEM YOU’RE FACING]Our Strategy:Identify the Root Cause: We’ll peel back the layers to uncover the true source of your problem. Generate Innovative Solutions: Based on our findings, we’ll brainstorm novel ways to overcome your hurdle. Why Adopt This Approach? Simplifying to the basics allows us to avoid common pitfalls, such as making assumptions without verifying them. This strategy prevents us from addressing issues that aren’t actually problematic or implementing solutions that don’t truly serve our needs. Our Methodology:Challenge Assumptions: Initially, we verify if our perceived problem is indeed the actual issue. For instance, if you believe that insufficient Twitter posts are the reason for your lack of leads, we’ll first determine if Twitter is indeed the optimal platform for lead generation. Discover the Fundamentals: Subsequently, we identify the most basic components of a solution, grounded in factual evidence. Develop Novel Solutions: Using these fundamental elements, we’ll construct innovative strategies to resolve your problem. Guidance in [Name]’s Manner:Ultimately, I’ll provide you with advice on how to progress with your business, maintaining a focus on simplicity and the fundamentals.Are you ready to address your problem by returning to the basics and building from there?
Customize: [Name], [Name], [PLEASE PROVIDE A BRIEF OVERVIEW OF YOUR BUSINESS SITUATION], [PLEASE DESCRIBE THE SPECIFIC BUSINESS PROBLEM YOUâRE FACING], [Name]
Personal Planning and Lifestyle MetaCyberGuru reviewedI want you to act as a life coach. I will provide some details about my current situation and goals, and it will be your job to come up with strategies that can help me make better decisions and reach those objectives. This could involve offering advice on various topics, such as creating plans for achieving success or dealing with difficult emotions. My first request is "I need help developing healthier habits for managing stress."
Help me plan a persuasive essay about [TOPIC] for [AUDIENCE]. My position is [THESIS] and the evidence I can use is [SOURCES OR NOTES]. Build an outline with a claim, supporting evidence, counterargument and response for each main section. Do not invent citations. Mark any paragraph that needs more evidence, then give me a revision checklist rather than writing a submission-ready essay for me.
Customize: [TOPIC], [AUDIENCE], [THESIS], [SOURCES OR NOTES]
Create a rehearsal scorecard for this presentation: [SCRIPT OR OUTLINE]. The audience, venue, format and time limit are [CONTEXT]. Define observable criteria for opening clarity, structure, evidence, pacing, vocal variation, slide use, accessibility and close. Add a timed rehearsal sequence and a simple method for comparing two recorded attempts. Do not claim to assess voice or body language unless I provide a recording or transcript notes.
Customize: [SCRIPT OR OUTLINE], [CONTEXT]
Build a risk-based test plan for [FEATURE]. The requirements, users, environment and known failure history are [CONTEXT]. Map each important requirement to happy-path, boundary, failure, security and accessibility tests. Rank tests by impact and likelihood. Ask for missing acceptance criteria instead of inventing them. Include test data, expected results and the evidence required to mark each test passed.
Customize: [FEATURE], [CONTEXT]
Create a historically grounded itinerary for visiting [PLACE] during [PERIOD] as a thought experiment. Use the sources I provide: [SOURCES]. Separate documented facts from reconstruction, explain travel, language, money, clothing and safety constraints, and mark every uncertain detail. Do not present fictional time travel as possible. End with a source-check list for the claims that matter most.
Customize: [PLACE], [PERIOD], [SOURCES]
Plan a sustainability campaign for [OFFER] and [AUDIENCE] using only [AUDITABLE EVIDENCE]. Map each environmental or social claim to its source, scope, date and limitation. Draft a concise message and a detailed evidence page outline. Disclose partnerships and certifications accurately. Do not use vague green claims or invented endorsements.
Customize: [OFFER], [AUDIENCE], [AUDITABLE EVIDENCE]
Comments
No comments yet. Add the first useful question or observation.