OkayTeacher
EN English 한국어 日本語 中文 हिन्दी বাংলা اردو Español Português Français Deutsch Русский العربية Bahasa Indonesia Tiếng Việt ไทย Türkçe

How to enable notifications

Notifications are unavailable in this browser or on this address. Try a supported browser on the secure SONUB site.

If notifications are blocked, allow them in your browser settings.

  1. Open the site controls beside the address bar, or your browser’s site settings. Set Notifications for this site to Allow.
  2. In your device settings, allow notifications for your browser and check Do Not Disturb or Focus.
  3. Return to SONUB, reload the page, and use the bell to enable notifications.

On iPhone or iPad, add SONUB to your Home Screen, open it there, then allow notifications.
Glossary · Learn more

Rules

Instruction files in .claude/rules/ that load with CLAUDE.md. See what it is, how it works, how it is used and what to watch for, with pictures and examples.

Back to the glossary Claude Code
A recipe box of tabbed index cards with one card lifted out, showing separate rule files loaded one at a time.

What it is

Rules are small files you keep in the .claude/rules/ folder. Instead of writing one very long CLAUDE.md, you give each topic its own file, such as testing.md or security.md, which is easier for a team to keep up to date. A rule without paths loads at the start of every session, with the same priority as .claude/CLAUDE.md. A rule with paths in its frontmatter loads only when reads, writes or edits a matching file, so it takes no space until it is needed.

How it works

  1. Make a .claude/rules/ folder
  2. Write one Markdown file per topic
  3. Add paths to limit when it loads
  4. Claude reads it when it matters

How to use it

  1. .claude/rules/testing.md

    one topic per file. like frontend/ also work, because every .md file inside is found.

  2. paths with "src/api/**/*.ts"

    the rule loads only when Claude works on a matching file, for example with the Read or Edit tool, or with cat on that file.

  3. ~/.claude/rules/

    your personal rules for every project on this computer. They load before project rules.

  4. ln -s ~/shared-claude-rules .claude/rules/shared

    share one set of rules across projects with a . A link that points outside the project needs your approval once.

Watch out

paths is the only frontmatter field reads in a rule, and if the is broken the rule loads as if it had no paths. If a user rule and a project rule disagree, Claude may follow either one, so keep them consistent. For instructions needed only for one kind of task, a is often better, because skills load only when called or relevant.

Original and official docs

This page explains the term in plain words. The original is the authority: if they differ, follow the original.