juicebox-local-dev-loop
Configure Juicebox local development workflow.Use when setting up local testing, mock data, or development environmentfor Juicebox integration work.Trigger with phrases like "juicebox local dev", "juicebox development setup","juicebox mock data", "test juicebox locally".
When & Why to Use This Skill
The Juicebox Local Dev Loop skill automates the configuration of a high-efficiency local development environment for Juicebox SDK integrations. It streamlines the setup of environment variables, mock data generation for offline testing, and robust test utilities, enabling developers to achieve rapid iteration through hot-reloading and sandbox-mode testing without relying on live API calls.
Use Cases
- Initial Environment Setup: Quickly generate .env.development files and sandbox configurations to start Juicebox integration projects.
- Offline UI/UX Development: Use pre-defined mock profiles and search responses to build and test frontend components without an active internet connection.
- Automated Integration Testing: Implement reliable test suites using the provided TypeScript utilities and Vitest configurations to validate SDK interactions.
- Workflow Optimization: Configure hot-reload scripts (nodemon/vitest) to ensure immediate feedback during the development and debugging process.
| name | juicebox-local-dev-loop |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(pip:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Juicebox Local Dev Loop
Overview
Configure a fast local development workflow for Juicebox integration with mock data and testing utilities.
Prerequisites
- Juicebox SDK installed
- Node.js or Python environment
- Test API key (sandbox mode)
Instructions
Step 1: Configure Development Environment
# Create development config
cat > .env.development << 'EOF'
JUICEBOX_API_KEY=jb_test_xxxxxxxxxxxx
JUICEBOX_ENVIRONMENT=sandbox
JUICEBOX_LOG_LEVEL=debug
EOF
Step 2: Set Up Mock Data
// mocks/juicebox.ts
export const mockProfiles = [
{
id: 'mock-1',
name: 'Test User',
title: 'Software Engineer',
company: 'Test Corp',
location: 'San Francisco, CA'
}
];
export const mockSearchResponse = {
total: 1,
profiles: mockProfiles,
hasMore: false
};
Step 3: Create Test Utilities
// test-utils/juicebox.ts
import { JuiceboxClient } from '@juicebox/sdk';
export function createTestClient() {
return new JuiceboxClient({
apiKey: process.env.JUICEBOX_API_KEY,
sandbox: true,
timeout: 5000
});
}
export async function withMockSearch<T>(
fn: (client: JuiceboxClient) => Promise<T>
): Promise<T> {
const client = createTestClient();
return fn(client);
}
Step 4: Hot Reload Setup
// package.json
{
"scripts": {
"dev": "nodemon --watch src --exec ts-node src/index.ts",
"test:watch": "vitest watch"
}
}
Output
- Development environment configuration
- Mock data for offline testing
- Test utilities for integration tests
- Hot reload for rapid iteration
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Sandbox Limit | Exceeded test quota | Wait or upgrade plan |
| Mock Mismatch | Schema changed | Update mock data |
| Hot Reload Fail | File lock | Restart dev server |
Examples
Integration Test
import { describe, it, expect } from 'vitest';
import { createTestClient } from './test-utils/juicebox';
describe('Juicebox Search', () => {
it('returns profiles for valid query', async () => {
const client = createTestClient();
const results = await client.search.people({
query: 'engineer',
limit: 5
});
expect(results.profiles.length).toBeGreaterThan(0);
});
});
Resources
Next Steps
With local dev configured, explore juicebox-sdk-patterns for production patterns.