System Prompt

A system prompt is a set of background instructions that an AI reads before you say anything, defining how it should behave, what conventions to follow, and what rules to apply throughout the session. Think of it as the AI’s operating manual for your project: it sets the tone, constraints, and priorities before any conversation begins. In coding tools, system prompts are often stored as project files (like CLAUDE.md or .cursorrules) that get loaded automatically at the start of every session.

The Simple Version

When you talk to an AI, there are usually two layers of instruction. There’s what you type (the prompt), and then there’s a set of background instructions that the AI has already been given before you say anything. That background layer is the system prompt.

Think of it like hiring a new employee. Before they start taking assignments, you give them an orientation: here’s how we do things, here’s our style guide, here’s what matters, here’s what to avoid. A system prompt is that orientation for an AI tool.

Why It Matters

Without a system prompt, every AI interaction starts from zero. The AI doesn’t know your project’s conventions, your audience, your preferences, or your constraints. You end up repeating the same instructions every session.

With a system prompt, those instructions are baked in. The AI follows your rules automatically. It writes in your tone, follows your linking strategy, respects your file organization, and applies your conventions without being reminded.

Different tools use different formats for system prompts:

• Claude Code uses CLAUDE.md files
• Cursor uses .cursorrules files
• Windsurf uses rules files
• GitHub Copilot uses custom instructions

The format varies, but the concept is the same: persistent instructions that shape how the AI works on your project.

How It’s Used on This Site

CLAUDE.md is this site’s system prompt. It tells Claude Code the linking strategy (all terms link to glossary pages, no external links in blog posts), the blog tone (conversational, no em dashes, written for non-technical readers), the commit rules (never auto-commit, always explain what was done), and the content conventions (glossary terms must include on-site examples, tool entries must include “Try It” sections). Every session, Claude Code reads this file and follows these rules automatically.