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.
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
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
@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.
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.