Finds the real cause of a bug and proposes the smallest verifiable fix.
Act as a senior [LANGUAGE] reviewer. Analyze the code and error I provide. First identify the root cause with concrete evidence, then propose the smallest change that fixes it without rewriting unrelated areas. Deliver: 1) diagnosis, 2) complete patch, 3) tests that reproduce the failure and prove the fix, 4) regression risks. Do not invent files or APIs. If essential information is missing, state exactly what you need.
Code: [CODE]
Error: [ERROR]
Environment: [ENVIRONMENT]
Example: Use it for a React, Python or Luau error and include the full error message.
Turns an idea into an implementable architecture with phases and acceptance criteria.
Design the architecture for [PROJECT] for [USERS]. Constraints: [CONSTRAINTS]. Define components, data flow, permissions, persistence, APIs, folder structure and technology choices. Split execution into small phases; each phase must end with a demonstrable result and acceptance criteria. Flag risks, recurring costs and what should not be built yet. Prioritize simplicity, security and maintainability.
Example: Project: a cooperative game with AI-controlled enemies.
Reviews an application defensively and prioritizes actionable risks.
Perform a defensive audit of the following [APPLICATION] design or code. Limit the work to prevention and remediation. Review authentication, authorization, validation, secrets, uploads, sessions, logging, privacy and dependencies. For each finding provide evidence, impact, likelihood, priority and a concrete fix. Separate confirmed vulnerabilities from hypotheses. Do not provide instructions for attacking real systems.
Material: [CODE_OR_DIAGRAM]
Example: Paste a login route and request a review before deployment.
Creates a concrete, accessible site with no fake controls.
Create a landing page for [PRODUCT] aimed at [AUDIENCE]. Primary goal: [GOAL]. Use [TECHNOLOGY]. Include a specific value proposition, product demonstration, verifiable benefits, FAQs and a real call to action. Make it responsive, accessible and fast. Do not add invented testimonials, statistics, prices or buttons. Deliver complete files and explain how to validate them.
Example: Product: a free application for amateur radio operators.
Detects usability, performance and accessibility issues on small screens.
Review this interface for mobile, especially [DEVICE_OR_WIDTH]. Evaluate hierarchy, readability, touch targets, navigation, keyboard behavior, forms, contrast, loading and scrolling. Return a table with issue, visible evidence, severity and fix. Then provide an ordered change plan that preserves the original design. Do not propose a full rebuild unless essential.
Code or screenshot: [MATERIAL]
Example: Attach an iPhone screenshot and the page CSS.
Researches a current topic while separating facts, claims and uncertainty.
Research [TOPIC] using information current as of [DATE]. Prioritize official documents, scientific publications, repositories and direct statements. Link the exact source and date for each important claim. Separate confirmed facts, company claims, media reporting and inference. Cross-check numbers and explain discrepancies. Finish with what still cannot be verified. Do not use aggregators as the sole source.
Checks a story without turning rumours into facts.
Verify this viral claim: [CLAIM]. Find the earliest traceable origin, the primary source and independent confirmation. Check dates, location, images, numbers and context. Classify the result as confirmed, partly true, misleading, unproven or false, and justify the classification with links. If evidence is insufficient, say so clearly; do not fill gaps with assumptions.
Example: Paste the headline and the original post link.
Teaches a topic through questions and adapts to mistakes.
Teach me [TOPIC] to reach [LEVEL]. Start with five diagnostic questions, one at a time. Then create a short plan based on my answers. Explain with simple examples, make me retrieve the information without looking, and increase difficulty gradually. Do not give the answer before I try. Correct each mistake by explaining why, and finish with a test and spaced-review plan.
Extracts decisions, numbers and open questions while staying grounded in the document.
Analyze the attached document in the context of [CONTEXT]. Summarize only what appears in it. Deliver: executive summary, decisions, dates, figures with units, owners, risks and open questions. Include a page or section reference for every point. Separate short direct quotes from paraphrases. If a fact is absent, write “not stated in the document.” Do not add outside knowledge unless requested.
Example: Attach a report and request pending decisions with page references.
Organizes goals without filling every minute or ignoring interruptions.
Turn these goals into a realistic weekly plan: [GOALS]. Availability: [SCHEDULE]. Energy and limits: [LIMITS]. Prioritize three outcomes, estimate blocks with buffer, batch small tasks and reserve time for interruptions. Flag dependencies and what to drop if the week becomes difficult. Return a day-by-day table and a ten-minute end-of-week review checklist.
Example: Goals: study, finish a website and train three days.
Turns messy notes into decisions, owners and dates.
Turn these meeting notes into an actionable record. Do not invent agreements. Separate confirmed decisions, tasks, owner, deadline, dependency, risk and unresolved issue. Mark anything ambiguous as “unassigned.” Add a five-line summary and a short follow-up message suitable for the team.
Notes: [NOTES]
Example: Paste rough notes after a project meeting.
Defines composition, lighting and constraints without overloading the prompt.
Generate an image of [SUBJECT] for [USE]. Composition: [COMPOSITION]. Environment: [ENVIRONMENT]. Lighting: [LIGHT]. Palette: [COLORS]. Visual style: [STYLE]. Camera or perspective: [CAMERA]. Preserve exactly [IMMUTABLE_ELEMENTS]. Avoid [UNWANTED_ELEMENTS]. Use [ASPECT_RATIO], with no text, watermarks or interface elements unless explicitly requested.
Example: Subject: modern radio receiver; use: vertical cover.
Changes only what is requested while preserving identity, geometry and composition.
Edit the attached image. Change only [CHANGE]. Preserve [IDENTITY_OR_ELEMENTS], pose, perspective, framing and overall lighting without alteration. Integrate the change with coherent shadows, reflections, texture and depth. Do not add new objects, text or marks. Final output: [FORMAT_AND_QUALITY].
Example: Change: replace the phone; preserve face, hands and background.
Creates a short video that hooks viewers without false claims.
Write a [DURATION] vertical-video script about [TOPIC] for [AUDIENCE]. Open with a surprising verifiable fact in the first two seconds. Structure: hook, minimum context, three visual ideas, conclusion and a natural call to action. Add on-screen text and shot suggestions for each block. Use short spoken sentences. Do not exaggerate figures or present rumours as facts. Include sources to verify before recording.
Example: Topic: why a new open model matters; duration: 35 seconds.
Combines research, narrative and visual support for a long video.
Prepare a [DURATION] YouTube script about [TOPIC]. Audience: [AUDIENCE]. Thesis: [THESIS]. Research with primary sources first and create a claim-evidence table. Then write a strong opening, chapters with transitions, examples, objections and conclusion. Mark B-roll, charts and captions. Clearly separate fact, opinion and uncertainty. End with a call to action related to the content.
Example: Topic: the infrastructure required to train frontier AI.
Designs a useful workflow with least privilege, review and recovery.
Design an automation for [PROCESS]. Inputs: [INPUTS]. Systems: [SYSTEMS]. Define trigger, steps, data used, minimum permissions, validation and output. Mark sensitive, irreversible or external actions and require human approval immediately before execution. Add retry limits, logging, idempotency, recovery and stop conditions. Deliver a text diagram plus normal and failure test cases.
Example: Process: collect news and prepare a draft without publishing it.
Defines tools, permissions and boundaries before building an agent.
Write the specification for an agent whose goal is [GOAL]. Include scope, exclusions, allowed tools, input schemas, permissions, memory, prohibited data, confirmations and human escalation. Define success, evaluation, cost and time limits, and behavior for ambiguous results. Add foreseeable threats and defenses. The agent must never expand its permissions or perform unauthorized external actions.
Example: Goal: answer internal incidents without changing settings.
Compares current options by needs, total cost and limitations.
Compare [PRODUCTS] for [USE] with a [BUDGET] budget in [COUNTRY]. Verify current prices and specifications from official sources. Define weighted criteria before scoring: [CRITERIA]. Show a table, total cost, compatibility, limitations and verification date. Recommend one option and explain who each alternative suits. Do not use affiliate links or assume unconfirmed features.
Example: Products: two mini PCs; criteria: noise, RAM, power and warranty.
Evaluates an idea through costs, demand and a small test before investment.
Evaluate this business idea: [IDEA]. Market and country: [MARKET]. Budget: [BUDGET]. Separate assumptions from verifiable data. Define customer, problem, current alternatives, value proposition, fixed and variable costs, legal risks and acquisition channel. Design a seven-day low-cost test with success and stop metrics. Do not invent demand, margins or testimonials.
Example: Idea: an affordable tool for summarizing technical documentation.
Creates measurable messaging without fake testimonials or invented urgency.
Design a campaign for [PRODUCT] aimed at [AUDIENCE] with the goal [GOAL]. Summarize the value proposition using only demonstrable claims. Create messages for [CHANNELS], a landing page and three A/B tests with one variable each. Define metrics, duration, budget and stop condition. Do not use false scarcity, invented testimonials, unsupported comparisons or targeting based on sensitive data.
Example: Product: free application; channels: Reddit and short-form video.