juicebox-reference-architecture
Implement Juicebox reference architecture. Trigger: "juicebox architecture", "recruiting platform design".
What this skill does
# Juicebox Reference Architecture
## Overview
Production architecture for AI-powered candidate analysis integrations with Juicebox. Designed for recruiting teams needing automated dataset ingestion from job descriptions, intelligent candidate scoring and ranking, result caching for repeated searches, and seamless export to ATS platforms like Greenhouse and Lever. Key design drivers: search result freshness, candidate deduplication across sources, outreach sequencing, and analysis pipeline throughput for high-volume hiring.
## Architecture Diagram
```
Recruiter Dashboard ──→ Search Service ──→ Cache (Redis) ──→ Juicebox API
↓ /search
Queue (Bull) ──→ Analysis Worker /profiles
↓ /outreach
ATS Export Service ──→ Greenhouse/Lever
↓
Webhook Handler ←── Juicebox Events
```
## Service Layer
```typescript
class CandidateSearchService {
constructor(private juicebox: JuiceboxClient, private cache: CacheLayer) {}
async findAndRank(criteria: SearchCriteria): Promise<RankedCandidate[]> {
const cacheKey = `search:${this.hashCriteria(criteria)}`;
const cached = await this.cache.get(cacheKey);
if (cached) return cached;
const results = await this.juicebox.search(criteria);
const ranked = results.profiles.map(p => ({ ...p, score: this.scoreCandidate(p, criteria) }))
.sort((a, b) => b.score - a.score);
await this.cache.set(cacheKey, ranked, CACHE_CONFIG.searchResults.ttl);
return ranked;
}
async exportToATS(candidates: string[], jobId: string, ats: 'greenhouse' | 'lever'): Promise<ExportResult> {
const deduped = await this.deduplicateAgainstATS(candidates, jobId, ats);
return this.juicebox.export({ profiles: deduped, destination: ats, job_id: jobId });
}
}
```
## Caching Strategy
```typescript
const CACHE_CONFIG = {
searchResults: { ttl: 1800, prefix: 'search' }, // 30 min — candidate pools shift slowly
profiles: { ttl: 3600, prefix: 'profile' }, // 1 hr — profile data stable short-term
analysisRuns: { ttl: 7200, prefix: 'analysis' }, // 2 hr — analysis results are expensive to recompute
atsState: { ttl: 300, prefix: 'ats' }, // 5 min — ATS pipeline freshness for dedup
outreach: { ttl: 60, prefix: 'outreach' }, // 1 min — sequence status changes frequently
};
// New search invalidates matching cached results; ATS export clears ats cache for that job
```
## Event Pipeline
```typescript
class RecruitingPipeline {
private queue = new Bull('juicebox-events', { redis: process.env.REDIS_URL });
async onSearchComplete(searchId: string, results: RankedCandidate[]): Promise<void> {
await this.queue.add('analyze', { searchId, candidateIds: results.map(r => r.id) },
{ attempts: 3, backoff: { type: 'exponential', delay: 2000 } });
}
async processOutreachEvent(event: OutreachEvent): Promise<void> {
if (event.type === 'reply_received') await this.flagForRecruiterReview(event);
if (event.type === 'bounced') await this.markInvalid(event.candidateId);
await this.syncStatusToATS(event);
}
}
```
## Data Model
```typescript
interface SearchCriteria { role: string; skills: string[]; location?: string; experienceYears?: number; companySize?: string; }
interface RankedCandidate { id: string; name: string; title: string; company: string; score: number; skills: string[]; profileUrl: string; }
interface OutreachSequence { id: string; candidateId: string; jobId: string; steps: OutreachStep[]; status: 'active' | 'replied' | 'bounced' | 'opted-out'; }
interface ExportResult { exported: number; duplicatesSkipped: number; atsJobId: string; }
```
## Scaling Considerations
- Parallelize search requests across role categories — Juicebox API supports concurrent queries
- Cache analysis results aggressively — AI scoring is the most expensive operation per candidate
- Batch ATS exports by job requisition to minimize Greenhouse/Lever API round-trips
- Deduplicate candidates across searches before outreach to avoid double-contacting
- Rate-limit outreach sequencing to maintain sender reputation and deliverability
## Error Handling
| Component | Failure Mode | Recovery |
|-----------|-------------|----------|
| Candidate search | Juicebox API timeout | Retry with reduced result count, serve cached results if available |
| Analysis pipeline | Scoring model latency spike | Queue with timeout, return unscored results with flag |
| ATS export | Greenhouse rate limit | Batch retry with exponential backoff, notify recruiter on persistent failure |
| Outreach sequence | Email bounce | Mark candidate invalid, remove from active sequences, update ATS |
| Webhook handler | Duplicate event delivery | Idempotency key on event ID + candidate ID |
## Resources
- [Juicebox AI](https://juicebox.ai)
- [Juicebox Integrations](https://juicebox.ai/integrations)
## Next Steps
See `juicebox-deploy-integration`.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.