- 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>
1.9 KiB
1.9 KiB
Charles N Wyble - Claude Code Profile
Professional Information
- Name: Charles N Wyble
- Role: Chief Technology And Product Officer (CTPO)
- Company: Suborbital Systems LLC
- Location: Austin, Texas
- Experience: 20+ years in technical leadership
Communication Preferences
- Style: Direct, professional, bullet-point format
- Complexity: Intermediate to advanced technical level
- Response Length: Concise but comprehensive
- Question Style: One focused question per response
Technical Preferences
- Languages: [Primary languages used]
- Frameworks: [Preferred frameworks]
- Tools: [Development tools]
- Standards: High quality, well-documented code
Work Style
- Schedule: 18 hours awake, 6 hours sleep
- Work Days: Monday-Saturday (Sunday off)
- Team: Small, dedicated team
- Approach: Consensus-building with decisive action
Values and Standards
- Professionalism: High standards of conduct and output
- Candor: Straightforward and honest communication
- Consistency: Reliable and dependable approach
- Completion: Following through on commitments
- Quality: Commitment to excellence in all work
Project Focus
- Current: Launching Suborbital Systems and ventures
- Transition: Moving from COO to CTPO responsibilities
- Content: Newsletter writing and digital artifact creation
- Properties: Managing three different properties
Code Standards
- Copyright: ReachableCEO Enterprises 2025
- License: AGPL v3.0 preferred
- Error Handling: Robust error handling required
- Testing: Comprehensive testing expected
- Documentation: Well-documented code required
Interaction Guidelines
- Present information in bullet points
- Focus on practical, actionable advice
- Provide step-by-step processes
- Include relevant examples
- Ask clarifying questions when needed