StratIQX Documentation

Appearance

Using StratIQX Docs with Claude Code CLI ​

🎯 Purpose ​

This documentation serves as a living knowledge base for building the StratIQX platform. Quick reference during Claude Code CLI sessions for:

  • Architecture decisions
  • Code patterns
  • Configuration examples
  • Troubleshooting guides
  • Style guidelines

🔍 Quick Search Tips ​

Search Shortcuts ​

Press / or Ctrl+K (Mac: Cmd+K) to instantly search all docs.

Common Search Terms ​

Architecture:

  • "hybrid architecture" - System design overview
  • "AI orchestrator" - AI integration patterns
  • "microservices" - Service architecture

Configuration:

  • "environment" - Environment setup
  • "configuration" - Config reference
  • "deployment" - Deployment guides

Development:

  • "Claude Code" - Workflow tips
  • "error-driven" - Design patterns
  • "session handoff" - Automation guides

Style & Branding:

  • "brand style" - StratIQX branding guidelines
  • "Big 3" - Consulting style guidelines
  • "Chicago style" - Report formatting

Troubleshooting:

  • "email troubleshooting" - Email issues
  • "stripe webhook" - Payment integration issues
  • "database cleanup" - Data management

📋 Quick Reference by Use Case ​

Starting a New Feature ​

  1. Architecture Overview
  2. Service Abstraction Guide
  3. B2B SaaS Design Patterns

Working with AI Integration ​

  1. AI Orchestrator Architecture
  2. AI Orchestration Configuration
  3. Semantic Anchoring Breakthrough

Styling & Branding ​

  1. StratIQX Brand Style Guide
  2. Form Styling Guidelines
  3. Email Template Guidelines

Debugging Issues ​

  1. Configuration Diagnostics Runbook
  2. Email Troubleshooting Guide
  3. Error-Driven Solution Design

Integration Work ​

  1. Payment Auth Integration
  2. Single Unified Auth Flow
  3. Cloudflare Worker Communications

💡 Tips for Claude Code CLI Usage ​

Share Context Efficiently ​

Option 1: Reference by URL

bash
# In Claude Code CLI, reference specific docs:
"Check the architecture guide at docs.stratiqx.ai/v1/hybrid-architecture"

Option 2: Search First, Then Reference

bash
# Search docs for pattern, then paste relevant section
"Following the pattern from our email template guidelines..."

Option 3: Multi-Doc Context

bash
# Reference multiple related docs:
"Using patterns from our:
- AI orchestrator architecture
- Service abstraction guide
- Error-driven design framework"

Common Claude Code CLI Workflows ​

1. Starting New Feature

1. Search docs for similar feature
2. Review architecture patterns
3. Reference style guidelines
4. Check integration requirements
5. Start coding with context

2. Debugging Issues

1. Search troubleshooting guides
2. Check configuration diagnostics
3. Review error patterns
4. Apply solutions from docs

3. Code Review

1. Reference brand style guide
2. Check design patterns
3. Verify against guidelines
4. Ensure consistency

Most Referenced Docs ​

Daily Use:

Architecture Decisions:

Code Quality:

Integration:

📝 Keeping Docs Updated ​

During Development ​

When you discover new patterns or solutions:

  1. Document it immediately
  2. Add to relevant section
  3. Update search keywords
  4. Cross-reference related docs

After Major Features ​

  1. Create architecture doc
  2. Document decision rationale
  3. Add troubleshooting guide
  4. Update integration guides

Session Handoff ​

Use Session Handoff Automation Guide to:

  • Save context between sessions
  • Document progress
  • Track decisions
  • Plan next steps

🎯 Best Practices ​

For Claude Code CLI Sessions ​

Start of Session:

"I'm working on [feature]. 
Reference: docs.stratiqx.ai/v1/[relevant-doc]
Continue from last session..."

During Development:

"Following the pattern from our [doc-name] guide:
[paste relevant section]"

End of Session:

"Document this solution in [section] 
for future reference"

Documentation Maintenance ​

Weekly:

  • Review recent work
  • Update relevant docs
  • Add new patterns discovered
  • Fix any outdated info

After Major Updates:

  • Update architecture docs
  • Document new patterns
  • Add troubleshooting sections
  • Update integration guides

🔧 Advanced Tips ​

Multi-Doc References ​

Combine multiple docs for complex features:

Context from:
1. Architecture: [doc A]
2. Integration: [doc B]
3. Style: [doc C]
Implementing: [feature]

Pattern Library ​

Build your own shortcuts:

  • Bookmark frequently used docs
  • Create quick-reference sections
  • Maintain personal notes alongside docs

Cross-Platform Usage ​

  • Desktop: Full docs with search
  • Mobile: Quick reference via bookmarks
  • CLI: URL references in prompts

📊 Documentation Stats ​

Current Status:

  • V1 Docs: 70+ comprehensive guides
  • Categories: 16 organized sections
  • Search: Full-text with fuzzy matching
  • Version: VitePress 1.6.3

Coverage:

  • ✅ Architecture & Design
  • ✅ Configuration & Setup
  • ✅ AI & Intelligence
  • ✅ Development Tools
  • ✅ Integration & APIs
  • ✅ Style Guidelines
  • ✅ Troubleshooting

🎉 Making It Work For You ​

Personalize Your Workflow ​

  1. Identify your most-used docs
  2. Create shortcuts or bookmarks
  3. Add personal notes to docs
  4. Maintain a "favorites" list

Share Knowledge ​

  • Document solutions as you find them
  • Add examples from real implementations
  • Create decision logs
  • Build a pattern library

Continuous Improvement ​

  • Update docs after solving issues
  • Add missing information
  • Improve search keywords
  • Cross-link related content

💬 Remember ​

This is YOUR knowledge base!

  • Keep it organized
  • Keep it updated
  • Keep it searchable
  • Keep it useful

Every doc you write:

  • Saves time later
  • Maintains consistency
  • Transfers knowledge
  • Speeds development

Happy Building with StratIQX Docs + Claude Code CLI! 🚀

Quick Access: Press / to search anything, anytime!

Strategic Intelligence Hub Documentation

Copyright © 2024-present StratIQX