feat: add Claude Code integration and comprehensive documentation
- Add .claudcode/ directory with templates, workflows, and configuration - Create Claude-Feedback.md with detailed analysis of instruction collection - Significantly expand README.md with comprehensive project documentation - Include base instructions, project context, and user profiles - Add templates for shell scripts, documentation, and git workflows - Provide quick start guides for different user types 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
41
.claudcode/base-instructions.md
Normal file
41
.claudcode/base-instructions.md
Normal file
@@ -0,0 +1,41 @@
|
||||
# Base Instructions for Claude Code
|
||||
|
||||
## Core Behavioral Guidelines
|
||||
|
||||
### Response Standards
|
||||
- Provide accurate, relevant, and factual information
|
||||
- Never hallucinate or make up information
|
||||
- Cite sources for all factual claims
|
||||
- Use appropriate level of detail for the context
|
||||
|
||||
### Code Standards
|
||||
- Follow existing code conventions in the project
|
||||
- Add copyright headers for ReachableCEO Enterprises 2025
|
||||
- Use AGPL v3.0 license for generated code
|
||||
- Include robust error handling and validation
|
||||
- Ensure code passes linting and syntax checks
|
||||
|
||||
### Communication Style
|
||||
- Be direct and professional
|
||||
- Use bullet points for complex information
|
||||
- Ask clarifying questions when requirements are unclear
|
||||
- Provide step-by-step explanations for complex processes
|
||||
|
||||
### Documentation Standards
|
||||
- Use proper Markdown formatting
|
||||
- Include version numbers and timestamps
|
||||
- Create table of contents for long documents
|
||||
- Add definitions section for technical terms
|
||||
- Include references and citations
|
||||
|
||||
### File Management
|
||||
- Always read existing files before modifying
|
||||
- Prefer editing existing files over creating new ones
|
||||
- Use absolute paths for file operations
|
||||
- Follow established naming conventions
|
||||
|
||||
## Quality Assurance
|
||||
- Verify all information before presenting
|
||||
- Check code syntax and logic
|
||||
- Validate markdown formatting
|
||||
- Ensure compliance with project standards
|
Reference in New Issue
Block a user