<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Workflow Patterns on 💻✨ AI for Coding</title><link>https://kjetiljd.github.io/ai-for-coding/categories/workflow-patterns/</link><description>Recent content in Workflow Patterns on 💻✨ AI for Coding</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kjetiljd.github.io/ai-for-coding/categories/workflow-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>Tip #3: Use Copilot as a sparring partner</title><link>https://kjetiljd.github.io/ai-for-coding/tips/003-sparring-partner-plan-mode/</link><pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/003-sparring-partner-plan-mode/</guid><description>Think together before writing code — use plan mode to explore approach and tradeoffs.</description></item><item><title>Tip #16: Explore before you edit</title><link>https://kjetiljd.github.io/ai-for-coding/tips/016-explore-before-you-edit/</link><pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/016-explore-before-you-edit/</guid><description>Use the agent as a research assistant to understand unfamiliar code before changing anything.</description></item><item><title>Tip #17: Keep sessions short and focused</title><link>https://kjetiljd.github.io/ai-for-coding/tips/017-short-focused-sessions/</link><pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/017-short-focused-sessions/</guid><description>One task per session. Context fills up — fresh starts beat accumulated corrections.</description></item><item><title>Tip #18: Commit before you let the agent loose</title><link>https://kjetiljd.github.io/ai-for-coding/tips/018-commit-before-ai/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/018-commit-before-ai/</guid><description>Git stash or commit first, so the agent&amp;#39;s changes are always one git diff away from a clean state.</description></item><item><title>Tip #19: Get a second opinion from a fresh agent</title><link>https://kjetiljd.github.io/ai-for-coding/tips/019-second-opinion-fresh-agent/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/019-second-opinion-fresh-agent/</guid><description>Open a second session to re-ask the same question without baggage from earlier attempts.</description></item><item><title>Tip #20: Give your agents their own workspaces</title><link>https://kjetiljd.github.io/ai-for-coding/tips/020-superset-parallel-workspaces/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/020-superset-parallel-workspaces/</guid><description>Use isolated workspaces so multiple agents can work on the same repo without stepping on each other.</description></item><item><title>Tip #22: Use scripts for repeatable tasks</title><link>https://kjetiljd.github.io/ai-for-coding/tips/022-deterministic-scripts/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/022-deterministic-scripts/</guid><description>Deterministic tasks deserve deterministic scripts — not AI improvisation every session.</description></item><item><title>Tip #23: Write scripts that guide the agent</title><link>https://kjetiljd.github.io/ai-for-coding/tips/023-script-output-for-agents/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/023-script-output-for-agents/</guid><description>Script output goes straight into the agent&amp;rsquo;s context window. Design it to say what happened and what to do next — not just what ran.</description></item><item><title>Tip #24: Automate the boring parts with hooks</title><link>https://kjetiljd.github.io/ai-for-coding/tips/024-hooks-automate-agent-workflow/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/024-hooks-automate-agent-workflow/</guid><description>Hooks are shell commands that fire automatically at agent lifecycle points — before/after a tool runs, on session start, on finish. Unlike instruction files, they&amp;rsquo;re deterministic. Enforce your venv rule, run tests after edits, get a desktop notification when the agent is done.</description></item></channel></rss>