How I Prompt AI Models in 2026 vs a Year Ago: 3 Key Changes

A regular user of Claude and Codex shares three concrete changes that transformed how they prompt AI models over the past year. The advice is practical, no-nonsense, and aimed at developers using AI coding agents regularly.
1. Switch from Prompt Templates to Skills
Prompt templates are static and hard to share. Instead, the author now uses skills — formalized prompt templates that live inside Claude, Codex, or on GitHub. A skill is written once, reused across projects, and easily shared with teammates. This replaces the old approach of everyone maintaining their own prompt doc.
2. Prioritize Goals Over Step-by-Step Instructions
The second change: stop writing rigid, step-by-step instructions. Instead, write the skill or spec like you would for a senior developer: clearly describe the goal, what success looks like, and provide all necessary context. Modern models handle step decomposition better on their own. As models improve, this approach remains valid without rewriting skills every time a new model drops.
3. Use Loops Instead of Interactive Prompting
For complex, long-running projects (e.g., building software, websites, or long analyses), write a solid spec document and have the model run a loop against it. In Claude Code, the /loop command lets the model self-prompt continuously against the spec for hours. Codex has the same feature. This replaces the manual prompt-review-repeat cycle.
The author notes that skills plus goal-over-steps made the biggest difference and recommends starting there if you only change one thing.
📖 Read the full source: r/ClaudeAI
👀 See Also

Fix Ollama Cloud Model maxTokens: Cap is 16K, Not Config Value
Ollama cloud caps output at 16,384 tokens regardless of maxTokens config. Set to 14,000 to avoid EOF errors. Restructure long outputs or route to direct provider.

9 Practical Claude Tips from 8 Months of Daily Use (Non-Coding)
A Reddit user shares 9 hard-won lessons from 8 months of daily Claude use for writing and research—not code—covering editing, context management, style setup, and using Claude as a thinking partner.

Claude Code /insights command provides debugging and autonomous task tips
A Reddit user shares two practical techniques for using Claude Code's /insights command: asking for at least three potential root causes when debugging bugs, and using comprehensive task specifications with --dangerously-skip-permissions for autonomous runs.

How routing simple tasks to cheaper models cut AI costs by 40%
An OpenClaw user reduced their AI bill by 40% by analyzing usage logs and routing simple tasks like file operations and Q&A to cheaper models like DeepSeek-v3 and Gemini Flash, while reserving Claude Sonnet for complex reasoning tasks.