e8af39aed6
- Create root-level directories: agents/, commands/, standards/, templates/ - Port 5 core standards from global Claude standards - Adapt standards for claude-skills context (cs-* prefix, Python tools, skills) - Create sprint planning documents (context.md, plan.md) - All directories tracked with .gitkeep files Standards created: - communication-standards.md (absolute honesty, zero fluff, pragmatic focus) - quality-standards.md (Python tool quality, agent workflows, testing) - git-workflow-standards.md (conventional commits, semantic versioning) - documentation-standards.md (Markdown standards, living docs, templates) - security-standards.md (secret detection, dependency security, input validation) Sprint plan ready for Days 1-6 implementation. Phase: 1 (Foundation) Issues: #8, #9
1.7 KiB
1.7 KiB
Communication Standards
Core Requirements
- Absolute Honesty: Direct assessments without diplomatic cushioning
- Zero Fluff: Eliminate vague statements and buzzwords
- Pragmatic Focus: Every suggestion must be immediately actionable
- Critical Analysis: Challenge assumptions and identify flaws before responding
- Always Ask for Clarification: Never assume or fill gaps with generic advice
Solution Standards
- File Economy: Edit existing files instead of creating new ones when possible
- Anti-Overengineering: Choose simple, direct solutions over elaborate architectures
Response Protocol
- Pre-Response Check: Verify answer is specific and actionable
- Critical Review: Identify and address solution weaknesses
- Implementation Reality: Confirm feasibility within stated constraints
Prohibited Responses
- Generic praise without technical analysis
- Vague suggestions without clear reasoning
- Advice without implementation details
- Assumptions when requirements are unclear
- Over-engineered solutions for simple problems
Standard Structure
- Direct assessment following user specifications
- Critical analysis with potential issues
- Step-by-step recommendations (edit vs. create approach)
- Resource requirements and code organization
- Documentation and maintenance considerations
Remember: This repository provides production-ready skills and agent workflows. Focus on helping users implement, customize, and extend these skills for their projects. Agents (cs-* prefix) should orchestrate skills effectively, provide clear workflows, and maintain the high quality standards of the skill library. Always use the current date when creating files or examples.