Tools Required

This document lists the required and recommended tools for each role at EGI. All team members should have their tools installed and configured by the end of Day 1. The assigned buddy can assist with setup and configuration questions.

Tools by Role

Developer

Developers are expected to have the following installed and configured on their local machine:

Core Development

Tool	Purpose	Required Version
VS Code	Primary code editor	Latest stable
Node.js	JavaScript runtime	LTS version (check project .nvmrc files)
nvm	Node version management	Latest
Git	Version control	2.40+
Docker	Containerized development and testing	Latest stable
pnpm or npm	Package management	Per project configuration

VS Code Extensions (Recommended)

• ESLint -- Linting integration
• Prettier -- Code formatting
• Tailwind CSS IntelliSense -- Autocomplete for Tailwind projects
• GitLens -- Enhanced Git history and blame
• Prisma -- Schema highlighting and formatting (for projects using Prisma)
• Docker -- Container management from the editor

CLI Tools

• Vercel CLI (vercel) -- Local preview deployments and project linking
• GitHub CLI (gh) -- PR creation, issue management, repo operations
• Claude Code (claude) -- AI-assisted development (follow team guidelines for usage)

Configuration

• Git must be configured with the developer's EGI email: git config --global user.email "firstname.lastname@egintegrations.com"
• SSH keys must be generated and added to GitHub for repository access
• GPG signing is recommended but not currently required

Designer

Tool	Purpose	Notes
Penpot	UI/UX design and prototyping	Open-source, browser-based
VS Code	Asset editing and design token management	When working with code repos
Git	Version control for design assets	Basic proficiency expected
Browser DevTools	Inspecting implemented designs	Chrome or Firefox

Project Manager

Tool	Purpose	Notes
SuiteDash	Project management, task tracking, client communication	Primary PM tool
Browser	Accessing Vercel dashboards, PostHog analytics, GitHub PRs	Chrome or Firefox recommended
ERPNext	Resource planning and operational reporting	Access provided by operations lead

Communication Tools (All Roles)

Tool	Purpose	Setup
Slack	Day-to-day team communication	Desktop and mobile apps recommended
Email	External communication, formal internal communication	EGI account via web or mail client
Video conferencing	Meetings, pair programming, design reviews	Google Meet or team-agreed platform

Slack Channel Structure

All team members should be in these default channels:

• #general -- Company-wide announcements and discussions
• #engineering -- Technical discussions, architecture decisions, code questions
• #operations -- Operational requests, access issues, tooling questions

Project-specific channels are created as needed and follow the naming convention #project-[name].

Monitoring and Analytics

Tool	Role Access	Purpose
PostHog	Developers, PMs	Product analytics, feature flags, session replay
Vercel Analytics	Developers, Ops	Deployment status, performance monitoring, error tracking
Cloudflare	Ops only	DNS management, DDoS protection, edge caching

Version Control (All Technical Roles)

GitHub

GitHub is the single source of truth for all code at EGI. Every developer and designer working with code must:

• Have a GitHub account added to the EGI organization
• Understand the branching strategy (feature branches off main, PRs for all changes)
• Be familiar with PR review expectations (see development workflow documentation)
• Never commit secrets, credentials, or environment variables to any repository

Repository Access

Repository access is granted on a need-to-know basis:

• Developers receive write access to their assigned project repositories
• Additional repository access requires manager approval
• Organization-wide read access is not granted by default

Tool Installation Verification

At the end of Day 1, the new hire should verify their setup by completing the following:

1. Clone a project: git clone an assigned repository via SSH
2. Install dependencies: Run the project's install command (pnpm install or npm install)
3. Run locally: Start the development server and confirm it loads in the browser
4. Connect to Slack: Send a message in #general confirming setup is complete
5. Access Vercel: Log in to the Vercel dashboard and locate the assigned project

If any step fails, post in #operations for assistance. Setup blockers should be resolved within 4 business hours.