culture-architect
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, cultural rituals by stage, and culture debt management. Use when building company values, assessing culture health, designing rituals, creating culture codes, handling culture clashes, managing through rapid growth, M&A integration, or when user mentions culture, values, culture debt, founder culture, culture code, psychological safety, engagement, eNPS, or remote culture.
What this skill does
# Culture Architect
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 from 5 people to 500.
## Keywords
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, psychological safety, culture scaling, engagement, eNPS, remote culture, hybrid culture, culture clash, employer brand, onboarding culture, performance culture, recognition
---
## Core Principle
**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 is descriptive. The work is closing the gap between stated and actual.
---
## Culture Diagnostic Decision Tree
```
START: "How is our culture?"
|
v
[Run the Values Audit]
Ask: "What did the last person who got promoted demonstrate?"
|
+-- Answer matches stated values --> Values are real. Check transmission.
| |
| v
| [Can a 30-day employee describe the culture accurately?]
| +-- YES --> Culture is operational. Maintain and evolve.
| +-- NO --> Transmission gap. Fix onboarding and rituals.
|
+-- Answer differs from stated values --> Values are performative.
|
v
[Do leaders model the real (non-stated) values?]
+-- YES --> Rewrite values to match reality, then iterate.
+-- NO --> Deeper problem: no coherent culture exists. Build from scratch.
```
---
## Framework 1: Mission / Vision / Values Workshop
### Mission (Why We Exist)
| Element | Test | Example |
|---------|------|---------|
| Present-tense | Is it about what we do now, not what we aspire to? | "We reduce preventable falls in elderly care" |
| Specific | Could a competitor claim the exact same thing? If yes, too generic. | Not "We make the world better" |
| Meaningful | Would something be lost if we disappeared? | Answer must be concrete |
### Vision (What Winning Looks Like)
| Quality | Bad | Good |
|---------|-----|------|
| Specificity | "Be the market leader" | "Every care home in Europe uses our system by 2030" |
| Falsifiability | "Transform healthcare" | "Reduce fall-related injuries by 50% in partner facilities" |
| Timeline | No date | 5-10 year horizon with milestones |
### Values (What We Actually Do)
| Rule | Explanation |
|------|-------------|
| 3-5 values maximum | More than 5 and none are memorable |
| Derived from observation | "What did our best hire do that nobody asked?" |
| Each has behavioral anchors | Specific enough to judge against |
| Include the tension | Good values have a cost ("Speed" means "we accept some risk") |
---
## Framework 2: Values-to-Behaviors Translation
This is the work that makes values operational. Every value needs concrete behavioral anchors.
| Value | Vague Version | Behavioral Anchor | How You'd Observe It |
|-------|---------------|-------------------|---------------------|
| Transparency | "We're open and honest" | "We share bad news within 24 hours, including to our manager" | Bad news travels fast, no surprises |
| Ownership | "We take responsibility" | "We don't hand off problems -- we own until resolved, even across team boundaries" | No orphaned issues |
| Speed | "We move fast" | "Decisions under $5K happen at team level, same day" | Low decision latency |
| Quality | "We don't cut corners" | "We stop the line before shipping something we're not proud of" | Teams delay launches for quality |
| Customer-first | "Customers are our priority" | "Any team member can escalate a customer issue to leadership, bypassing normal channels" | Escalation is celebrated, not punished |
### Translation Workshop (90 minutes)
```
For each value:
Step 1: State the value in 2-3 words
Step 2: Ask "How would a new hire know we live this on day 30?"
Step 3: Write 3 observable behaviors that prove this value
Step 4: Write 3 behaviors that violate this value
Step 5: Ask "What does this value cost us? What's the trade-off?"
Step 6: If no trade-off exists, it's not a value -- it's a platitude
Output: Value card with behaviors, violations, and trade-offs
```
---
## Framework 3: Culture Code Creation
A culture code is a public document that describes how you operate. It should attract the right people and repel the wrong ones.
### Culture Code Structure
| Section | Purpose | Key Question |
|---------|---------|-------------|
| 1. Who We Are | Mission, context, stage | "Why does this company exist?" |
| 2. Who Thrives Here | Specific behaviors, not adjectives | "What does success look like day-to-day?" |
| 3. Who Doesn't Thrive Here | Honest misfit description | "When have we made a bad hire? What was the pattern?" |
| 4. How We Make Decisions | Decision rights, speed expectations | "Who can decide what, and how fast?" |
| 5. How We Communicate | Channels, cadence, expectations | "What can I expect in response time and transparency?" |
| 6. How We Grow People | Career development, feedback | "What's my path here?" |
| 7. What We Expect of Leaders | Leadership behaviors | "How should managers behave?" |
### Culture Code Anti-Patterns
| Anti-Pattern | Why It Fails | Better Alternative |
|-------------|-------------|-------------------|
| "We're a family" | Families don't fire for performance | "We're a high-performing team that cares about each other" |
| Only positive traits | Not credible, doesn't help people self-select | Include "who doesn't thrive here" section |
| Aspirational, not descriptive | Creates cynicism when reality differs | Describe what IS, then iterate |
| Too long (> 15 pages) | Nobody reads it | Keep to 5-8 pages, link to details |
| Never updated | Becomes irrelevant as company scales | Review annually, update at each stage |
---
## Framework 4: Culture Health Assessment
Run quarterly. Anonymous. 8-12 questions maximum.
### Core Assessment Dimensions
| Dimension | Question Example | What It Measures |
|-----------|-----------------|-----------------|
| Psychological safety | "I can raise a concern without fear of negative consequences" | Trust in the system |
| Clarity | "I know how my work connects to company goals" | Strategic alignment |
| Fairness | "Decisions here are made consistently and transparently" | Trust in leadership |
| Growth | "I am learning and being challenged here" | Development opportunity |
| Trust in leadership | "I believe what leadership tells me" | Communication credibility |
| Recognition | "Good work is noticed and acknowledged" | Reward system health |
| Belonging | "I feel like I belong on this team" | Inclusion effectiveness |
| Autonomy | "I have enough freedom to do my best work" | Micromanagement detection |
### Score Interpretation and Response
| Score Range | Status | Action Required | Timeline |
|-------------|--------|-----------------|----------|
| 80-100% | Healthy | Document what works, celebrate, share practices | Maintain |
| 65-79% | Warning | Identify specific friction points, address top 2-3 | 30 days |
| 50-64% | Damaged | Leadership attention required, specific interventions | 14 days |
| < 50% | Crisis | All-hands intervention, external facilitation may be needed | Immediate |
### eNPS Integration
```
eNPS Question: "On a scale of 0-10, how likely are you to recommend
this company as a place to work?"
Promoters (9-10) - Detractors (0-6) = eNPS
-----------------------------------------
> 50 = Exceptional
30-50 = Good
10-30 = Acceptable
0-10 = Concerning
< 0 = Crisis
```
---
## Framework 5: Cultural Rituals by Stage
Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.
### Ritual Matrix
| Stage | Team Size | Key Rituals | Culture Risk |
|-------|-----------|-------------|-------------|
| Seed | < 15 | Weekly all-hands Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".