awesome-claude-md

Alive24/CKBoost

View CLAUDE.md
libraries frameworks Updated 2026-02-10

Analysis

Category: Libraries & Frameworks Source: Alive24/CKBoost CLAUDE.md: View Original License: MIT License Why it's exemplary: Demonstrates sophisticated Task Master AI integration with comprehensive PRD-First development methodology and blockchain-specific patterns for CKB ecosystem.

Key Features That Make This Exemplary

1. Task Master AI Integration

  • Auto-Loading Context: "This CLAUDE.md file is automatically loaded for context"
  • Task ID Hierarchy: Structured task management with unique identifiers
  • Multi-Claude Workflows: Coordination patterns for multiple AI assistant sessions
  • Custom Slash Commands: /init, /plan, /next for workflow automation

2. PRD-First Development Mandate

  • Quality Gates: Mandatory checkpoints before implementation begins
  • Anti-Patterns: Explicit documentation of what NOT to do
  • Product Governance: Framework for managing feature specifications
  • Template-Driven: Consistent PRD structure across all features

3. Blockchain-Specific Patterns

  • SSRI Method: Off-chain transaction building vs. on-chain validation separation
  • ConnectedTypeID Pattern: O(1) cell lookups for performance optimization
  • Recipe-Based Validation: Declarative transaction validation system
  • Molecule Schema: CKB-specific data serialization patterns

4. AI Orchestration Framework

  • MCP Server Configuration: Model Context Protocol integration
  • Session Management: Multi-session coordination patterns
  • Context Preservation: Maintaining state across AI assistant interactions
  • Workflow Automation: Automated task transitions and status updates

Specific Techniques to Learn

Task Master Integration

**Task Workflow Commands:**
- `/init` - Initialize new task context
- `/plan` - Generate implementation plan
- `/next` - Advance to next task in sequence
- `/status` - Report current task state

Custom commands for AI assistant workflow automation.

PRD-First Methodology

**Before Implementation:**
1. Create PRD document in /docs/prd/
2. Define acceptance criteria
3. Identify dependencies
4. Get stakeholder approval
5. Only then begin coding

Enforces planning discipline with clear checkpoints.

Blockchain Transaction Patterns

**SSRI Pattern:**
- Build transaction off-chain (client-side)
- Validate transaction on-chain (smart contract)
- Separate concerns for testability
- Enable dry-run validation before broadcast

Domain-specific architecture for blockchain applications.

Quality Gate Anti-Patterns

**Avoid:**
- Skipping PRD for "small" features
- Implementing without acceptance criteria
- Mixing implementation and specification changes
- Bypassing review checkpoints

Explicit documentation of common mistakes to avoid.

Key Takeaways

  1. AI Workflow Automation: Define custom commands for common AI assistant operations
  2. Planning Discipline: Enforce PRD-first methodology with explicit quality gates
  3. Domain Patterns: Document blockchain-specific patterns (SSRI, ConnectedTypeID)
  4. Anti-Pattern Documentation: Explicitly state what NOT to do, not just what to do
  5. Multi-Agent Coordination: Patterns for orchestrating multiple AI assistant sessions

Attribution

This analysis references the original CLAUDE.md from Alive24/CKBoost. All credit for the original documentation belongs to the repository maintainers.