Claude Code
A getting-started guide and a skills library for business professionals and educators.
Start here
New to this repository? Work through it in order:
- Get started. What Claude Code adds beyond Claude chat and Cowork, how to install it on Mac or Windows, and how to set up your first project.
- Set up version history. Put your Claude Code environment under Git and sync two machines through a private GitHub repository, so every change to your skills and standards is tracked and reversible.
- Adopt handoffs and resume. End each session with a structured summary so the next one picks up where you left off.
- Browse the skills. Reusable workflows for slides, documents, analysis, and knowledge management. For a worked example of skills chained into one pipeline, see From Academic Paper to Slides.
About
This repository is maintained by Ben Bentzin, Associate Professor at the University of Texas at Austin McCombs School of Business. Ben teaches AI strategy to MBA students and corporate executives and serves as a McCombs Teaching Fellow focused on faculty AI integration. He writes about integrating AI into business at businessai.substack.com.
These skills were built to solve a practical problem: producing consistent, high-quality course materials (slide decks, exercises, case studies, analyses) across a full-semester MBA course on AI strategy. The tools here are the result of that work, generalized for anyone doing similar knowledge work with Claude Code.
What This Is
A collection of Claude Code skills, style guides, and templates that turn ad-hoc AI prompting into structured, repeatable professional workflows. The skills were developed for MBA course development but apply to any knowledge worker who creates documents, presentations, analyses, and research summaries.
Who This Is For
- Business faculty creating course materials (slides, exercises, cases, discussion outlines)
- Knowledge workers who produce recurring document types (presentations, proposals, reports)
- Claude Code users looking for practical skill examples beyond software development
- Anyone interested in building structured AI environments for professional work
Philosophy
Most AI usage today is ad-hoc: each conversation starts from scratch, corrections are forgotten when the chat ends, and output quality depends entirely on the user's prompting skill in the moment.
A structured AI environment changes this. Corrections persist as feedback memories. Recurring tasks run as reusable skills with built-in quality gates. Project context carries forward through handoffs. The investment is not in learning to code; it is in encoding your professional judgment into rules, skills, and quality standards that compound over time.
This repository publishes the skills, templates, and methodology behind that approach.
The Four-Layer Model
| Layer | Purpose | Example |
|---|
| Rules (CLAUDE.md) | Declarative constraints loaded every session | Writing standards, routing tables, delivery gates |
| Reinforcement (Memories) | Corrections and preferences that persist across sessions | "Save each project's deliverables to the top level of its folder" |
| Execution (Skills) | Procedural workflows loaded on demand | PDF-to-slides pipeline, exercise generator |
| Enforcement (Audit Agents) | Post-hoc quality checks that catch what the compiler misses | Beamer overlay audit, anonymization checklist |
See methodology.md for the full design rationale.
Set up your environment
The foundations the rest of this repository builds on. The Getting Started guide walks a newcomer through them, or you can go straight to each:
- git-sync (recipe). Version your
~/.claude environment with Git and keep two machines in sync through a private GitHub repository. You get history, diffs, and one-command revert on your skills, standards, and memory. Point Claude Code at the directory and it can do the setup for you.
- handoff-resume (protocol). Carry project context across sessions: end with a structured summary, and start the next session by reading it back.
- CLAUDE-template. A starting
CLAUDE.md to copy and customize for your identity, writing standards, and workflow.
Skills
Task-specific workflows, each loaded on demand when your request matches its triggers. Most install by copying SKILL.md into ~/.claude/skills/<skill-name>/SKILL.md; writing-voice-guide is a process guide you follow to build your own voice layer. Each skill's README documents its own install steps.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
