Write the test first. Watch it fail. Write minimal code to pass.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionlaravel-tddExecute the skills CLI command in your project's root directory to begin installation:
Fetches laravel-tdd from iserter/laravel-claude-agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate laravel-tdd. Access via /laravel-tdd in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
31
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
31
stars
Write the test first. Watch it fail. Write minimal code to pass.
This skill adapts TDD principles specifically for Laravel applications using Pest PHP, Laravel's testing features, and framework-specific patterns.
Always for Laravel:
Exceptions (ask your human partner):
RED → Verify RED → GREEN → Verify GREEN → REFACTOR → Repeat
Write one minimal test showing what the Laravel feature should do.
Feature Test Example:
<?php
use App\Models\User;
use App\Models\Post;
test('authenticated user can create post', function () {
$user = User::factory()->create();
$this->actingAs($user)
->post('/posts', [
'title' => 'My First Post',
'content' => 'Post content here',
])
->assertRedirect('/posts');
expect(Post::where('title', 'My First Post')->exists())->toBeTrue();
expect(Post::first()->user_id)->toBe($user->id);
});
php artisan test --filter=authenticated_user_can_create_post
Write simplest Laravel code to pass the test.
php artisan test
After green only:
use Illuminate\Foundation\Testing\RefreshDatabase;
uses(RefreshDatabase::class);
test('creates post in database', function () {
$user = User::factory()->create();
$this->actingAs($user)
->post('/posts', ['title' => 'Test', 'content' => 'Content']);
$this->assertDatabaseHas('posts', ['title' => 'Test']);
});
test('user cannot delete others posts', function () {
$user = User::factory()->create();
$post = Post::factory()->create();
$this->actingAs($user)
->delete("/posts/{$post->id}")
->assertForbidden();
});
test('creates post via API', function () {
$user = User::factory()->create();
$this->actingAs($user, 'sanctum')
->postJson('/api/posts', ['title' => 'API Post', 'content' => 'Content'])
->assertCreated();
});
Every Laravel feature → Test exists and failed first
Otherwise → Not TDD
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: laravel-tdd is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added laravel-tdd from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
laravel-tdd reduced setup friction for our internal harness; good balance of opinion and flexibility.
laravel-tdd has been reliable in day-to-day use. Documentation quality is above average for community skills.
laravel-tdd is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for laravel-tdd matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for laravel-tdd matched our evaluation — installs cleanly and behaves as described in the markdown.
laravel-tdd fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
laravel-tdd has been reliable in day-to-day use. Documentation quality is above average for community skills.
laravel-tdd reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 58