Configure Clay local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Clay. Trigger with phrases like "clay dev setup", "clay local development", "clay dev environment", "develop with clay".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-local-dev-loop81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Set up a fast, reproducible local development workflow for Clay.
clay-install-auth setupmy-clay-project/
├── src/
│ ├── clay/
│ │ ├── client.ts # Clay client wrapper
│ │ ├── config.ts # Configuration management
│ │ └── utils.ts # Helper functions
│ └── index.ts
├── tests/
│ └── clay.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 { ClayClient } from '../src/clay/client';
describe('Clay Client', () => {
it('should initialize with API key', () => {
const client = new ClayClient({ 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('@clay/sdk', () => ({
ClayClient: vi.fn().mockImplementation(() => ({
// Mock methods here
})),
}));# Enable verbose logging
DEBUG=CLAY=* npm run devSee clay-sdk-patterns for production-ready code patterns.
22fc789
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.