Onboarding

Our Principles

1. Concepts over code — Understand the WHY before writing the HOW
2. Solid foundations — Architecture, patterns, and principles FIRST
3. Domain-driven structure — The code screams the business, not the framework
4. Monolith-first — Start simple, extract when proven necessary
5. Test what matters — Domain and application logic always tested
6. Automate everything — CI/CD, linting, formatting, testing

First Day Setup

Prerequisites

• Git configured with company email
• Node.js >= 20 installed (use nvm or fnm)
• pnpm >= 9 installed
• Docker Desktop installed and running
• Flutter SDK installed (for mobile projects)
• IDE: VS Code or equivalent with extensions
• Access to GitHub organization
• Access to AWS console (if needed)

IDE Extensions (VS Code)

• Vue — Official (Volar)
• TypeScript
• ESLint
• Prettier
• Tailwind CSS IntelliSense
• Dart & Flutter (for mobile)
• Prisma

Clone and Run

# Clone the project
git clone [email protected]:vera-sesiom/{project-name}.git
cd {project-name}

# Install dependencies
pnpm install

# Copy environment variables
cp .env.example .env.local

# Start development database (Docker)
docker compose up -d

# Run database migrations
pnpm --filter @vera-sesiom/api prisma migrate dev

# Start all apps in development
pnpm dev

Skills to Read First

Read these skills in this order to understand how we work:

1. Architecture (Read First)

1. hexagonal-architecture — How we structure ALL code
2. monorepo-structure — How projects are organized

2. Stack-Specific (Read Your Stack)

3. vue-frontend — If working on frontend
4. node-backend — If working on backend
5. flutter-mobile — If working on mobile

3. Process (Read as Needed)

6. git-workflow — How we use Git
7. testing-strategy — How we test
8. code-review — How we review PRs
9. api-design — How we design APIs
10. security-practices — Security standards

For AI Agents

If you're an AI agent working on a Vera Sesiom project:

1. Load the relevant skills before writing any code
2. Follow hexagonal architecture — domain/application/infrastructure layers
3. Use the naming conventions from _shared/conventions.md
4. Check the project's ADRs for past architectural decisions
5. Run tests before considering work done
6. Follow git conventions — conventional commits, branch naming

Quick Reference

Key Contacts

Common Gotchas

1. Always use pnpm — not npm or yarn
2. Always work from develop — never branch from main (except hotfixes)
3. Run pnpm install after pulling — dependencies might have changed
4. Check .env.example after pulling — new env vars might be needed
5. TypeScript strict mode is ON — no shortcuts, type everything
6. Prisma generate after schema changes — pnpm --filter @vera-sesiom/api prisma generate