Blog
NOTIFICATIONS LANDSCAPE

Introducing Courier Skills: Teaching Your AI IDE to Build Notifications Correctly

Thomas Schiavone

January 30, 2026

Courier Agent Skills for Cursor and Claude Code

Table of contents

What Are Agent Skills (and How They Compare to MCP)?

Introducing Courier Skills

What Courier Skills Covers

Installation

Try It Out

Introducing Courier Skills: Teaching Your AI IDE to Build Notifications Correctly

I’ve been living in Cursor for the past couple of months. It’s been a while since I was writing code daily, but AI IDEs pulled me back in. Staying in flow, iterating quickly, and thinking at a higher level reminded me how much I enjoy building.

When you use an AI IDE heavily, you start to notice a pattern. The model is very good at generating plausible implementations, but it has no durable understanding of domain constraints. Each prompt is treated as a fresh problem, even when the underlying system has well-defined rules, invariants, and preferred patterns.

Notifications are a good example of this. They are shaped by compliance requirements, delivery semantics, channel-specific limits, and user experience tradeoffs. Those constraints do not change often, but they are rarely obvious from a single doc page or code snippet.

Agent Skills address this by giving the model stable, opinionated context. Instead of rediscovering rules on every prompt, the AI can reason from a shared baseline. The result is guidance that is not just syntactically correct, but aligned with production reality.

That is the gap Courier Skills is designed to fill.


What Are Agent Skills (and How They Compare to MCP)?

Agent Skills are markdown-based knowledge files that give AI IDEs durable domain context.

They provide passive guidance. When relevant, the AI reads them and applies that knowledge while generating code or architectural suggestions. Skills are well suited for encoding best practices, constraints, invariants, and recommended patterns that do not change frequently.

This is different from MCP, or Model Context Protocol.

MCP gives AI assistants active capabilities such as running queries, calling APIs, or fetching live data from external systems. It is powerful, but it requires additional infrastructure and ongoing maintenance.

The distinction is simple:

  • Agent Skills provide knowledge and judgment
  • MCP provides execution and integration

They complement each other well. Agent Skills establish the mental model. MCP enables action based on that model.

In practice, this changes how your AI IDE behaves. When you ask it to add a channel, design a notification flow, or extend an existing system, it no longer starts from a blank slate. It already understands the constraints that shape those decisions, which means less back and forth, fewer almost-right solutions, and more confidence in what you ship.


Introducing Courier Skills

Courier Skills is a curated, open-source collection of Agent Skills for building production-grade notifications.

We built it by distilling the domain knowledge our team uses every day. This includes how different channels behave, where teams tend to run into issues, and which patterns consistently hold up in production. Instead of spreading that context across documentation, examples, and internal knowledge, we captured it in a form AI IDEs can apply directly.

The goal is not to teach your AI how to call an API. It is to teach it how to reason about notifications as a system.


What Courier Skills Covers

Courier Skills encodes the domain knowledge required to build production-grade notifications across common channels and use cases.

Channels
Email, SMS, Push notifications, In-app Inbox, Slack, Microsoft Teams, and WhatsApp.

Patterns and guidance
Authentication and security notifications, order and billing updates, account alerts, onboarding and engagement flows, multi-channel routing, user preferences, compliance, reliability patterns, batching, and rate limits.

This is the knowledge teams usually accumulate over time. Courier Skills makes it available upfront.


Installation

Courier Skills works with Cursor, Claude Code, and other AI IDEs that support Agent Skills.

Cursor (global): git clone https://github.com/trycourier/courier-skills.git ~/.cursor/skills/courier-skills

Cursor (project-specific): git clone https://github.com/trycourier/courier-skills.git .cursor/skills/courier-skills

Claude Code: git clone https://github.com/trycourier/courier-skills.git ~/.claude/skills/courier-skills

Once installed, your AI assistant can reference Courier Skills automatically when working on notification-related tasks.


Try It Out

We built Courier Skills for ourselves first. It led to fewer corrections, fewer surprises, and more predictable outcomes when building notification flows in AI IDEs.

If you are using an AI IDE today, install the skills and try your next notification task with them in place. Pay attention to how the model reasons, not just what it outputs.

The project is open source, and contributions are welcome.

Explore the code on GitHub:
github.com/trycourier/courier-skills

Happy building.

Similar resources

Apple OS 27 lineup (WWDC 2026)
Notifications LandscapeGuide

watchOS 27 Notifications: What Changed and How to Adapt Your Product Sends

Apple's watchOS 27, announced at WWDC 2026, presents Apple Watch notifications based on relevance instead of arrival time and expands contextual Smart Stack widgets. Because watch notifications mirror iPhone push, your push strategy is your watch strategy. This guide covers what product and B2B notification teams should change: setting APNs interruption levels honestly, writing glanceable payloads, routing by urgency across push, email, SMS, and in-app inbox, using widgets for status content, and handling the split audience after watchOS 27 drops Series 8, Ultra 1, and SE 2.

By Kyle Seyler

June 09, 2026

Courier Inbox
Product ManagementNotifications Landscape

Your Notification Center, Your Competitive Edge

The in-app inbox is the most valuable notification surface you own. Every other channel has a gatekeeper: push, email, and SMS all run through someone else's filters. The inbox is the one surface where you set the rules. Courier Inbox ships as a drop-in component backed by a hosted API that stores messages, syncs read state across devices in real time, and integrates with your other channels. SDKs for React, Web Components, React Native, Flutter, iOS, and Android. Install it with an AI coding agent or a few lines of code. Theme it, customize the renderers, or go fully headless.

By Kyle Seyler

April 22, 2026

5 Best Platforms for Product Messages 2026 - Header
Notifications LandscapeUser ExperienceProduct Management

5 Best Platforms for Product Messages in 2026

Product messages are a requirement for every SaaS product, but most teams outgrow their initial setup fast. You start with one email provider, add push, then SMS, and suddenly you're maintaining multiple integrations with no shared routing, no preference management, and every copy change requires a deploy. This guide compares five platforms that solve different versions of this problem: Courier for cross-channel messaging with AI tooling, Resend for developer-friendly transactional email, Customer.io for marketing-adjacent journeys, Supabase for built-in auth emails, and Novu for open-source self-hosted infrastructure.

By Kyle Seyler

April 15, 2026

Multichannel Notifications Platform for SaaS

Products

Platform

Integrations

Customers

Blog

API Status

Subprocessors


© 2026 Courier. All rights reserved.