claude-skills-generator: Instructions file for Claude Code

{{PROJECT_NAME}} - Claude Code Instructions

Project Overview

{{PROJECT_DESCRIPTION}}

This file contains mandatory instructions for Claude Code when working on this project.

Code Quality Requirements

Security First

• Never introduce OWASP Top 10 vulnerabilities
• All file operations must respect sandboxing rules
• Credentials must use OS keychain, never plaintext
• All user inputs must be validated

Architecture

{{ARCHITECTURE_DESCRIPTION}}

Key Documentation

• README: README.md - Project overview
• Contributing: CONTRIBUTING.md - How to contribute
• Architecture: CLAUDE_CODE_ARCHITECTURE.md - Claude Code integration guide

Slash Commands

Use these commands for common implementation tasks (customize as needed):

• /implement-feature - Load feature implementation skills
• /run-tests - Execute test suite

Commit Guidelines

• Use conventional commit format
• Ensure all tests pass before committing
• Never commit sensitive credentials

Dependency Management Rules

CRITICAL: Never Guess Package Versions

STOP! Before updating ANY dependency, you MUST:

1. Check actual latest version:

   npm view <package> version
   # or for Python
   pip index versions <package>
   

2. Read migration guide for major version updates

3. Update one package at a time - never bulk update

4. Run verification after each update:

   {{INSTALL_COMMAND}} && {{DEV_COMMAND}} && {{BUILD_COMMAND}} && {{TEST_COMMAND}}
   

Version Specification Rules

// Use conservative ranges for production dependencies
"package": "~1.0.0"          // Patch only

// Caret (^) only for dev tools
"eslint": "^9.0.0"           // Minor + patch OK

Testing Requirements

When User Asks to "Run Tests"

When the user asks to run tests, execute ALL of these automatically:

{{TEST_COMMANDS}}

Report results for each step. If any step fails, attempt to fix the issue before proceeding.