procore-reference-architecture

Implement Procore reference architecture with best-practice project layout. Use when designing new Procore integrations, reviewing project structure, or establishing architecture standards for Procore applications. Trigger with phrases like "procore architecture", "procore best practices", "procore project structure", "how to organize procore", "procore layout".

claude-code
2 Tools
procore-pack Plugin
saas packs Category

Allowed Tools

ReadGrep

Provided by Plugin

procore-pack

Claude Code skill pack for Procore (24 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the procore-pack plugin:

/plugin install procore-pack@claude-code-plugins-plus

Click to copy

Instructions

Procore Reference Architecture

Overview

Production-ready architecture patterns for Procore integrations.

Prerequisites

  • Understanding of layered architecture
  • Procore SDK knowledge
  • TypeScript project setup
  • Testing framework configured

Project Structure


my-procore-project/
├── src/
│   ├── procore/
│   │   ├── client.ts           # Singleton client wrapper
│   │   ├── config.ts           # Environment configuration
│   │   ├── types.ts            # TypeScript types
│   │   ├── errors.ts           # Custom error classes
│   │   └── handlers/
│   │       ├── webhooks.ts     # Webhook handlers
│   │       └── events.ts       # Event processing
│   ├── services/
│   │   └── procore/
│   │       ├── index.ts        # Service facade
│   │       ├── sync.ts         # Data synchronization
│   │       └── cache.ts        # Caching layer
│   ├── api/
│   │   └── procore/
│   │       └── webhook.ts      # Webhook endpoint
│   └── jobs/
│       └── procore/
│           └── sync.ts         # Background sync job
├── tests/
│   ├── unit/
│   │   └── procore/
│   └── integration/
│       └── procore/
├── config/
│   ├── procore.development.json
│   ├── procore.staging.json
│   └── procore.production.json
└── docs/
    └── procore/
        ├── SETUP.md
        └── RUNBOOK.md

Layer Architecture


┌─────────────────────────────────────────┐
│             API Layer                    │
│   (Controllers, Routes, Webhooks)        │
├─────────────────────────────────────────┤
│           Service Layer                  │
│  (Business Logic, Orchestration)         │
├─────────────────────────────────────────┤
│          Procore Layer        │
│   (Client, Types, Error Handling)        │
├─────────────────────────────────────────┤
│         Infrastructure Layer             │
│    (Cache, Queue, Monitoring)            │
└─────────────────────────────────────────┘

Key Components

Step 1: Client Wrapper


// src/procore/client.ts
export class ProcoreService {
  private client: ProcoreClient;
  private cache: Cache;
  private monitor: Monitor;

  constructor(config: ProcoreConfig) {
    this.client = new ProcoreClient(config);
    this.cache = new Cache(config.cacheOptions);
    this.monitor = new Monitor('procore');
  }

  async get(id: string): Promise<Resource> {
    return this.cache.getOrFetch(id, () =>
      this.monitor.track('get', () => this.client.get(id))
    );
  }
}

Step 2: Error Boundary


// src/procore/errors.ts
export class ProcoreServiceError extends Error {
  constructor(
    message: string,
    public readonly code: string,
    public readonly retryable: boolean,
    public readonly originalError?: Error
  ) {
    super(message);
    this.name = 'ProcoreServiceError';
  }
}

export function wrapProcoreError(error: unknown): ProcoreServiceError {
  // Transform SDK errors to application errors
}

Step 3: Health Check


// src/procore/health.ts
export async function checkProcoreHealth(): Promise<HealthStatus> {
  try {
    const start = Date.now();
    await procoreClient.ping();
    return {
      status: 'healthy',
      latencyMs: Date.now() - start,
    };
  } catch (error) {
    return { status: 'unhealthy', error: error.message };
  }
}

Data Flow Diagram


User Request
     │
     ▼
┌─────────────┐
│   API       │
│   Gateway   │
└──────┬──────┘
       │
       ▼
┌─────────────┐    ┌─────────────┐
│   Service   │───▶│   Cache     │
│   Layer     │    │   (Redis)   │
└──────┬──────┘    └─────────────┘
       │
       ▼
┌─────────────┐
│ Procore    │
│   Client    │
└──────┬──────┘
       │
       ▼
┌─────────────┐
│ Procore    │
│   API       │
└─────────────┘

Configuration Management


// config/procore.ts
export interface ProcoreConfig {
  apiKey: string;
  environment: 'development' | 'staging' | 'production';
  timeout: number;
  retries: number;
  cache: {
    enabled: boolean;
    ttlSeconds: number;
  };
}

export function loadProcoreConfig(): ProcoreConfig {
  const env = process.env.NODE_ENV || 'development';
  return require(`./procore.${env}.json`);
}

Instructions

Step 1: Create Directory Structure

Set up the project layout following the reference structure above.

Step 2: Implement Client Wrapper

Create the singleton client with caching and monitoring.

Step 3: Add Error Handling

Implement custom error classes for Procore operations.

Step 4: Configure Health Checks

Add health check endpoint for Procore connectivity.

Output

  • Structured project layout
  • Client wrapper with caching
  • Error boundary implemented
  • Health checks configured

Error Handling

Issue Cause Solution
Circular dependencies Wrong layering Separate concerns by layer
Config not loading Wrong paths Verify config file locations
Type errors Missing types Add Procore types
Test isolation Shared state Use dependency injection

Examples

Quick Setup Script


# Create reference structure
mkdir -p src/procore/{handlers} src/services/procore src/api/procore
touch src/procore/{client,config,types,errors}.ts
touch src/services/procore/{index,sync,cache}.ts

Resources

Flagship Skills

For multi-environment setup, see procore-multi-env-setup.

Ready to use procore-pack?