replit-reference-architecture
Implement Replit reference architecture with best-practice project layout. Use when designing new Replit integrations, reviewing project structure, or establishing architecture standards for Replit applications. Trigger with phrases like "replit architecture", "replit best practices", "replit project structure", "how to organize replit", "replit layout". allowed-tools: Read, Grep version: 1.0.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed Tools
No tools specified
Provided by Plugin
replit-pack
Claude Code skill pack for Replit (30 skills)
Installation
This skill is included in the replit-pack plugin:
/plugin install replit-pack@claude-code-plugins-plus
Click to copy
Instructions
# Replit Reference Architecture
## Overview
Production-ready architecture patterns for Replit integrations.
## Prerequisites
- Understanding of layered architecture
- Replit SDK knowledge
- TypeScript project setup
- Testing framework configured
## Project Structure
```
my-replit-project/
βββ src/
β βββ replit/
β β βββ 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/
β β βββ replit/
β β βββ index.ts # Service facade
β β βββ sync.ts # Data synchronization
β β βββ cache.ts # Caching layer
β βββ api/
β β βββ replit/
β β βββ webhook.ts # Webhook endpoint
β βββ jobs/
β βββ replit/
β βββ sync.ts # Background sync job
βββ tests/
β βββ unit/
β β βββ replit/
β βββ integration/
β βββ replit/
βββ config/
β βββ replit.development.json
β βββ replit.staging.json
β βββ replit.production.json
βββ docs/
βββ replit/
βββ SETUP.md
βββ RUNBOOK.md
```
## Layer Architecture
```
βββββββββββββββββββββββββββββββββββββββββββ
β API Layer β
β (Controllers, Routes, Webhooks) β
βββββββββββββββββββββββββββββββββββββββββββ€
β Service Layer β
β (Business Logic, Orchestration) β
βββββββββββββββββββββββββββββββββββββββββββ€
β Replit Layer β
β (Client, Types, Error Handling) β
βββββββββββββββββββββββββββββββββββββββββββ€
β Infrastructure Layer β
β (Cache, Queue, Monitoring) β
βββββββββββββββββββββββββββββββββββββββββββ
```
## Key Components
### Step 1: Client Wrapper
```typescript
// src/replit/client.ts
export class ReplitService {
private client: ReplitClient;
private cache: Cache;
private monitor: Monitor;
constructor(config: ReplitConfig) {
this.client = new ReplitClient(config);
this.cache = new Cache(config.cacheOptions);
this.monitor = new Monitor('replit');
}
async get(id: string): Promise {
return this.cache.getOrFetch(id, () =>
this.monitor.track('get', () => this.client.get(id))
);
}
}
```
### Step 2: Error Boundary
```typescript
// src/replit/errors.ts
export class ReplitServiceError extends Error {
constructor(
message: string,
public readonly code: string,
public readonly retryable: boolean,
public readonly originalError?: Error
) {
super(message);
this.name = 'ReplitServiceError';
}
}
export function wrapReplitError(error: unknown): ReplitServiceError {
// Transform SDK errors to application errors
}
```
### Step 3: Health Check
```typescript
// src/replit/health.ts
export async function checkReplitHealth(): Promise {
try {
const start = Date.now();
await replitClient.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) β
ββββββββ¬βββββββ βββββββββββββββ
β
βΌ
βββββββββββββββ
β Replit β
β Client β
ββββββββ¬βββββββ
β
βΌ
βββββββββββββββ
β Replit β
β API β
βββββββββββββββ
```
## Configuration Management
```typescript
// config/replit.ts
export interface ReplitConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
timeout: number;
retries: number;
cache: {
enabled: boolean;
ttlSeconds: number;
};
}
export function loadReplitConfig(): ReplitConfig {
const env = process.env.NODE_ENV || 'development';
return require(`./replit.${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 Replit operations.
### Step 4: Configure Health Checks
Add health check endpoint for Replit 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 Replit types |
| Test isolation | Shared state | Use dependency injection |
## Examples
### Quick Setup Script
```bash
# Create reference structure
mkdir -p src/replit/{handlers} src/services/replit src/api/replit
touch src/replit/{client,config,types,errors}.ts
touch src/services/replit/{index,sync,cache}.ts
```
## Resources
- [Replit SDK Documentation](https://docs.replit.com/sdk)
- [Replit Best Practices](https://docs.replit.com/best-practices)
## Flagship Skills
For multi-environment setup, see `replit-multi-env-setup`.