Team
4 humans with tailored tools. Each role gets a specific MCP config, skill set, and agent index — so everyone has exactly the tools they need, nothing more.
Team Members
Abdout — Builder
Engineering everything. Architecture, full-stack, deployment.
Ali — QA Engineer + Sales
Tests features (reports issues on GitHub), manages sales@databayt.org. Outreach for schools, sponsors, investors, early adopters, leads, clients, contributors.
Samia — R&D & Kun Caretaker
Research on Claude/Anthropic products, sharing economy models, revenue distribution. Taking care of Kun engine. Core vision contributor.
Sedon — Executor
Clear task maps, reliable delivery. Saudi operations: bank account, physical presence, payments.
Role-Specific MCP Configs
| Role | Config File | Servers |
|---|---|---|
| engineer | mcp.json | github, vercel, neon, stripe, sentry, figma, shadcn, browser, + 10 more |
| business | mcp-business.json | github, slack, linear, stripe, notion, browser, context7, memory-bank |
| content | mcp-content.json | github, slack, notion, browser, figma, context7, memory-bank, ref |
| ops | mcp-ops.json | github, slack, vercel, sentry, neon, stripe, browser, posthog, memory-bank |
Setup
One command per role — installs or updates config + runs health check:
# macOS/Linux
cd ~/kun && bash .claude/scripts/setup.sh engineer
cd ~/kun && bash .claude/scripts/setup.sh business
cd ~/kun && bash .claude/scripts/setup.sh content
cd ~/kun && bash .claude/scripts/setup.sh ops
# Windows (PowerShell)
cd ~/kun; .\.claude\scripts\setup.ps1 -Role engineer
cd ~/kun; .\.claude\scripts\setup.ps1 -Role business
cd ~/kun; .\.claude\scripts\setup.ps1 -Role content
cd ~/kun; .\.claude\scripts\setup.ps1 -Role opsRe-run anytime to update config after pulling latest from git.
What gets installed
| Layer | Common (all roles) | Scoped (per role) |
|---|---|---|
| CLAUDE.md | Shared instructions | — |
| Agents | All 45 agent definitions | Role-specific index |
| Commands | docs, repos, screenshot, codebase | Role-specific skills |
| Rules | All rules | — |
| Memory | Team, company data | — |
| Settings | — | Hooks (engineer) or minimal |
| MCP | — | Role-specific server set |
Daily Workflows
Abdout — Builder
> "dev" # Start dev server
> [build features] # Full agent fleet
> "build" # Validate
> "push" # Commit + push
> "deploy" # Ship to Vercel
Ali — QA + Sales
QA:
> Test features from URL checklists on GitHub Issues
> Report bugs as comments (not WhatsApp)
> Re-verify fixes, check off boxes
Sales (sales@databayt.org):
> Outreach: schools, sponsors, investors, early adopters, contributors
> Draft proposals, follow up leads
Samia — R&D
Cowork:
> Research Claude/Anthropic products
> Study sharing economy models
> Investigate revenue distribution
> Take care of Kun engine
Sedon — Executor
> [clear task map] # Well-defined tasks with steps
> Saudi operations # Bank, payments, physical presence
> Batch weekly # Monday map, Friday delivery
Config Health Monitoring
Each team member's config is verified continuously. Results report to a shared GitHub issue.
# Check local health
bash ~/.claude/scripts/health.sh
# Check + report to GitHub
bash ~/.claude/scripts/health.sh --report
# Windows
.\.claude\scripts\health.ps1
.\.claude\scripts\health.ps1 -ReportOr use the /health command inside Claude Code:
/health— local check + team dashboard from GitHub/health report— post local health to GitHub/health all— show all team members' latest status
Checks: core files exist, JSON valid, MCP count matches role, commands match scope, permissions correct, CLI installed, config staleness.