tessl install github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-architecture-variantsChoose and implement Clay validated architecture blueprints for different scales. Use when designing new Clay integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Clay applications. Trigger with phrases like "clay architecture", "clay blueprint", "how to structure clay", "clay project layout", "clay microservice".
Review Score
82%
Validation Score
13/16
Implementation Score
73%
Activation Score
90%
Three validated architecture blueprints for Clay integrations.
Best for: MVPs, small teams, < 10K daily active users
my-app/
├── src/
│ ├── clay/
│ │ ├── client.ts # Singleton client
│ │ ├── types.ts # Types
│ │ └── middleware.ts # Express middleware
│ ├── routes/
│ │ └── api/
│ │ └── clay.ts # API routes
│ └── index.ts
├── tests/
│ └── clay.test.ts
└── package.json// Direct integration in route handler
app.post('/api/create', async (req, res) => {
try {
const result = await clayClient.create(req.body);
res.json(result);
} catch (error) {
res.status(500).json({ error: error.message });
}
});Best for: Growing startups, 10K-100K DAU, multiple integrations
my-app/
├── src/
│ ├── services/
│ │ ├── clay/
│ │ │ ├── client.ts # Client wrapper
│ │ │ ├── service.ts # Business logic
│ │ │ ├── repository.ts # Data access
│ │ │ └── types.ts
│ │ └── index.ts # Service exports
│ ├── controllers/
│ │ └── clay.ts
│ ├── routes/
│ ├── middleware/
│ ├── queue/
│ │ └── clay-processor.ts # Async processing
│ └── index.ts
├── config/
│ └── clay/
└── package.json// Service layer abstraction
class ClayService {
constructor(
private client: ClayClient,
private cache: CacheService,
private queue: QueueService
) {}
async createResource(data: CreateInput): Promise<Resource> {
// Business logic before API call
const validated = this.validate(data);
// Check cache
const cached = await this.cache.get(cacheKey);
if (cached) return cached;
// API call with retry
const result = await this.withRetry(() =>
this.client.create(validated)
);
// Cache result
await this.cache.set(cacheKey, result, 300);
// Async follow-up
await this.queue.enqueue('clay.post-create', result);
return result;
}
}Best for: Enterprise, 100K+ DAU, strict SLAs
clay-service/ # Dedicated microservice
├── src/
│ ├── api/
│ │ ├── grpc/
│ │ │ └── clay.proto
│ │ └── rest/
│ │ └── routes.ts
│ ├── domain/
│ │ ├── entities/
│ │ ├── events/
│ │ └── services/
│ ├── infrastructure/
│ │ ├── clay/
│ │ │ ├── client.ts
│ │ │ ├── mapper.ts
│ │ │ └── circuit-breaker.ts
│ │ ├── cache/
│ │ ├── queue/
│ │ └── database/
│ └── index.ts
├── config/
├── k8s/
│ ├── deployment.yaml
│ ├── service.yaml
│ └── hpa.yaml
└── package.json
other-services/
├── order-service/ # Calls clay-service
├── payment-service/
└── notification-service/// Event-driven with domain isolation
class ClayAggregate {
private events: DomainEvent[] = [];
process(command: ClayCommand): void {
// Domain logic
const result = this.execute(command);
// Emit domain event
this.events.push(new ClayProcessedEvent(result));
}
getUncommittedEvents(): DomainEvent[] {
return [...this.events];
}
}
// Event handler
@EventHandler(ClayProcessedEvent)
class ClayEventHandler {
async handle(event: ClayProcessedEvent): Promise<void> {
// Saga orchestration
await this.sagaOrchestrator.continue(event);
}
}| Factor | Monolith | Service Layer | Microservice |
|---|---|---|---|
| Team Size | 1-5 | 5-20 | 20+ |
| DAU | < 10K | 10K-100K | 100K+ |
| Deployment Frequency | Weekly | Daily | Continuous |
| Failure Isolation | None | Partial | Full |
| Operational Complexity | Low | Medium | High |
| Time to Market | Fastest | Moderate | Slowest |
Monolith → Service Layer:
1. Extract Clay code to service/
2. Add caching layer
3. Add background processing
Service Layer → Microservice:
1. Create dedicated clay-service repo
2. Define gRPC contract
3. Add event bus
4. Deploy to Kubernetes
5. Migrate traffic graduallyUse the decision matrix to identify appropriate variant.
Select Monolith, Service Layer, or Microservice based on needs.
Set up project layout following the chosen blueprint.
Document upgrade path for future scaling.
| Issue | Cause | Solution |
|---|---|---|
| Over-engineering | Wrong variant choice | Start simpler |
| Performance issues | Wrong layer | Add caching/async |
| Team friction | Complex architecture | Simplify or train |
| Deployment complexity | Microservice overhead | Consider service layer |
# Count team size and DAU to select variant
echo "Team: $(git log --format='%ae' | sort -u | wc -l) developers"
echo "DAU: Check analytics dashboard"For common anti-patterns, see clay-known-pitfalls.