jean-claude-dev

Codifies Jean Claude project's development and testing guidance for contributors.

1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/JoshuaOliphant/jean-claude --skill jean-claude-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jean-claude-dev
Source: https://github.com/JoshuaOliphant/jean-claude/tree/main/.claude/skills/jean-claude-dev
Command: npx skills add https://github.com/JoshuaOliphant/jean-claude --skill jean-claude-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill documents internal development practices, patterns, and institutional knowledge to accelerate contributor onboarding and code quality for the Jean Claude project.

Core Features & Use Cases

  • Codified development guidance for code changes in src/jean_claude, tests, and architecture.
  • Structured testing patterns, retrospectives, and experimental workflow notes to reduce onboarding time.
  • A living reference that evolves with each retrospective, ensuring up-to-date best practices for contributors.

Quick Start

Describe a change to Jean Claude's source and follow the testing patterns outlined here.

Frequently Asked Questions about jean-claude-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document contributor knowledge for internal development practices?

To document contributor knowledge for internal development practices, you codify institutional patterns into a structured guide covering source changes, testing patterns, and architecture notes to accelerate developer onboarding.

What testing patterns should I follow when changing source code in src/jean_claude?

When changing source code in src/jean_claude, follow the structured testing patterns outlined in the development guide. These patterns are codified from retrospectives to ensure code quality and reduce onboarding time for contributors.

How do I use retrospectives to update development documentation?

Retrospectives update development documentation by feeding insights back into a living reference guide. Each retrospective ensures best practices evolve, keeping architectural guidance and experimental workflow notes current for all project contributors.

Does this contributor guide apply to architecture changes and code reviews?

Yes, this contributor guide applies to architecture changes and code reviews. It provides codified development guidance for modifications in src/jean_claude, structured testing workflows, and retrospective activities to maintain project consistency.

What's the best way to speed up developer onboarding for a complex internal project?

The best way to speed up developer onboarding is codifying institutional knowledge into a living reference. Documenting source changes, testing patterns, and architecture decisions reduces ramp-up time and ensures consistent code quality.

Can I load development guidance directly into my context using scripts and references?

Yes, you can load development guidance directly into context using optional resources like scripts and references. These components provide structured access to testing patterns, architecture notes, and contributor workflows during development.