A comprehensive collection of templates, use cases, and workflows for AI-assisted development using context engineering principles.
This repository provides:
- Production-ready templates - Tested and proven document structures
- Custom commands - Reusable automation for Claude Code
- Reverse thinking methodology - Identify risks before they become problems
- SERENA MCP integration - Memory persistence for continuous improvement
/generate-release project:MyProject version:1.0.0 source_dir:/path/to/code scope:full-app
/validate-release package_path:/path/to/Release_v1.0.0 severity:standard
/reverse-check focus:all package_path:/path/to/Release_v1.0.0
usecase-with-flows/
├── .claude/
│ └── commands/ # Custom slash commands
│ ├── generate-release.md # Generate documentation package
│ ├── validate-release.md # Quality assurance
│ ├── reverse-check.md # Risk analysis
│ ├── update-docs.md # Incremental updates
│ └── create-template.md # Create new templates
├── templates/
│ └── release-package/ # Release documentation template
│ ├── README.md # Template overview
│ ├── implementation-guide.md # Detailed usage
│ ├── serena-memory-guide.md # Memory management
│ └── doc-templates/ # Actual templates
│ ├── README.template.md
│ ├── USECASE.template.md
│ ├── DEPLOY.template.md
│ └── TROUBLESHOOTING.template.md
├── CLAUDE.md # Global ruleset & conventions
└── README.md # This file
Generate professional release documentation with:
- README, USECASE, DEPLOY, TROUBLESHOOTING guides
- Architecture and API documentation
- Configuration and changelog
- Reverse thinking validation
Location: templates/release-package/
Quick Start:
/generate-release project:MyApp version:1.0.0 source_dir:/dev/myapp scope:full-app
| Command | Description | Time |
|---|---|---|
/generate-release |
Create complete documentation package | 30-60 min |
/validate-release |
Quality assurance and validation | 10-15 min |
/reverse-check |
Risk and gap analysis | 15-20 min |
/update-docs |
Incremental documentation updates | 5-10 min |
/create-template |
Generate new template skeletons | 10-15 min |
Instead of only asking "How does this work?", we also ask:
- What could go wrong?
- What are we assuming?
- What happens when X fails?
- What questions haven't we answered?
- Memory persistence - Templates and findings saved across sessions
- Pattern recognition - Learn from previous releases
- Continuous improvement - Each release improves the next
Consistent indicators across all documents:
⚠️ Warnings and critical items- ✅ Required steps / success
- ℹ️ Notes and context
- ❌ Common mistakes
START
│
▼
[Load Context] → Previous templates, issues, patterns
│
▼
[Phase 1: Analysis] → Map structure, identify gaps
│
▼
[Phase 2: Generate] → Populate templates
│
▼
[Phase 3: Develop] → Write content, add examples
│
▼
[Phase 4: Validate] → Reverse thinking, risk check
│
▼
[Phase 5: Assemble] → Package and deliver
│
▼
SUCCESS
/generate-release project:UserAuth version:2.0.0 source_dir:/home/dev/auth scope:microservice
Output:
Release_v2.0.0/
├── README.md
├── USECASE.md
├── DEPLOY.md
├── TROUBLESHOOTING.md
├── ARCHITECTURE.md
├── API_REFERENCE.md
├── CONFIGURATION.md
├── CHANGELOG.md
├── INDEX.md
└── _MANIFEST.json
/validate-release package_path:/releases/v2.0.0 severity:extended
/reverse-check focus:security package_path:/releases/v2.0.0
- CLAUDE.md - Global conventions and standards
- templates/release-package/ - Release package template
- Create directory under
templates/ - Add README.md with overview
- Create
doc-templates/subdirectory - Add implementation guide
- Test with
/validate-release
- Use
/reverse-checkto identify gaps - Update templates
- Test changes
- Document in commit message
All templates must achieve:
- Completeness score >= 95%
- Zero critical issues
- All code examples syntactically correct
- All internal links working
MIT License - See LICENSE file
- Check CLAUDE.md for conventions
- See template-specific guides in
templates/ - Use
/reverse-checkto identify gaps
Built with context engineering principles for AI-assisted development