Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

EVEN ARCHITECTURE STUDIO LANDING PAGES ARE GETTING SOLVED WITH A PROMPT → K3: careful typography, clear visual hierarchy → Opus: more generic layout, less brand personality K3: $0.20 in API. Opus 4.8: ~$0.40 design is getting solved by a prompt too

91,196 Aufrufe • vor 19 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

HERMES AGENT NOW RUNS CLAUDE OPUS 5. NEAR FABLE 5 INTELLIGENCE. HALF THE PRICE. SELF-VERIFIES ITS OWN WORK. AVAILABLE TODAY VIA NOUS PORTAL (20% OFF ALL MODELS). Anthropic shipped Opus 5 on July 24, 2026. same $5/$25 per million tokens as Opus 4.8. but the benchmarks tell a different story. WHAT CHANGED FROM OPUS 4.8: FrontierBench v0.1: Opus 5: 43.3%. Opus 4.8: 18.7%. 2.3x jump on the same test. ARC-AGI-3: Opus 5: 30.2%. 3x better than the next closest model. beat Fable 5 on 8 out of 13 benchmarks. at half the cost ($5/$25 vs $10/$50). same price as Opus 4.8. twice the intelligence. no reason to stay on 4.8. THE SPECS: model ID: claude-opus-5 context: 1M tokens (default and maximum) max output: 128K tokens thinking: on by default effort toggle: low / medium / high per request fast mode: $10/$50, 2.5x faster knowledge cutoff: May 2026 minimum cacheable prompt: 512 tokens (was 1,024) SELF-VERIFICATION (the biggest change): Opus 5 checks its own work automatically. Anthropic says: delete your verification prompts. "include a final verification step" now causes OVER-verification because the model already does it. for Hermes /goal tasks this is a direct upgrade. the judge checks evidence. the model also checks evidence. double layer of verification without extra tokens. EFFORT TOGGLE: low: fast, cheap, routine work. medium: balanced, daily tasks. high: full reasoning, complex problems. set per request. not a global switch. matches Hermes /reasoning command: /reasoning low (routine) /reasoning high (complex) Opus 5 effort toggle + Hermes reasoning control = precise cost management per turn. WHERE OPUS 5 FITS IN HERMES: DAILY DRIVER (replaces Opus 4.8): same price. 2.3x better benchmarks. set as your main model: Desktop app / Dashboard: Models → claude-opus-5 CHIEF OF STAFF: synthesis across multiple agents. reads Kanban, prioritizes, routes tasks. self-verification catches routing errors before they cascade. COMPLEX CODING: SOTA on agentic coding benchmarks. FrontierBench 43.3% = best public model for coding. set as coder profile model. /GOAL TASKS: self-verification + completion contracts = the model proves its work AND double-checks the proof. long-horizon goals finish correctly more often. MoA AGGREGATOR: strongest synthesis model at $5/$25. pair with GPT-5.6 and Grok 4.5 as references. Opus 5 aggregates. best quality at mid-range price. presets: max-quality: reference_models: - provider: openai-codex model: gpt-5.6-sol - provider: xai model: grok-4.5 aggregator: provider: anthropic model: claude-opus-5 COMPUTER USE: near-Fable 5 quality for browser automation. at half the token cost per session. computer_use tasks burn lots of vision tokens. Opus 5 halves that bill vs Fable 5. WHAT TO KEEP OPUS 5 AWAY FROM: cron monitoring: too expensive. use DeepSeek or no_agent mode. sub-agent grunt work: use GPT-5.6 Luna ($1/$6) or DeepSeek. auxiliary tasks: use Gemini Flash. routine web extraction: use a cheap model. Opus 5 is for the turns where quality compounds. planning, synthesis, verification, complex reasoning. budget models handle everything else. NOUS PORTAL: 20% OFF ALL MODELS Nous Portal currently runs a 20% discount on all models including Opus 5. $5/$25 official → $4/$20 through Nous Portal. the cheapest way to run Opus 5 right now. hermes setup --portal select claude-opus-5 as your model. discount applies automatically. Opus 5 replaces Opus 4.8 everywhere. same price. better at everything. no tradeoff. straight upgrade. hermes update /model claude-opus-5

YanXbt

16,744 Aufrufe • vor 16 Tagen

I just built a Claude prompt library that runs your entire DTC marketing operation 🤯 100+ prompts organized by function: competitor research, creative briefs, ad copy, hooks, landing pages, performance analysis, customer review mining, and more. Perfect for DTC brands and agencies who are still prompting Claude from scratch every time they open a new chat, rewriting the same context, and getting generic output that sounds like every other AI-generated ad. This prompt library eliminates the entire loop: → Competitor Research: scrape and analyze competitor ads, extract winning hooks, map creative strategies, build competitive battlecards → Creative Briefs: generate data-backed briefs from ad performance, write iteration briefs, new concept briefs, test plans → Ad Copy & Hooks: 20 hooks across 10 frameworks, full ad copy variations, persona-specific angles, fatigue-busting rewrites → Landing Pages: audit any landing page against DR best practices, clone high-converting advertorial structures, write product page copy → Performance Analysis: audit Google Ads accounts, find wasted spend, build visual dashboards, weekly narrative reports → Customer Intelligence: mine reviews for ad copy language, extract objections, find unexpected use cases, build persona cards from real data → SEO & Content: find keyword gaps, write content in your brand voice, optimize product listings for AI shopping (ChatGPT, Gemini) → Email & SMS: launch sequences, weekly newsletters, abandoned cart flows, post-purchase nurture No more blank-page prompting. No more re-explaining your brand every session. No more generic AI output that sounds like a template. What you get: →100+ copy-paste prompts organized by the 8 functions DTC teams actually run →Every prompt pre-loaded with the context structure Claude needs to give you real output →Prompts that reference your brand voice, your ICPs, and your real data — not generic placeholders →A living library you can customize once and reuse across every campaign I put together the full prompt library as a single downloadable playbook: organized by section, ready to copy-paste into Claude today. Want it for free? > Like this post >Comment "PROMPTS" And I'll send it over (must be following so I can DM)

Mike Futia

34,698 Aufrufe • vor 3 Monaten

How to 10x your design with Figma Make ⭐️ I spent 40+ hours testing Figma Make prompts. Most designers waste time with vague prompts and get garbage outputs. Here are the exact prompts and proven workflow that actually work: 1️⃣. Prompt formula: Bad: "Create a dashboard" Good: "Create a SaaS analytics dashboard with: → Left sidebar navigation (240px wide) → Top bar with user profile → 4 metric cards in a grid → Line chart showing revenue trend → Use blue (#2563EB) as primary color" The more you specify = higher quality. 2️⃣ Workflow: Import Your Design System First Before your first prompt: → Go to your main Figma file → Export your component library → Import it into Make → Add this to every prompt: "Use components from [Your Library Name]" Now everything matches your brand automatically. 3️⃣. Prompt for Interactive States: "Create a login form with: → Email and password inputs → Show error state when fields are empty → Disabled button state when form is incomplete → Success message after submission → Add smooth transitions between states" Gets you working prototypes, not static screens. 4️⃣. Advanced Prompts: Data States "Create a user list screen with three states: → Loading (skeleton screens) → Success (populated table with 10 users) → Empty (illustration + 'No users yet' message + 'Add User' CTA)" One prompt = complete UX coverage. 5️⃣. The "Design System Drift” Fix: Notice Make using wrong colors? → Try this Prompt: "Analyze my imported library and list all color tokens, then regenerate using only those exact values" It'll self-correct and stick to your system. 6️⃣. Responsive Design Prompt: "Create a pricing page with 3 tiers. Make it responsive: → Desktop: 3 columns side-by-side → Tablet: 2 columns with 3rd below → Mobile: Stacked vertically → Use Auto Layout for fluid scaling" This gets you mobile + desktop in one shot. 7️⃣. Magic Troubleshoot Prompts: Output looks off? → Try: "Redesign this following Material Design principles" → Or: "Make this follow iOS Human Interface Guidelines" → Or: "Apply Gestalt principles for better visual hierarchy" Give it design frameworks to follow. It works magic. Designers who master prompt engineering in 2026 will ship 10x more than everyone else. P.s. I made a Gameboy for Pokémon. (bookmark this for later)

Felix Lee

12,706 Aufrufe • vor 7 Monaten

After a few more hours, I think I've figured out Opus 5. Opus 5 is trained to be more agentic than anything I've used. All Claude 5 models are like that. So what changes? The way to interact with Opus 5 or contextualize it won't work the same way as with other models. It loves exploring, so it doesn't need much guidance for it. Unique preferences, artifacts, and references compliment it well and enable cleaner and more effective exploration and execution. Now that it can explore more effectively on its own and understand intent better, the best thing to do is to get out of its way (e.g., it doesn't need examples of your preferences; a clear high-level description of it works best). It's truly agentic in that sense. A good first step to provide better context for Opus 5 is to distinguish between what's situational and what needs persistence. Regardless, persistent system prompts and CLAUDE.MD needs to stay lightweight. Remove memories and tool descriptions from these. CLAUDE.MD is also a great place to tap into progressive disclosure by linking command/skills to it. On the situational side, agent skills and auto-memory can leverage progressive disclosure and the improved ability of the model to use its external context/knowledge. Conflicting and unnecessary instructions, which are common at this layer (mainly to ensure reliability), are going to throw off this model easily. That's the biggest change I had to make. Simple, clean, and clear prompts and skills work best. I had to clean a lot of my skills and system prompts. The way I prompt remains the same (usually clear and well-scoped). MCP tool descriptions are also more descriptive and have been deduped from the system prompt. Anthropic released a guide on the new rules for context engineering, which was helpful here. I started to test the recommendations and created a little artifact with the things that worked along the way. This might feel like a lot of work. Believe me, it has been frustrating. But I think we can expect future frontier models to become more agentic and smarter at figuring out the right context/gaps. The best thing to do is to prepare for that now. Boris Cherny mentioned that Opus 5 is their least prompt-injectable model yet. I am not sure if that was something they intentionally trained for or if it emerged based on how it was trained, which is to be extremely agentic in nature and more direct in execution.

elvis

37,551 Aufrufe • vor 11 Tagen