A field manual for colleagues onboarding to Claude Code at NBG — the stuff we wish we'd had on day 1.
Why this exists
Claude Code adoption is ramping across NBG over the next year. The AI unit got there first — by about six months — and made every beginner mistake on the way. We built this hub so the colleagues joining us next don't have to repeat them. Control keys, prompting habits, context discipline, the gotchas that look obvious in hindsight and opaque on day 1.
Who it's for
Primarily for colleagues new to joining over the next 6–12 months. Roles range from developers and data scientists to business analysts, operations, and managers. If your role isn't listed, you're still welcome — Claude Code is general-purpose by design.
Who built it
The hub is maintained by the AI unit. Contributions are welcome via pull requests against the repo on GitHub ↗. Every skill, tip, and glossary entry on this site is hand-authored or hand-reviewed by a team member. News items are AI-triaged from RSS feeds but the curation rules are ours.
Content rules
Tone: "what I wish I knew a year ago." Everything you read here was painful, surprising, or non-obvious to someone on the team. We assume the reader is a smart colleague new to Claude Code — not a stranger, not an expert. Bank-confidential content does not live on this repo (the repo is on a personal account); anything sensitive goes through compliance review first.
Where to start
New to Claude Code? Begin at Foundations, then Day 1 setup. Already using it? Jump straight to Skills, Tips, or Glossary. Tech news lives at AgentNews ↗ (curated by a colleague). General Claude-at-NBG onboarding (provisioning, policy, the bigger picture) lives at the Onboarding guide ↗.
How to reach us
Found a typo, a stale link, a confusing tip? Open a pull request or a GitHub issue at the repo ↗. For larger asks (a new skill, a section that's missing, a contribution you'd like to discuss) ping the team channel and we'll route it.