Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/culture-architect
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/culture-architect/SKILL.md \
-o ~/.claude/skills/culture-architect/SKILL.md Culture is what you DO, not what you SAY. This skill builds culture as an operational system — observable behaviors, measurable health, and rituals that scale.
culture, company culture, values, mission, vision, culture code, cultural rituals, culture health, values-to-behaviors, founder culture, culture debt, value-washing, culture assessment, culture survey, Netflix culture deck, HubSpot culture code, psychological safety, culture scaling
Culture = (What you reward) + (What you tolerate) + (What you celebrate)
If your values say “transparency” but you punish bearers of bad news — your real value is “optics.” Culture is not aspirational. It’s descriptive. The work is closing the gap between stated and actual.
Run this conversationally, not as a corporate offsite. Three questions:
Mission — Why do we exist (beyond making money)?
Vision — What does winning look like in 5–10 years?
Values — What behaviors do we actually model?
This is the work. Every value needs behavioral anchors or it’s decoration.
| Value | Bad version | Behavioral anchor |
|---|---|---|
| Transparency | ”We’re open and honest" | "We share bad news within 24 hours, including to our manager” |
| Ownership | ”We take responsibility" | "We don’t hand off problems — we own them until resolved, even across team boundaries” |
| Speed | ”We move fast" | "Decisions under €5K happen at team level, same day, no approval needed” |
| Quality | ”We don’t cut corners" | "We stop the line before shipping something we’re not proud of” |
| Customer-first | ”Customers are our priority" | "Any team member can escalate a customer issue to leadership, bypassing normal channels” |
Workshop exercise: Write your value. Then ask “How would a new hire know we actually live this on day 30?” If you can’t answer concretely, it’s not a value — it’s an aspiration.
A culture code is a public document that describes how you operate. It should scare off the wrong people and attract the right ones.
Structure:
See templates/culture-code-template.md for a complete template.
Anti-patterns to avoid:
Run quarterly. 8–12 questions. Anonymous. See references/culture-playbook.md for survey design.
Core areas to measure:
Score interpretation:
| Score | Signal | Action |
|---|---|---|
| 80–100% | Healthy | Maintain, celebrate, document |
| 65–79% | Warning | Identify specific friction — don’t over-react |
| 50–64% | Damaged | Urgent leadership attention + specific fixes |
| < 50% | Crisis | Culture emergency — all-hands intervention |
Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.
Seed stage (< 15 people)
Early growth (15–50 people)
Scaling (50–200 people)
Large (200+ people)
Value-washing: Listing values you don’t practice. Symptom: employees roll their eyes during values discussions.
Culture debt: Accumulating cultural compromises over time. “We’ll address the toxic star performer later.” Later compounds.
Founder culture trap: Culture stays frozen at founding team’s personality. New hires assimilate or leave.
Culture by osmosis: Assuming culture transmits naturally. It did at 10 people. It doesn’t at 50.
| When… | Culture Architect works with… | To… |
|---|---|---|
| Hiring surge | CHRO | Ensure culture fit is measured, not guessed |
| Org reorg | COO + CEO | Manage culture disruption from structure change |
| M&A or partnership | CEO + COO | Detect and resolve culture clashes early |
| Performance issues | CHRO | Separate culture fit from skill deficit |
| Strategy pivot | CEO | Update values/behaviors that the pivot makes obsolete |
| Rapid growth | All | Scale rituals before culture dilutes |
references/culture-playbook.md — Netflix analysis, survey design, ritual examples, M&A playbooktemplates/culture-code-template.md — Culture code document templateYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions