Click any tag below to further narrow down your results
Links
@lennox_saint on X
A user on X says you can get better results from Claude Code by picking the Fable 5.2 model with /model and setting sub-agents to Opus 5.5, so they don't copy the main model's output. The post is a short how-to with a prompt template asking for a title, summary, key points, and tags.
- Steps: open Claude Code, run /model and choose Fable 5.2, then set sub-agents to Opus 5.5.
- The poster says sub-agents set to the same model copy the main model's output, which is why they recommend the split.
- The post offers a structured prompt template for big jobs, asking for a highlight, summary, key points, and tags.
Sean Goedecke argues that using AI well is a real, durable skill, not something you can pick up instantly once models improve. He lists the parts of that skill, from supplying context to reviewing AI-written code, and says engineers who avoid AI entirely are falling behind.
- Good AI users supply context and explain the reasons behind a goal, because agents guess badly when they're missing information.
- Knowing what models can and can't do is durable: new models improve most on tasks older ones already handled well, so that sense carries over.
- AI-generated code looks polished but makes different mistakes than humans do, such as adding unnecessary mutexes for trivial edge cases, so reviewers need a separate skill set.
- Avoiding AI completely means being left behind, though the author warns against going all-in, since LLMs reward expertise that comes from doing the work by hand.
This is Anthropic's hands-on course teaching you how to write better prompts for Claude, with 9 chapters covering prompt structure, common failure modes, and practical techniques. You work through exercises and test examples in a live playground to see how prompt changes affect Claude's responses.
- The course teaches 80/20 techniques to fix common prompt failures and covers Claude's specific strengths and weaknesses
- It's structured as 9 chapters plus an appendix, designed to be worked through in order with practice exercises and an answer key
- The tutorial uses Claude 3 Haiku (the smallest and cheapest model) but notes that Sonnet and Opus are available as more capable alternatives
This is a feature guide for an AI tool that transforms video clips by changing their visual style, setting, or character while preserving the original motion and framing. You upload a 2-15 second clip, describe what you want to change, and get back a private 720p or 1080p variation.
- The tool uses your source video's motion and camera work as a fixed guide while applying new visual treatments (anime, 3D, watercolor, cinematic) or relocating scenes to different settings and lighting conditions
- Input videos must be 2-15 seconds, under 50 MB, with clear readable movement and a short edge between 480-720 pixels; outputs are private to your account and stay available in history
- Results aren't frame-perfect copies — faces, details, timing, and framing can shift because the AI interprets both the source and your prompt, so focused single-direction requests work better than multiple changes
@AnatoliKopadze on X
This is a promotional X post pointing to a 38-minute video where OpenAI CEO Sam Altman talks about using LLMs, paired with a guide on building a system that prompts itself. The post itself offers no substance beyond the video pitch and the claim that the talk beats 99% of users.
- Altman's core claim, as quoted, is that people will no longer need to write prompts.
- The post promotes a follow-up guide on building a self-prompting system, but the guide's contents are not included here.
- The "better than 99% of people" framing is unsupported marketing language, not a measured result.
@AnatoliKopadze on X
Andrej Karpathy walks through how he uses AI day to day, covering which model to pick, when thinking models pay off, turning one prompt into a full research report, running code through the model, and getting it to remember you across chats. The post is a pitch for a Claude-focused guide that expands on those same workflows.
- Karpathy's two-hour talk breaks down model choice, when reasoning models are worth the wait, and how to get a full research report from a single prompt.
- Two of the five segments cover letting the model run code for you and giving it persistent memory across separate chats.
- The author claims most people use about 10% of these models' capability and frames the linked guide as covering the other 90%, mapping the same ideas onto Claude features.
@undefinedKi on X
The post says Anthropic published the onboarding material it gives new hires, a framework called the 4D model: Delegation, Description, Discernment and Diligence. Its point is that prompting is only one quarter of working well with AI, and the rest is picking the right work, judging the output, and owning the result.
- Prompting falls under Description, so it is one quarter of the framework; the other three cover choosing work, evaluating output, and taking responsibility for it.
- New hires are trained on common model mistakes so they can review AI work more effectively, and the training continues as "ever-boarding" after onboarding.
- Anthropic made the full material public last week, free, with a certificate, under a Creative Commons license.
This is a detailed prompt template for generating AI product images of a skincare bottle with specific lighting, composition, and styling requirements. It's designed for creating clean, editorial-style product shots without branding elements.
- It's a single reusable prompt template, not an article with analysis or reporting
- The prompt specs an unbranded serum bottle on pale limestone with soft morning window light, 4:5 vertical crop, no text/logos/watermarks
- Intended for generating mockup-style skincare product photography without manually writing a detailed prompt
Martin Fowler shows that in long-running multi-agent workflows the real cost isn’t parallel execution but context pollution in the orchestrator’s working memory. He recounts how status polling and redundant file orientation dumped massive transcripts into the main thread, competing for attention. He then proposes simple rules—like merging overlapping tasks and avoiding unnecessary polls—to keep only essential information in context.
- Status-check prompts that dumped full JSONL transcripts into the main thread, not parallel execution itself, were the real token/attention sink in a multi-agent Claude Code session.
- The actual bottleneck in long multi-agent runs is the orchestrator's working memory getting polluted, since tokens are a one-time cost but context pollution degrades focus for the rest of the session.
- Running adjacent subagents independently meant each paid the full cost of learning the same architecture from scratch, wasting effort that duplicate orientation could have avoided by grouping tasks with shared context.
- The fix is partitioning work by "cognitive locality" (grouping tasks that share a mental model) and having subagents return only refined conclusions rather than raw reasoning, keeping noise out of the orchestrator's context.
The article argues that speaking long, unfiltered “rambles” to an LLM captures your full train of thought and design trade-offs in a way short typed prompts can’t. It offers tips like embracing uncertainties, recording group debates, and voicing emotions to give the model enough context to make decisions that match your priorities. Finally, it shows how to set up a dictation app or transcription pipeline to feed those recordings into your coding agent.
- Rambling long, unfiltered voice memos to Codex (transcribed via Whisper) beats short typed prompts because it captures hidden preferences and context, sharply reducing follow-up questions
- Recording hours-long debates between cofounders gives the AI "ground truth" on team biases/priorities, effectively making it a third team member
- Deliberately voicing uncertainties, false starts, and emotional reactions (not just polished conclusions) reveals constraints that let the AI make on-target decisions
@trq212 on X
A practitioner's guide to working with Claude Fable 5 by mapping what you know, don't know, and haven't considered before and during agentic coding work. The core idea is that output quality tracks how well you clarify the unknowns Claude runs into.
- Fable is described as the first model where output quality is bottlenecked by the user's ability to clarify unknowns, not by the model itself.
- The author sorts unknowns into four buckets: known knowns, known unknowns, unknown knowns, and unknown unknowns, and suggests prompting for each (e.g., a "blindspot pass" for unknown unknowns).
- Techniques span the whole workflow: brainstorm and HTML prototypes before coding, interviews where Claude asks one question at a time, pointing Fable at reference source code, and an implementation-notes file to log deviations.
- The author's own launch video for Fable was edited with Claude Code, using prototypes and a color-grading lesson to surface gaps in his knowledge.
@Raytar on X
A post from X user @raytar claims a friend who is an Anthropic engineer shared an internal video on how the core team prompts Claude, and says the author realized after watching it that they had been using Claude wrong for two years. The post itself contains no concrete prompting techniques, so the value depends entirely on the linked video.
- The author says a friend at Anthropic, who they claim earns $1.2 million a year, sent them an internal video of the core team's prompting playbook.
- The author describes the video as something "never supposed to get out" and says nothing better on prompting exists.
- The post names no specific technique, example, or finding, so it is mainly a pointer to the video rather than a standalone source of guidance.
@Raytar on X
A post from @raytar says a friend on Andrej Karpathy's team at Anthropic shared the CLAUDE.md file he uses, and that it makes Claude follow instructions far better from the first message. The post is a short pitch with no technical detail, so the file itself is the real content, and it is linked as an article rather than shown inline.
- The author says a CLAUDE.md file from a colleague of Andrej Karpathy, who joined Anthropic five weeks ago, changed how Claude behaves for them.
- The claimed benefit is that Claude stops resisting their requests and works the way they need from the first message.
- The post itself gives no specifics on what the file contains, so the claims are unverified.
@xiathis on X
A Spanish-language X post where the author says he watched two Anthropic engineers spend 24 minutes walking through little-known Claude features, and admits he has been using Claude Code inefficiently. The post itself is mostly a promo for a video, so the substance lives in that video rather than in the text.
- Two Anthropic engineers cover hidden Claude features in a 24-minute video.
- The author says he had been using Claude Code in a basic way and missed these capabilities.
- The post gives no specific features or techniques, only the claim that the video will change how you use AI.
@anujcodes_21 on X
Anthropic has published a free 27-minute workshop on writing prompts for Claude, taught by the team that built the model. The post's author argues it covers more practical ground in its first few minutes than paid courses costing $300 do in full.
- Anthropic's workshop is 27 minutes long and free to watch, with no registration or paywall.
- The instructors are the people who built Claude, not third-party course creators.
- The author claims paid $300 prompting courses cover less in their first 8 minutes than this workshop does overall.
Caveman Compression strips predictable words like articles, fillers, and connectives to cut token count by 15–58% while preserving facts. It offers three methods—rule-based NLP, masked-LM, and LLM-based—to balance speed, cost, and compression ratio. Use it to pack more content into limited token budgets, especially for LLM reasoning and RAG contexts.
- Three compression modes trade off cost/speed for ratio: rule-based NLP (15-30%, <100ms, free), RoBERTa MLM (20-30%, 1-5s, free), and LLM-based via OpenAI API (40-58%, ~2s, needs API key)
- Benchmarks across 13 test cases show 100% fact preservation with ~40% average token reduction
- Compressed RAG contexts can store 2-3x more information, and agents reasoning directly in caveman format fit more chain-of-thought steps per context window
- Best suited for internal docs and agent reasoning, not for user-facing, legal, or emotional text where tone and grammar matter
Exploring the effectiveness of coding agents hinges on effective user input, constraints, and context. By applying Steven Johnson's patterns for generating ideas, the article demonstrates how to enhance coding agent outputs through structured prompting and feedback mechanisms. This approach encourages incremental development, reuses existing solutions, and fosters a collaborative environment between humans and AI.
- Coding agents produce better output when users apply Steven Johnson's "good ideas" patterns (adjacent possible, liquid networks, slow hunches) as prompting strategies rather than treating the agent as a one-shot answer machine.
- Structured constraints and iterative feedback loops—not just clearer instructions—are what actually improve agent performance, mirroring how innovation historically emerges from recombination rather than isolated genius.
- Treating coding agents as collaborators to think alongside, rather than tools to extract finished answers from, leads to more incremental, reusable, and higher-quality code.
Explore around 30 pro-tips for maximizing the efficiency of Gemini CLI, an open-source AI assistant designed for command-line use. The guide covers setup instructions, essential features, and advanced techniques for coding, debugging, and automating tasks through natural language prompts.
- Gemini CLI is a free, open-source command-line AI assistant, and the repo compiles ~30 practical tips for using it effectively in coding workflows
- Covers concrete techniques like setting up context/config files, using custom slash commands, and chaining prompts for debugging and automation
- Focuses on efficiency tricks (e.g., scripting repetitive tasks, managing context windows) rather than just basic feature explanations