A presentation for professionals
Understanding AI, Language Models, and the Future of Software
Press → to begin
Context
Part 1 — Foundations
Software that can perform tasks that normally require human intelligence.
See images, hear speech, read text
Analyze, compare, draw conclusions
Write text, create code, produce content
| Type | What It Does | Example |
|---|---|---|
| Traditional ML | Finds patterns in structured data | Fraud detection, credit scoring |
| Computer Vision | Understands images and video | Document scanning, ID verification |
| Speech AI | Converts speech ↔ text | Call center transcription |
| Large Language Models | Understands and generates text & code | ChatGPT, Claude, Gemini |
Today we focus on Large Language Models (LLMs) — the technology behind ChatGPT and Claude.
An LLM is software trained on enormous amounts of text to understand and generate human language.
Think of an LLM as the world's most well-read intern.
The quality of the output depends heavily on the quality of your prompt — what you ask and how you ask it.
| Term | Plain English |
|---|---|
| Prompt | The question or instruction you give the AI |
| Context | Background information the AI uses to answer better |
| Token | A chunk of text (~¾ of a word). How AI measures length |
| Context Window | How much text the AI can "see" at once (like working memory) |
| Hallucination | When the AI makes something up that sounds plausible but is wrong |
| Model | The trained AI system itself (GPT-4, Claude, etc.) |
| Fine-tuning | Additional training to specialize the model for a specific use |
| API | A way for software to talk to the AI programmatically |
🌟
ChatGPT, GPT-4
First to go mainstream. Backed by Microsoft.
◈
Claude
Focus on safety & reliability. Claude Code for developers.
◆
Gemini
Integrated into Google products. Multimodal.
Part 2 — From Chat to Code
Each step gives the AI more context and more capability.
You paste code into a chat window. The AI responds. You copy-paste back. Works, but lots of back-and-forth.
The AI lives inside your project. It reads your files, runs commands, edits code directly. It's a collaborator, not a chatbot.
Code is instructions written for a computer in a language it can understand.
Calculate the total revenue for Q4 2025 and show it as a formatted table.
revenue = df[df['quarter'] == 'Q4-2025'] total = revenue['amount'].sum() print(f"Q4 Revenue: ${total:,.2f}")
Most people interact with computers through graphical interfaces — clicking buttons, dragging files.
A terminal (or command line) lets you control the computer by typing text commands.
Developers use it because it's faster, more precise, and automatable.
Terminal
$ ls project/ README.md src/ tests/ package.json $ claude Claude Code v1.0 Ready. What would you like to do? > Find all files that handle user authentication and explain how they work Searching your codebase...
Part 3 — Claude Code
An AI coding agent that lives in your terminal. Made by Anthropic (the company behind Claude).
Explores your entire codebase, understands file relationships
Creates and edits files directly in your project
Executes commands, runs tests, installs packages
Think of it as: a senior developer sitting next to you, with access to your project files, who never gets tired.
| ChatGPT / Claude.ai | Claude Code | |
|---|---|---|
| Where | Web browser | Your terminal, in your project |
| Context | Only what you paste in | Your entire codebase |
| Edits files | No — gives you text to copy | Yes — edits directly |
| Runs code | Limited sandbox | Full access to your tools |
| Remembers project | No (fresh each chat) | Yes (via CLAUDE.md) |
| Connects to tools | Limited plugins | MCP servers (GitHub, DBs, etc.) |
| Customizable | Minimal | Skills, hooks, plugins |
| Best for | Quick questions, drafting | Real development work |
A simple loop:
You stay in control at every step. Claude asks for permission before making changes.
Core Concepts
The #1 factor determining AI quality is how much relevant context you provide.
You: "Fix the bug"
AI: "What bug? In what project?
What language? What file?"
The AI is guessing.
You: "Fix the login bug"
[Claude Code already knows:]
- Your tech stack (React + Node)
- The auth system (JWT tokens)
- Recent git changes
- The error in the logs
The AI gives a precise fix.
This is why Claude Code exists. It gives the AI automatic access to your entire project as context.
How you ask determines what you get. A few principles:
"Make this better"
Better how? Faster? Prettier? More secure? The AI guesses.
"Add input validation to the login form. Check that email is valid and password is at least 8 characters. Show error messages below each field."
AI doesn't read words — it reads tokens. A token is roughly ¾ of a word.
"The quarterly revenue report" = 4 tokens: [The] [quarterly] [revenue] [report] "$1,234,567.89" = 6 tokens: [$] [1] [,234] [,567] [.89]
The maximum amount of text the AI can "see" at once. Think of it as working memory.
| Model | Context Window | Roughly |
|---|---|---|
| GPT-4 | 128K tokens | ~200 pages |
| Claude | 200K tokens | ~300 pages |
| Gemini | 1M tokens | ~1500 pages |
Bigger window = can work with more code at once.
By default, an LLM can only talk. Tools let it take actions.
Look at your project code and documents
Make changes to existing code
Execute scripts, install packages, run tests
Find files and patterns in your codebase
Fetch documentation or API data
GitHub, databases, Slack, etc.
Claude Code comes with all of these built in. You can add more via MCP servers.
An agent is an AI that can plan, use tools, and complete multi-step tasks on its own.
You ask → it answers → done.
One question, one response. No actions taken.
You ask → it thinks → reads files → plans → edits code → runs tests → fixes errors → reports back.
Multi-step, autonomous, uses tools along the way.
Claude Code asks before it acts. You're always in control.
Claude wants to run: npm test [Allow] [Deny] [Always allow]
"Always allow" means you won't be asked again for npm test.
For finance teams: this permission model is critical. You can enforce policies about what the AI can and cannot do in your codebase.
Part 4 — Extensibility
5 ways to customize and extend Claude Code
Feature 1 of 5
A file that tells Claude everything about your project so it doesn't have to ask.
You: "Run the tests"
AI: "What test framework?
What command?
Where are the tests?"
You: "Jest. npm test. In /tests"
AI: "Got it..."
(Repeat every session)
You: "Run the tests" AI: "Running npm test..." Claude already knows: - Framework: Jest - Command: npm test - Location: /tests - Style: 2-space indent - Language: TypeScript
CLAUDE.md
# Risk Analytics Platform ## Tech Stack - Python 3.11, FastAPI - PostgreSQL 15 - React frontend ## Commands - `make test` — Run all tests - `make lint` — Code quality check - `make deploy-staging` — Deploy ## Rules - All monetary values use Decimal - Never use floating point for money - Require type hints on all functions - Every endpoint needs auth middleware
./CLAUDE.md | Whole team sees it |
./CLAUDE.local.md | Only you see it |
~/.claude/CLAUDE.md | All your projects |
claude
> /init
# Auto-generates based on
# your project structure!
CLAUDE.md
For larger teams, organize rules into separate files:
your-project/
├── CLAUDE.md
└── .claude/
└── rules/
├── code-style.md
├── security.md
├── api-standards.md
└── compliance.md
All .md files in rules/ are loaded automatically.
# .claude/rules/api-standards.md --- paths: - "src/api/**/*.py" --- All API endpoints must: - Validate input with Pydantic - Log to the audit trail - Return standard error format - Require authentication
These rules only activate when Claude works on matching files.
Feature 2 of 5
Turn any workflow into a reusable /command.
🔄
You type the same detailed instructions every time you want Claude to review code, deploy, or run a specific workflow.
⚡
Type /review and Claude already knows exactly what to check, how to format the output, and what standards to follow.
Skills
Create a file at .claude/skills/review/SKILL.md:
--- name: review description: Review code for quality user-invocable: true argument-hint: "[file]" --- Review the specified code for: 1. Bugs — logic errors, edge cases 2. Security — injection, auth issues 3. Performance — slow queries, leaks 4. Style — naming, readability For each issue: - State the problem - Show the line - Suggest a fix
# In Claude Code, just type: > /review > /review src/auth.py
.claude/skills/ | Project (shared) |
~/.claude/skills/ | Personal (all projects) |
$ARGUMENTS — pass parameters!`command` — inject shell outputcontext: fork — run in isolationSkills
Review code changes for compliance with SOX, PCI-DSS, or internal audit requirements.
Validate data pipeline code ensures no silent data loss, null handling, and type safety.
Generate plain-English documentation for quantitative models and algorithms.
Check for hardcoded credentials, insecure API calls, and data exposure risks.
Plan and execute database schema changes with rollback strategies.
Generate an incident report from git logs and error traces.
Skills encode your team's best practices so everyone follows them consistently.
Feature 3 of 5
Connect Claude to the tools your team already uses.
MCP = Model Context Protocol — a standard way for AI to talk to external services.
The MCP server acts as a bridge. Claude talks to it using a standard protocol.
MCP Servers
# Connect to GitHub claude mcp add \ --transport http \ github \ https://api.githubcopilot.com/mcp/ # Then authenticate: > /mcp
Now Claude can create PRs, review code, manage issues.
# Connect to PostgreSQL claude mcp add \ --transport stdio \ mydb \ -- npx -y @bytebase/dbhub \ --dsn "postgresql://..."
Now Claude can query your database in natural language.
--scope project to save the config in .mcp.json, which you commit to git. Everyone gets the same integrations.
MCP Servers
🐙
PRs & issues
🗃
Database queries
🚨
Error tracking
💬
Messaging
📝
Knowledge
📋
Project mgmt
💳
Payments
🔧
Build your own
You: "What were the top 5 errors in production this week?" Claude: [queries Sentry via MCP, analyzes results] "Here are the top 5 errors, ranked by frequency..." You: "Fix the most common one" Claude: [reads the stack trace, finds the file, edits the code, runs tests]
Feature 4 of 5
Scripts that run automatically when events happen in Claude Code.
Like setting up rules: "Whenever X happens, do Y."
Hooks
{
"hooks": {
"PostToolUse": [{
"matcher": "Edit|Write",
"hooks": [{
"type": "command",
"command": "prettier --write"
}]
}]
}
}
Every time Claude edits a file, it gets auto-formatted.
{
"hooks": {
"PreToolUse": [{
"matcher": "Edit|Write",
"hooks": [{
"type": "command",
"command": "... | grep '.env'
&& exit 2 || exit 0"
}]
}]
}
}
exit 2 = block the action. Protects secrets.
Hooks
| Event | When | Blocks? | Use case |
|---|---|---|---|
PreToolUse | Before any tool runs | Yes | Protect files, enforce policies |
PostToolUse | After tool succeeds | No | Format, lint, log changes |
UserPromptSubmit | You hit Enter | Yes | Input validation, injection checks |
Stop | Claude finishes | Yes | Verify all tasks completed |
SessionStart | Session begins | No | Load environment, greet |
SessionEnd | Session ends | No | Cleanup, save state |
Notification | Permission prompt | No | Desktop notification |
Configure in .claude/settings.json or interactively with /hooks.
Feature 5 of 5
Bundle skills + hooks + integrations into one installable package.
Any or all of these. A plugin can be simple (one skill) or comprehensive.
Plugins
my-plugin/ ├── .claude-plugin/ │ └── plugin.json ← manifest ├── skills/ │ ├── review/SKILL.md │ └── deploy/SKILL.md ├── hooks/ │ └── hooks.json ├── agents/ │ └── analyzer.md └── .mcp.json ← integrations
{
"name": "finance-toolkit",
"description": "Finance team
standards & workflows",
"version": "1.0.0"
}
# Test locally claude --plugin-dir ./my-plugin # Or install from marketplace > /plugin install
Plugins
| Scenario | Best approach |
|---|---|
| Quick project notes | CLAUDE.md Just write a CLAUDE.md |
| One reusable workflow | Skill Create a single SKILL.md file |
| Connect to a service | MCP Add an MCP server |
| Automatic code formatting | Hook Add a PostToolUse hook |
| Enforce security policies | Hook Add a PreToolUse hook |
| Share all of the above with your team | Plugin Bundle into a plugin |
| Distribute to the community | Plugin + marketplace |
Start simple. You can always package things into a plugin later.
Bonus
Fine-grained control over what Claude can do:
{
"permissions": {
"allow": [
"Bash(npm test *)",
"Bash(git status)",
"Read(./src/**)"
]
}
}
{
"permissions": {
"deny": [
"Bash(rm *)",
"Read(.env*)",
"Bash(curl *)",
"Read(./secrets/**)"
]
}
}
Part 5 — Real World
A day in the life with Claude Code
Your team builds internal risk analytics tools. Here's how Claude Code fits in:
Claude loads CLAUDE.md, knows your stack, compliance rules, and team conventions.
Type /review src/risk_engine.py. Skill runs automated review checking for bugs, security, and your internal standards.
Claude queries Sentry (via MCP) for the error, reads the stack trace, finds the bug, and proposes a fix.
Hooks auto-format every file Claude edits, block changes to production configs, and log all commands to audit trail.
They install the team plugin. Instantly get all skills, hooks, and integrations. Productive from day one.
deny rules for sensitive filesYour Project
CLAUDE.md — context
Skills — commands
Hooks — automation
Settings — permissions
Claude Code
AI Agent
Reads, writes, runs commands
Plans and executes
Asks for permission
External
MCP: GitHub
MCP: Database
MCP: Sentry
Plugins
npm install -g @anthropic-ai/claude-code
— requires Node.js
cd my-project && claude
/init
— auto-generates CLAUDE.md
claude mcp add --transport http github https://api.githubcopilot.com/mcp/
.claude/skills/review/SKILL.md and start using /review
/cost/compact to reduce context sizecontext: fork use separate context| Question | Answer |
|---|---|
| "Is our code sent to the cloud?" | Code is sent to Anthropic's API for processing. Enterprise plans offer enhanced data privacy. Nothing is used for training. |
| "Can it access production?" | Only what you configure. Use read-only DB connections. Use deny rules for sensitive paths. |
| "Will it replace developers?" | No. It's a productivity multiplier. Developers still design, review, and make decisions. |
| "How accurate is it?" | Very good, but not perfect. Always review changes, especially for financial calculations. |
| "Can we use it offline?" | No. It requires an internet connection to reach the API. |
| ChatGPT | GitHub Copilot | Claude Code | |
|---|---|---|---|
| Type | Chatbot | Autocomplete | Agent |
| Where | Browser | IDE plugin | Terminal |
| Reads codebase | No | Current file | Entire project |
| Edits files | No | Suggestions | Direct edits |
| Runs commands | Sandbox | No | Full access |
| External tools | Limited | No | MCP servers |
| Customizable | Minimal | Minimal | Skills, hooks, plugins |
| Multi-step tasks | Manual | No | Autonomous |
These tools complement each other. Many teams use multiple tools for different tasks.
Thank You
From ChatGPT to Claude Code
Questions?