# Prompt Related Articles

HTX News Center provides the latest articles and in-depth analysis on "Prompt", covering market trends, project updates, tech developments, and regulatory policies in the crypto industry.

Opus 5 Game Prompt Goes Viral, 3A Masterpiece Replicated in 24 Hours

Opus 5 Game Prompt Goes Viral, 3A-Style Game Replicated in 24 Hours An Opus 5 prompt for game development has gone viral on X (formerly Twitter). The "challenge loop" method instructs the primary AI agent to decompose a task, assign sub-agents to specialized work, and crucially, add a "judge" agent to compare outputs against real 3A games. If results fall short, they are sent back for improvement in a continuous loop until quality standards are met. Using this prompt, developer Anshu built a space exploration game prototype, *The Long Silence*, in just 24 hours. He started by instructing Opus 5 to create a basic browser-based game using Three.js, then issued a 24-hour "visual enhancement" order. The AI worked autonomously through multiple agents, with the judge agent comparing screenshots to games like *Starfield*. The final game is playable in a browser. The prompt's success sparked a trend. Others have used it to create prototypes for a kart-racing game and a "Claudepunk 2077." The method also works with other models like GPT-5.6 Sol, though Opus 5 performed best. This approach leverages Opus 5's strengths in long-horizon planning and iterative self-correction, adding a strict validation mechanism to push its capabilities. The phenomenon demonstrates how advanced AI models are enabling rapid, autonomous game prototyping.

marsbit07/29 08:47

Opus 5 Game Prompt Goes Viral, 3A Masterpiece Replicated in 24 Hours

marsbit07/29 08:47

Claude Code Slashes 80% of Prompt Tokens, But Opus 5 Just Adds Them Right Back In

Claude Code, the AI coding assistant from Anthropic, recently announced a massive reduction of over 80% in its system prompt content for models like Opus 5 and Fable 5. The goal was to remove verbose, often conflicting, rules (like strict commenting and documentation requirements) and replace them with a simpler directive: write code that matches the style of the surrounding project. This "pruning" aims to make the model more efficient by reducing internal conflict from overlapping instructions, with no measurable performance drop reported. However, a developer's (@chenchengpro) investigation revealed a twist. While the prompt was drastically cut from 15,225 characters in Opus 4.7 to 4,467 in Opus 4.8, it *increased* by approximately 72% to 7,694 characters in Opus 5. This isn't a contradiction. The "over 80% cut" refers to the overall shift from the old, detailed rulebook-style prompts to a new, streamlined system. The 72% increase for Opus 5 represents new, targeted instructions added to manage the model's enhanced capabilities. Opus 5 is more proactive—it likes to report progress, generate longer outputs, use sub-agents, and expand task scope. The added prompt content (roughly 3,755 characters) primarily provides guidelines for "Delivering work" (controlling task scope, progress reporting) and "Corrections" (limiting excessive self-correction). These new rules are necessary to curb potential over-engineering on simple tasks, ensuring efficiency even as the model becomes more independent. In short, the old, restrictive manual was deleted, but new guidelines were written to harness the model's newfound initiative.

marsbit07/27 11:37

Claude Code Slashes 80% of Prompt Tokens, But Opus 5 Just Adds Them Right Back In

marsbit07/27 11:37

OpenAI Officially Teaches You 8 Tricks to Master ChatGPT

OpenAI has released an updated guide with eight key strategies to get better results from ChatGPT: 1. **Use the latest model** (e.g., GPT-5.6 Sol) for best performance with prompt engineering. 2. **Provide clear, specific instructions**, detailing the desired content, format, style, and length. Avoid vague requests. 3. **Structure prompts effectively**: Place the core instruction at the beginning and use delimiters like `###` or `"""` to separate instructions from the text to be processed. 4. **Use examples and explanations** to clarify the exact output format and style you want. 5. **Adopt a stepwise approach**: Start with a zero-shot prompt (instruction only), then add a few examples (few-shot) if needed, and consider fine-tuning only as a last resort. 6. **Avoid vague or imprecise descriptions**. Use concrete terms (e.g., "3-5 sentences") instead of phrases like "keep it brief." 7. **Specify what to do, not just what to avoid**. After stating restrictions, guide the model toward the correct action. 8. **For code generation, use "leading words"** like `import` for Python or `SELECT` for SQL to steer the model into the correct pattern. Additionally, OpenAI's new "Generate Anything" feature can automatically create suitable prompts based on a simple description of your task. Mastering these techniques helps users get more accurate and useful outputs from ChatGPT.

marsbit07/16 08:26

OpenAI Officially Teaches You 8 Tricks to Master ChatGPT

marsbit07/16 08:26

Claude Accused of Becoming Dumber by the Entire Internet, Anthropic Steps In to Reveal: It’s Not the Model That’s Tricking You

When users complained that Claude was "getting dumber," the root cause wasn't the AI model itself. In an official blog post, Anthropic clarified the critical difference between two key settings in Claude Code: Model and Effort. Model refers to the core "brain"—the fixed, trained weights of a specific AI (like Sonnet, Opus, or Fable). Changing the Model addresses *capability* ("can it do this?"), but its knowledge is static post-training. Effort, however, controls the AI's *approach and thoroughness* for a specific task. A higher Effort level instructs Claude to read more files, run tests, perform verification, and complete multi-step reasoning before responding, significantly increasing its "work output" for that job. Conversely, low Effort leads to quicker, less thorough replies. This distinction explains the March 2024 uproar where users experienced a sudden drop in Claude's performance. The cause was not a model change but Anthropic quietly lowering the *default* Effort setting from "high" to "medium" to reduce latency, which was later reverted. The key insight is that a smaller, capable model (like Sonnet) on high Effort can often outperform a larger, more powerful model (like Opus) on low Effort for many tasks. The article provides a practical troubleshooting framework: if Claude makes an error, first check the context and instructions. If it seems to skip necessary steps or validations, increase Effort. If it diligently attempts the task but fails conceptually or makes consistent factual errors despite good context, then consider switching to a more capable Model. The takeaway is a shift in focus: effective AI programming is less about always choosing the "strongest" model and more about intelligently *orchestrating* models and effort levels—acting like a project manager to assign the right "brain" with the right level of diligence for each job, optimizing both results and cost.

marsbit07/12 05:56

Claude Accused of Becoming Dumber by the Entire Internet, Anthropic Steps In to Reveal: It’s Not the Model That’s Tricking You

marsbit07/12 05:56

Lao Huang: Prompt is Dead, the Entire AI Community is Frenziedly Chasing Loops

The article "Prompt is Dead: The AI Industry is Obsessively Chasing Loops" discusses a major shift in AI development, where "Loop Engineering" is replacing traditional prompt engineering. Industry leaders like NVIDIA's Jensen Huang, Andrew Ng, and engineers from Anthropic and OpenAI argue that manually crafting prompts is becoming obsolete. Instead, the new focus is on designing autonomous, self-improving AI systems (loops) that can operate 24/7. A loop system typically involves five key phases: Discovery (finding tasks), Handoff (assigning to agents), Validation (critical independent review), Persistence (saving progress), and Scheduling (automated operation). The core idea is to move humans from being the operational "engine" to being the system "architects" who design the loop, define goals, and set up verification mechanisms. A major challenge and necessity is implementing robust, independent validation to prevent AI from uncritically approving its own work. The trend is seen as part of a move towards "inference-time compute," where allocating computational budget effectively becomes a key engineering skill. While loops can produce higher-quality outputs, they are more expensive and time-consuming than simple prompting. The article warns of risks like "verification debt," "comprehension corrosion," and "cognitive surrender," where engineers might stop understanding the code their systems generate. Ultimately, the article concludes that in an era of automated loops, human judgment and oversight remain the most critical and scarce resources.

marsbit06/29 08:37

Lao Huang: Prompt is Dead, the Entire AI Community is Frenziedly Chasing Loops

marsbit06/29 08:37

Jensen Huang: Prompts are Becoming Obsolete, Loops are the New Paradigm

Jensen Huang, alongside AI leaders like Peter Norvig, Boris Cherny, and Andrew Ng, is advocating for a shift from "prompt engineering" to "loop engineering" as the new paradigm for AI development. Instead of manually crafting individual prompts, the focus is now on designing autonomous loops—systems where AI agents execute tasks, self-validate results, and iterate until completion without constant human oversight. A loop is a management framework that enables agents to operate independently. Key implementations are seen in Claude Code (with features like /loop, /goal, and /schedule) and OpenAI Codex, which employ multiple agents working in parallel within isolated environments. A core principle is the separation of roles: one agent (or model) performs the task, while an independent agent (or a smaller, separate model) validates the output to ensure objectivity. The article outlines a practical roadmap for implementing loops, starting with a "four-condition test" to assess suitability, building a minimal viable loop, and emphasizing critical pitfalls to avoid, such as lacking hard stop conditions or allowing loops to handle tasks requiring human judgment. This evolution is framed as the fourth major shift in AI interaction: from Prompt Engineering (crafting instructions) to Context Engineering (providing background information), then to Harness Engineering (building tool-enabled environments), and finally to Loop Engineering (creating self-sustaining systems). This progression reflects a consistent trend of increasing abstraction, moving human involvement from direct instruction to system design and rule-setting. The concept has academic roots in frameworks like ReAct, which formalized the "reason-act-observe" cycle. While loop engineering promises greater automation, experts caution about managing token costs and warn against outsourcing understanding—AI can assist, but deep problem comprehension remains essential.

marsbit06/25 14:26

Jensen Huang: Prompts are Becoming Obsolete, Loops are the New Paradigm

marsbit06/25 14:26

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

"Codex Goal Mode: How to Make AI Work Continuously Toward a Specific Goal" OpenAI's Codex "goal mode" (/goal) transforms the AI from a reactive code assistant into a proactive execution agent capable of working autonomously for hours or even days to achieve a defined objective. To maximize its effectiveness, follow these key principles: 1. **Define Clear, Verifiable Exit Criteria:** The goal prompt should be a concise, measurable success condition, not a lengthy specification. Use quantifiable metrics like "reduce build time by 30%" or "achieve 100% test parity." 2. **Provide Initial Guidance and Tools:** Direct Codex toward likely problem areas and specify available tools (e.g., browsers, testing environments) to prevent it from exploring unproductive paths. 3. **Enable Progress Measurement:** Equip Codex with ways to track advancement, such as creating comparison tools for visual tasks or evaluation sets, ensuring it can gauge its own progress. 4. **Use a Realistic Execution Environment:** For tasks like performance optimization, provide access to environments that closely mimic production (e.g., similar configs, databases) to yield valid results. 5. **Be Cautious with Visual Goals:** Avoid vague "pixel-perfect" instructions. Instead, supplement visual references with functional checklists or design system specifications to prevent Codex from obsessing over minor details. 6. **Implement Progress Tracking:** For long-running tasks, have Codex commit code to draft PRs, update progress documents, or send Slack updates to maintain visibility into its work. 7. **Review and Consolidate Results:** Once the goal is met, instruct Codex to review its work, clean up ineffective experimental code, and reflect on what strategies succeeded or failed. Ultimately, using goal mode shifts the developer's role from writing prompts to managing a persistent engineering agent—defining objectives, establishing metrics, configuring environments, and conducting final reviews.

marsbit06/06 08:11

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

marsbit06/06 08:11

How to Become a Pro Claude User in 30 Days?

"How to Become a Claude Power User in 30 Days" outlines a structured month-long program to transform from a casual user into someone who leverages Claude as a core productivity system. The first week focuses on mastering prompt structure (Role, Context, Task, Format, Constraints), understanding context windows, and setting up foundational Projects and Memory for personalized context. The second week involves building reusable workflows for research, writing (using a two-step outline-first process), and decision-making. The third week shifts to automation: using Claude Cowork for autonomous file tasks, connecting tools like Google Drive and Slack, and setting scheduled automation. The final week is for compounding gains: optimizing all workflows based on feedback, building a personal knowledge repository, teaching the system to a colleague, and designing a complete, ideal "Claude Operating System." By day 31, the user operates with an autonomous assistant that handles routine tasks with deep context, freeing them for high-value creative and strategic work. The core message is that consistent, systematic configuration over 30 days creates a powerful, personalized productivity advantage.

marsbit05/20 08:06

How to Become a Pro Claude User in 30 Days?

marsbit05/20 08:06

Three Frameworks for Ordinary People to Achieve AI Capability Leap: Say Goodbye to the Dilemma of 'Repeating Inputs Every Day'

Summary: This article outlines three frameworks for maximizing AI efficiency, moving beyond basic prompt usage. 1. **Three-Layer Evolution**: Users progress from (1) **Prompt** (one-off instructions, reset each session), to (2) **Project** (context-aware within a specific project), to (3) **Skill** (permanent, auto-applied knowledge). Most users stagnate at the first layer, repeating the same instructions daily with no cumulative improvement. Skills transform the AI from a chat tool into a personalized work system. 2. **Transaction vs. Compound Interest Mindset**: Using prompts is a linear transaction—effort and output are 1:1, and stopping resets progress. Investing time in building Skills is compound interest; a small initial time investment pays continuous dividends, as each Skill permanently elevates the AI's baseline performance. 3. **Thin Harness, Fat Skills**: The system architecture should prioritize thick, well-defined Skills (90% of the value—containing processes, standards, and domain knowledge) and a thin "harness" (the minimal technical environment). Avoid over-engineering the toolchain while neglecting the AI's actual knowledge. Skills are permanent assets that automatically improve with model updates. The key takeaway: Identify tasks you repeat, encode them into Skills (using tools like Claude's Skill Creator), and shift focus from daily prompting to building a compounding, self-improving AI system.

marsbit04/22 06:43

Three Frameworks for Ordinary People to Achieve AI Capability Leap: Say Goodbye to the Dilemma of 'Repeating Inputs Every Day'

marsbit04/22 06:43

The Image Generation Model That's Hotter Than Nano Banana Has Leaked, Screenshots Are No Longer Evidence | Includes Prompts

A new AI image generation model, widely referred to as "GPT Image 2," has been leaked and is demonstrating significant advancements over predecessors like DALL-E 3 and even Google's Nano Banana Pro. It excels in four key areas: text rendering, prompt adherence, photorealism, and world knowledge. The model can generate highly accurate text in multiple languages, including complex Chinese characters, making it capable of producing convincing fake documents, UI screenshots, and product labels. This capability also raises concerns about the reliability of using screenshots as evidence. The model is currently in A/B testing, with a full release expected around May 2026 when DALL-E services are officially retired. It is accessible for testing on the LM Arena platform. The article includes several prompt templates optimized for the model, such as generating realistic app screenshots, product photos with detailed labels, and street scenes with accurate signage. This advancement is reshaping creative workflows but also accelerating the displacement of some traditional design roles.

marsbit04/19 01:11

The Image Generation Model That's Hotter Than Nano Banana Has Leaked, Screenshots Are No Longer Evidence | Includes Prompts