<?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>All Tips on 💻✨ AI for Coding</title><link>https://kjetiljd.github.io/ai-for-coding/tips/</link><description>Recent content in All Tips on 💻✨ AI for Coding</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kjetiljd.github.io/ai-for-coding/tips/index.xml" rel="self" type="application/rss+xml"/><item><title>Tip #1: Give Copilot a memory</title><link>https://kjetiljd.github.io/ai-for-coding/tips/001-copilot-instructions/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/001-copilot-instructions/</guid><description>Set up an instruction file so the agent knows your conventions from the start.</description></item><item><title>Tip #2: Every AI mistake is a rule</title><link>https://kjetiljd.github.io/ai-for-coding/tips/002-every-mistake-is-a-rule/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/002-every-mistake-is-a-rule/</guid><description>When Copilot gets something wrong, add it to your instructions instead of just fixing it.</description></item><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 #4: Paste the error, get the explanation</title><link>https://kjetiljd.github.io/ai-for-coding/tips/004-paste-the-error/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/004-paste-the-error/</guid><description>Don&amp;#39;t Google cryptic errors. Paste them into chat and ask for the explanation first.</description></item><item><title>Tip #5: What actually belongs in your instruction file?</title><link>https://kjetiljd.github.io/ai-for-coding/tips/005-instruction-files-less-is-more/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/005-instruction-files-less-is-more/</guid><description>Less is more: hand-written, non-obvious rules beat auto-generated descriptions.</description></item><item><title>Tip #6: Your terminal just got an AI agent</title><link>https://kjetiljd.github.io/ai-for-coding/tips/006-copilot-cli/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/006-copilot-cli/</guid><description>Copilot CLI brings agentic coding to your terminal — reads files, runs commands, makes changes.</description></item><item><title>Tip #7: Let Copilot review every PR — automatically</title><link>https://kjetiljd.github.io/ai-for-coding/tips/007-automatic-code-review/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/007-automatic-code-review/</guid><description>Set up branch rulesets so Copilot reviews pull requests without anyone asking.</description></item><item><title>Tip #8: Teach your AI agent repeatable skills</title><link>https://kjetiljd.github.io/ai-for-coding/tips/008-agent-skills-intro/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/008-agent-skills-intro/</guid><description>Package step-by-step procedures as SKILL.md files the agent loads on demand.</description></item><item><title>Tip #9: Where to put your skills (and where they'll actually be found)</title><link>https://kjetiljd.github.io/ai-for-coding/tips/009-skill-placement/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/009-skill-placement/</guid><description>Project skills vs. personal skills, and how the agent discovers them.</description></item><item><title>Tip #10: Why your skills might not be triggering</title><link>https://kjetiljd.github.io/ai-for-coding/tips/010-skills-reliability/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/010-skills-reliability/</guid><description>The agent often ignores skills unless you tell it to look for them first.</description></item><item><title>Tip #11: What your agent already knows how to do</title><link>https://kjetiljd.github.io/ai-for-coding/tips/011-built-in-tools/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/011-built-in-tools/</guid><description>Built-in tools for file editing, search, shell commands, and GitHub — no setup needed.</description></item><item><title>Tip #12: MCP — the USB-C of AI tools</title><link>https://kjetiljd.github.io/ai-for-coding/tips/012-what-is-mcp/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/012-what-is-mcp/</guid><description>One open standard for connecting agents to external systems across all tools.</description></item><item><title>Tip #13: Give your agent a browser</title><link>https://kjetiljd.github.io/ai-for-coding/tips/013-browser-mcp/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/013-browser-mcp/</guid><description>Chrome DevTools MCP lets the agent click, inspect, and test web UIs from your terminal.</description></item><item><title>Tip #14: Your CLI tools are already AI tools</title><link>https://kjetiljd.github.io/ai-for-coding/tips/014-cli-tools-are-ai-tools/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/014-cli-tools-are-ai-tools/</guid><description>gh, git, jq, curl work without MCP — the agent just calls --help.</description></item><item><title>Tip #15: MCP servers eat your context window</title><link>https://kjetiljd.github.io/ai-for-coding/tips/015-mcp-context-cost/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/015-mcp-context-cost/</guid><description>Every connected server costs tokens every turn. Be selective.</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 #21: Meet OpenCode — the open source coding agent</title><link>https://kjetiljd.github.io/ai-for-coding/tips/021-opencode-provider-agnostic-agent/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/021-opencode-provider-agnostic-agent/</guid><description>A provider-agnostic coding agent that works with your existing Copilot license and 75+ other providers.</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><item><title>Tip #25: Your engineering skills didn't disappear — they shifted</title><link>https://kjetiljd.github.io/ai-for-coding/tips/025-engineering-skills-shifted/</link><pubDate>Fri, 17 Apr 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/025-engineering-skills-shifted/</guid><description>Less syntax, more architecture. Less typing, more judgment. AI rewards good engineering — but only if you stay sharp.</description></item><item><title>Tip #26: Before you wire AI agents to CI/CD, read this</title><link>https://kjetiljd.github.io/ai-for-coding/tips/026-clinejection-attack/</link><pubDate>Fri, 17 Apr 2026 00:00:00 +0000</pubDate><guid>https://kjetiljd.github.io/ai-for-coding/tips/026-clinejection-attack/</guid><description>The Clinejection attack showed how a malicious PR description can hijack an AI agent with CI/CD access. Know the risk before you automate.</description></item></channel></rss>