Claude Instructions Implementation Guide

Status: Complete
Generated: 2025-08-13 16:00 UTC

This guide documents the implementation of comprehensive Claude Code instructions for Sasha Studio, establishing a guide-first approach to institutional knowledge building.

Overview

The Claude instructions system provides comprehensive guidance to Claude Code when working within Sasha Studio, emphasizing proactive guide creation and institutional memory building. This transforms every interaction into an opportunity to expand the organization's knowledge base.

File Structure

Core Files Created

deployed-md-files/
├── docs/prompts/claude-instructions.md     # Main instructions file
├── scripts/build-claude-md.sh              # CLAUDE.md assembly script  
├── scripts/build-docs.sh                   # Comprehensive docs builder
└── docs/CLAUDE.md                          # Combined output file

Integration Points

Main build script: build.sh runs docs build before Docker build
Docker integration: Dockerfile.sliplane copies combined CLAUDE.md
Runtime deployment: Instructions available to Claude in deployed containers

Implementation Details

1. Claude Instructions File

Location: /docs/prompts/claude-instructions.md

Core Principles Implemented:

Guide-first philosophy - always check guides before answering
Proactive guide creation mandate - create guides for every significant solution
Institutional knowledge building - document WHY, not just HOW
Pattern recognition - identify documentation opportunities
Cross-referencing - link related guides and specialists

2. CLAUDE.md Assembly Process

Script: /scripts/build-claude-md.sh

Process:

Copies base project CLAUDE.md
Appends comprehensive Claude instructions
Creates unified guidance file
Outputs to deployed-md-files/docs/CLAUDE.md

3. Comprehensive Documentation Builder

Script: /scripts/build-docs.sh

Features:

Builds unified CLAUDE.md with instructions
Verifies documentation structure
Generates HTML static files with doc-builder
Provides build summary and statistics
Integrated into main Docker build process

4. Build Integration

Modified: build.sh

Enhancement:

# Pre-build: Documentation preparation
echo -e "${CYAN}📚 Pre-build: Preparing documentation...${NC}"
cd "$(dirname "$0")/deployed-md-files"
./scripts/build-docs.sh

Key Features

Guide-First Approach

Every question should reference existing guides first
Create new guides when solutions aren't documented
Build interconnected knowledge pathways
Maintain guide quality and relevance

Proactive Documentation

Claude MUST create guides for:

Questions not covered by existing guides
Complex multi-step solutions
Patterns in user questions
New workflows or best practices
Technical troubleshooting solutions

Guide Categories

Organized documentation structure:

Business Strategy: /docs/guides/business/
Research: /docs/guides/research/
Technical Implementation: /docs/guides/technical/
Deployment: /docs/guides/deployment/

Integration with Specialists

Connect user questions with domain experts
Apply specialist methodologies
Create specialist-specific guides
Build bridges between different knowledge domains

Deployment Process

Build Process

Documentation build - Assembles CLAUDE.md and generates HTML
Docker build - Includes documentation in container image
Deployment - Instructions available to Claude in production

Container Integration

Instructions copied to /home/nodejs/all-project-files/docs/
Available during Claude CLI operations
Guides accessible through UI panels
HTML documentation served for web access

Current Statistics

Documentation Inventory:

Guides: 33 files across multiple categories
Specialists: 7 domain expert profiles
Prompts: 5 instruction and template files
Total docs: 49 markdown files
Combined CLAUDE.md: 416+ lines with comprehensive instructions

Usage Examples

Example 1: Deployment Issue

User: "My client deployment isn't working"

Expected Claude Response:
1. Check [Client Deployment Guide](/docs/guides/sasha-client-deployment-guide.md)
2. Use troubleshooting section for diagnosis
3. If new issue discovered, update guide with solution
4. Document specific resolution for future users

Example 2: Business Analysis

User: "How should I analyze this company?"

Expected Claude Response:
1. Reference [Research Specialist](/docs/specialists/research-specialist.md)
2. Apply research methodologies from guides
3. If industry-specific approach needed, create new guide
4. Document analysis framework for reuse

Example 3: Technical Configuration

User: "How do I configure SSH access?"

Expected Claude Response:
1. Check existing technical guides
2. If no guide exists, create "SSH Container Access Setup"
3. Include commands, troubleshooting, security considerations
4. Cross-reference with deployment guides

Success Metrics

Indicators of Success:

Users find answers in guides before asking questions
Complex problems solved using documented procedures
New team members onboard using comprehensive guides
Business decisions reference documented strategies
Technical implementations follow proven patterns
Institutional knowledge grows with each interaction

Maintenance Process

Guide Quality Assurance

Update guides when better approaches are discovered
Archive outdated information with clear explanations
Merge redundant guides into comprehensive resources
Ensure consistent formatting and quality standards

Knowledge Evolution

Learn from each user interaction
Identify gaps in current documentation
Expand guides based on user patterns
Build connections between knowledge domains

Key Principles

Every Interaction Builds Knowledge

Transform every question into institutional memory:

Solve immediate problems
Document solutions as reusable guides
Create knowledge pathways
Build organizational intelligence

Guide-First Philosophy

Guides are the primary source of truth
Reference existing guides before providing solutions
Create new guides when solutions aren't documented
Maintain interconnected knowledge network

Institutional Memory Building

Document WHY decisions were made, not just HOW
Capture business context and rationale
Note lessons learned and common pitfalls
Link related concepts and dependencies

Future Enhancements

Planned Improvements

Automated guide generation from common questions
Integration with user feedback loops
Guide effectiveness metrics and analytics
Dynamic content updates based on usage patterns

Advanced Features

Cross-project knowledge sharing
Industry-specific guide templates
Automated guide quality assessment
Integration with external knowledge sources

This implementation establishes Sasha Studio as a comprehensive knowledge management system where every interaction contributes to organizational intelligence, ensuring that Claude Code becomes an increasingly effective guide creator and knowledge curator over time.