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 and reload the page. Once notifications are on, the bell disappears.

On iPhone or iPad, add SONUB to your Home Screen, open it there, then allow notifications.
Admin Log in Display theme Default theme Dark theme Pink theme Chat 1:1 Chat Group Chat Forum Notices News Suggestions Introductions Main menu Log out

Claude Code — Anthropic’s agentic coding tool in your terminal

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

Master — parallel work, GitHub, plugins, long tasks

Git worktrees — several sessions at once

)

When two edit the same files in one folder, they overwrite each other. checks out the same into another folder on another , so you can run one 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 , and list files ignores, such as , in .worktreeinclude to copy them into new worktrees.
  • Each worktree may need its own dependency install ( install and so on).
  • Split work into independent jobs that touch different files, and merge them through when done.
# 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 and just writing @claude in an issue or PR comment makes Claude read the repository, fix things and open a PR or leave a review. It runs on '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 (ANTHROPIC_API_KEY or a made with claude ) — it needs and admin rights on the repository.
  2. A like the one above appears in .github/workflows/.
  3. Comment on an issue or PR, for example "@claude fix this ".
  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 (, or ). The easiest way to make it follow your is a well-written instruction file.

Plugins and marketplaces — bundle and share a setup

)

A bundles , , and into one. A 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, 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 (): AGENTS.md, , , , (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 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 (deny) and hooks, not with instructions.
  • Push company-wide rules down through — 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, , a build — it can work for a long time without anyone watching.

  • Give the definition of done as commands — "until npm test and 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 is summarized or the session changes.
  • Have it commit after each complete, working step that can stand on its own, so you can that step independently. Do not split one unfinished change across several commits that must be undone together.
  • If three attempts to solve the same problem fail, have Claude stop and write down what it tried, why those attempts failed and what is blocking progress, before it tries again. This stops loops that go nowhere.
  • When it is all done, hand a to another (for example codex review) or a subagent.

Master practice — several sessions and automation

)
  1. Make a second working folder with git worktree add ../my-project-b -b try-b, run claude in each folder and give each a different small job. If git status changes separately in the two folders, it worked.
  2. Make a one-line review command: git | claude -p "List bugs in this diff". Put in a bug on purpose and check that it finds it.
  3. Write one team rule (for example, run the tests before committing) in AGENTS.md and also enforce it with a hook. Break the rule on purpose and check that the hook stops it.
  4. Bundle one of your skills and one subagent into a plugin as in the plugins section above, install it, and check that it loads in another project too.
  5. Give a long task with a written as a command (for example, npm test passes). When it says it is done, check the diff and the test result yourself.

If you get stuck: list worktrees with git worktree list and remove one with git worktree remove. If a hook blocks too much, take it out of settings.json for a moment and check with /hooks. Done all five? Check yourself with the checklist below.

Master checklist — the whole path from Basics to Master

)
  • Basics — you run claude in a Git project folder, plan first with /plan, approve only what belongs to the job and check git status and git diff before you commit
  • Intermediate — for web work the connection is on, so Claude opens and checks the page it changed
  • Intermediate — only AGENTS.md in the project, so every AI works from the same instructions. If you use CLAUDE.md, every folder that has an AGENTS.md also has a CLAUDE.md that references it with the line @AGENTS.md on its own
  • Intermediate — let safe commands run without asking and block secret files with deny
  • Intermediate — you watch the context with /context, shrink it with /compact and use when you switch to a new, unrelated task; each request says where, what and how to check
  • Advanced — repeated jobs go to skills (check the names in use with /skills first), big searches and reviews to subagents
  • Advanced — what must be followed is enforced with hooks and permissions, outside come in through MCP servers you trust, and one-off jobs run in with claude -p
  • Master — runs in worktrees, and @claude in GitHub Actions takes on issues and PRs
  • Master — the team's skills, subagents, hooks and MCP servers are shared as one plugin, and shared and personal settings are kept apart
  • Master — you give the definition of done as commands, commit each complete working step 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 ().

Official documentation

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

Claude Code lab Sonub Lab — Claude Code practice Use the real Claude Code on your own computer in this page’s terminal — install it in three steps and run sonub start. It uses the SONUB practice brain, so you need no Claude subscription or API key.
Keep going

Guidelines

AI

Agent Tools

Vibe Coding

AI in Practice

Certificate

AI Class

IT Basics

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.
Reading window