Configure Instantly local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Instantly. Trigger with phrases like "instantly dev setup", "instantly local development", "instantly dev environment", "develop with instantly".
Configures local development environments with hot reload and testing for Instantly projects.
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install instantly-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Set up a fast, reproducible local development workflow for Instantly.
instantly-install-auth setupmy-instantly-project/
├── src/
│ ├── instantly/
│ │ ├── client.ts # Instantly client wrapper
│ │ ├── config.ts # Configuration management
│ │ └── utils.ts # Helper functions
│ └── index.ts
├── tests/
│ └── instantly.test.ts
├── .env.local # Local secrets (git-ignored)
├── .env.example # Template for team
└── package.json
# Copy environment template
cp .env.example .env.local
# Install dependencies
npm install
# Start development server
npm run dev
{
"scripts": {
"dev": "tsx watch src/index.ts",
"test": "vitest",
"test:watch": "vitest --watch"
}
}
import { describe, it, expect, vi } from 'vitest';
import { InstantlyClient } from '../src/instantly/client';
describe('Instantly Client', () => {
it('should initialize with API key', () => {
const client = new InstantlyClient({ apiKey: 'test-key' });
expect(client).toBeDefined();
});
});
| Error | Cause | Solution |
|---|---|---|
| Module not found | Missing dependency | Run npm install |
| Port in use | Another process | Kill process or change port |
| Env not loaded | Missing .env.local | Copy from .env.example |
| Test timeout | Slow network | Increase test timeout |
vi.mock('@instantly/sdk', () => ({
InstantlyClient: vi.fn().mockImplementation(() => ({
// Mock methods here
})),
}));
# Enable verbose logging
DEBUG=INSTANTLY=* npm run dev
See instantly-sdk-patterns for production-ready code patterns.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.