Contributing to Developer Kit for Claude Code banner
giuseppe-trisciuoglio giuseppe-trisciuoglio

Contributing to Developer Kit for Claude Code

Development community intermediate

Description

Thank you for your interest in contributing! This document provides guidelines and instructions for contributing to the Developer Kit for Claude Code.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for giuseppe-trisciuoglio/developer-kit, shared by 3 entries in this directory. It describes the repository, not this entry specifically.

Contributing to Developer Kit for Claude Code

Thank you for your interest in contributing! This document provides guidelines and instructions for contributing to the Developer Kit for Claude Code.

🎯 What You Can Contribute

The Developer Kit welcomes contributions in the following areas:

1. **New Skills** 📚

Add reusable capabilities for Claude Code covering:

  • Java/Spring Boot patterns (expanded scope beyond existing)
  • New languages: PHP, TypeScript, Python, Go, Rust, etc.
  • New frameworks: Django, FastAPI, Laravel, Express, etc.
  • Specialized domains: Cloud providers (AWS, GCP, Azure), data processing, DevOps, etc.

2. **Skill Improvements** ✨

Enhance existing skills with:

  • Additional examples and use cases
  • Better explanations or clearer documentation
  • New best practices and patterns
  • Performance or security improvements
  • Supporting scripts or utilities

3. **Agents** 🤖

Create specialized AI assistants for:

  • Domain-specific code reviews
  • Language or framework specialists
  • Testing and debugging automation
  • Security and performance analysis

4. **Slash Commands** ⚡

Add quick-access commands for:

  • Common development tasks
  • Workflow automation
  • Project-specific shortcuts

5. **Documentation** 📖

Improve project documentation:

  • README updates with new capabilities
  • Architecture documentation
  • Troubleshooting guides
  • Integration guides

6. **Bug Fixes & Issues** 🐛

  • Report issues with existing skills
  • Fix documentation errors
  • Improve examples or code samples
  • Suggest enhancements

📋 Before You Start

  1. Check existing content: Search existing components in plugins/ to avoid duplicating skills, agents, or commands
  2. Open an issue: For significant changes, discuss your idea first by opening an issue
  3. Understand the structure: Review the project organization and existing patterns

🚀 Creating a New Skill

Directory Structure

skills/[category]/[skill-name]/
├── SKILL.md                 # Required: Skill metadata and instructions
├── reference.md             # Optional: Detailed API reference
├── examples.md              # Optional: Practical examples
├── scripts/                 # Optional: Helper scripts (Python, Bash, etc.)
│   ├── validator.py
│   └── processor.sh
└── templates/               # Optional: Templates and boilerplate
    └── sample.txt

SKILL.md Format

---
name: skill-descriptive-name
description: Brief description of what this skill does and when to use it. Include trigger keywords (max 1024 chars). Should mention BOTH capabilities AND use cases.
allowed-tools: Read, Write, Bash  # Optional: restrict tool access
---

# Skill Name

## When to Use
- Clear trigger phrases and context where this skill applies
- Specific use cases and scenarios
- What problems it solves

## Instructions
- Step-by-step guidance for using this skill
- Key concepts and terminology
- Common patterns and approaches

## Examples