Home
Team
4 members — profiles, roles, social links, and capacity.
BehindReviewed 2026-04-01
Overview
Team of 4 building databayt. Each member has Claude Code configured for their role with tailored agents, MCPs, and permissions. The QA scope rule governs what Claude Code can do for non-architect roles.
Current Progress
- 4 roles defined: founder, developer/QA, creative, ops
- Abdout's full config tested and operational
- Ali onboarded for QA on hogwarts (#115)
- QA scope rule deployed (.claude/rules/qa-scope.md)
Areas of Improvement
- Samia and Sedon not yet onboarded to Claude Code
- Role-specific settings.json templates not generated
- Team profile pages need social links and todo integration
- Missing onboarding guide for non-technical members
References
Setup
- Run the team setup script: .claude/setup/team-setup.sh
- Select role: founder, developer, designer, or ops
- Script configures settings.json with role-appropriate MCPs
Usage
- Abdout — Builder: full agent fleet, all MCPs, all keywords
- Ali — QA Engineer + Sales: testing, issue reports, outreach (sales@databayt.org)
- Samia — R&D & Kun Caretaker: Claude/Anthropic research, sharing economy, Kun care
- Sedon — Executor: clear task maps, Saudi operations, batch weekly
Config Files
.claude/setup/team-setup.sh.claude/settings.json.claude/rules/qa-scope.md