SONUB
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.
Anthropic

Claude Code — Anthropic’s coding agent in your terminal

Type claude in a project folder and it starts. It reads your , answers questions about it, edits files and runs commands to test its own work. This page covers installing it and your first run, and links to the course chapters that go deeper.

Master — teams and automation: parallel work, GitHub, plugins, long tasks

Move from a tool you use alone to the way a team works. Run several sessions at once, call @claude from , share the team setup as a plugin, and let long jobs check their own work until they are done.

Git worktrees — several sessions at once

When two sessions edit the same files in one folder, they overwrite each other. worktree checks out the same into another folder on another , so you can run one Claude per folder and move several jobs forward at the same time.

  • claude --worktree <name> (-w) creates a worktree and branch in .claude/worktrees/<name>/ and starts there. If you finish with no changes, it is removed automatically.
  • Add .claude/worktrees/ to .gitignore, and list files Git ignores, such as .env, in .worktreeinclude to copy them into new worktrees.
  • Each worktree may need its own dependency install (npm install and so on).
  • Split work into independent jobs that touch different files, and merge them through PRs when done.
Terminal
# Claude Code makes the worktree for you (.claude/worktrees/<name>/)
claude --worktree feature-login
claude -w bugfix-cart

# Or with plain git
git worktree add ../myapp-search -b feature-search
cd ../myapp-search && claude

git worktree list
git worktree remove ../myapp-search

GitHub Actions — @claude in issues and PRs

Install Claude Code GitHub Actions and just writing @claude in an issue or comment makes Claude read the repository, fix things and open a PR or leave a review. It runs on GitHub's , so your computer can be off.

  1. Run /install-github-app in Claude Code in the terminal. It guides you through installing the GitHub app and adding the secret (ANTHROPIC_API_KEY or a token made with claude setup-token) — it needs gh and admin rights on the repository.
  2. A workflow file like the one above appears in .github/workflows/.
  3. Comment on an issue or PR, for example "@claude fix this bug".
  4. A person reviews and tests the PR Claude opened before merging it.
.github/workflows/claude.yml
name: Claude
on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
jobs:
  claude:
    if: contains(github.event.comment.body, '@claude')
    runs-on: ubuntu-latest
    permissions:
      contents: write
      pull-requests: write
      issues: write
      id-token: write
    steps:
      - uses: actions/checkout@v4
      - uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

Claude in Actions also reads the repository's instruction file (AGENTS.md, or CLAUDE.md). The easiest way to make it follow your rules is a well-written instruction file.

Plugins and marketplaces — bundle and share a setup

A plugin bundles skills, , hooks and into one. A marketplace is a repository with a list of plugins. A team installs the same toolbox with one command and updates it together.

  • /plugin — find, install, turn on and turn off plugins.
  • Add a marketplace with /plugin marketplace add <owner/repo> and install with /plugin install <plugin>@<marketplace>.
  • Only plugin.json goes in the plugin folder's .claude-plugin/. skills/, agents/ and hooks/ sit at the top of the folder. Test it with claude --plugin-dir ./my-plugin.
  • If you only share skills, npx skills add works too — that is how SONUB skills are shared.
my-plugin/
my-plugin/
├── .claude-plugin/
│   └── plugin.json        ← name, description, version
├── skills/
│   └── release-notes/SKILL.md
├── agents/
│   └── code-reviewer.md
├── hooks/
│   └── hooks.json
└── .mcp.json
Claude Code
/plugin marketplace add my-team/claude-plugins
/plugin install my-plugin@claude-plugins
/plugin

Running a team setup — so rules stay clear as they pile up

When many people and many AIs work in one repository, settings pile up fast. Decide what is shared and what is personal, and what is a request and what is enforced.

  • Shared (commit): AGENTS.md, .claude/settings.json, .claude/skills/, .claude/agents/, .mcp.json (and every folder's CLAUDE.md if you use CLAUDE.md)
  • Personal (do not commit): .claude/settings.local.json, ~/.claude/ — keep personal instructions in ~/.claude/CLAUDE.md (do not put a CLAUDE.local.md in the project, because it stops AGENTS.md)
  • Keep instruction files short. Add a rule only when the same mistake repeats, and delete rules that are wrong or no longer useful.
  • Enforce what must be followed with permissions (deny) and hooks, not with instructions.
  • Push company-wide rules down through managed settings — other settings cannot override them.

Long tasks — check its own work until it is done

A master gives Claude a "definition of done" and has it check that definition itself. With a test a machine can judge — tests, lint, a build — it can work for a long time without anyone watching.

  • Give the definition of done as commands — "until npm test and npm run lint both pass".
  • Have it write what is done and what is left in a file such as PROGRESS.md, so it can carry on even after the context is summarized or the session changes.
  • Have it commit after each small step, so you can roll back at any time.
  • Have it stop and write down why after three failed tries, to prevent loops that go nowhere.
  • When it is all done, hand a cross-review to another AI (for example codex review) or a subagent.

Master checklist

  • Only AGENTS.md in the project — every AI works from the same instructions (if you use CLAUDE.md, put one in every folder with the one line @AGENTS.md)
  • Permission rules let safe commands run without asking and block secret files with deny
  • Repeated jobs go to skills, big searches and reviews to subagents
  • What must be followed is enforced with hooks
  • Parallel work runs in worktrees; repeated work is automated with claude -p and GitHub Actions
  • You give the definition of done as commands and check the result yourself with the diff and tests

The tools change often. Keep up with new features through /claude-skill update in the claude-skill skill or the official change log (CHANGELOG).

Official documentation

Checked against the official documentation on 2026-10-18. These tools change often — if a command fails, see the official docs.

Guidelines

AI

Certificate

Study

Vibe Coding

Game

Practice

Teachers

Chat

Forum

Create

Community

More

Glossary

Pick a word you don't know. You'll see a simple explanation and related terms.

No matching term yet.

Pick a term to see its explanation.