Uh oh!
There was an error while loading. Please reload this page.
docs: add comprehensive Claude Code session documentation and tools - #30
Merged
Conversation
Import complete Claude Code session documentation including technical specifications, parser implementations, and practical guides based on analysis of 114 session files across 3 projects. Key additions: - Core specifications for DAG structure and message format - Working parser examples with test session files - Implementation guidance for building session tools - Operations reference with validated patterns - Troubleshooting guide for common issues - Example transcript builder for human-readable output This documentation corrects fundamental misconceptions about DAG behavior: - Clarifies that all branches remain permanently in the DAG - Explains active branch determination by file line number - Documents message duplication for complete history preservation - Confirms no mechanism exists to reactivate old branches Provides developers with accurate, actionable documentation for building tools that work with Claude Code's actual session structure. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…aude-code-session-docs
Uh oh!
There was an error while loading. Please reload this page.
Michael J. Jabbour (michaeljabbour) added a commit
to michaeljabbour/amplifier
that referenced
this pull request
Sep 30, 2025
Complete comprehensive technical specification library with all 44 principles: **People (6 specs)** - #1 Small AI-first working groups - #2 Strategic human touchpoints only - #3 Prompt engineering as core skill - microsoft#4 Test-based verification over code review - microsoft#5 Conversation-driven development - microsoft#6 Human escape hatches always available **Process (13 specs)** - microsoft#7 Regenerate, don't edit - microsoft#8 Contract-first everything - microsoft#9 Tests as the quality gate - microsoft#10 Git as safety net - microsoft#11 Continuous validation with fast feedback - microsoft#12 Incremental processing as default - microsoft#13 Parallel exploration by default - microsoft#14 Context management as discipline - microsoft#15 Git-based everything - microsoft#16 Docs define, not describe - microsoft#17 Prompt versioning and testing - microsoft#18 Contract evolution with migration paths - microsoft#19 Cost and token budgeting **Technology (18 specs)** - microsoft#20 Self-modifying AI-first codebase - microsoft#21 Limited and domain-specific by design - microsoft#22 Layered virtualization - microsoft#23 Protected self-healing kernel - microsoft#24 Long-running agent processes - microsoft#25 Simple interfaces by design - microsoft#26 Stateless by default - microsoft#27 Disposable components everywhere - microsoft#28 CLI-first design - microsoft#29 Tool ecosystems as extensions - microsoft#30 Observability baked in - microsoft#31 Idempotency by design (reference) - microsoft#32 Error recovery patterns built in - microsoft#33 Graceful degradation by design - microsoft#34 Feature flags as deployment strategy - microsoft#35 Least-privilege automation - microsoft#36 Dependency pinning and security scanning - microsoft#37 Declarative over imperative **Governance (7 specs)** - microsoft#38 Access control and compliance - microsoft#39 Metrics and evaluation everywhere - microsoft#40 Knowledge stewardship and institutional memory - microsoft#41 Adaptive sandboxing with explicit approvals - microsoft#42 Data governance and privacy controls - microsoft#43 Model lifecycle management - microsoft#44 Self-serve recovery with known-good snapshots Each specification includes: - Plain-language definition - AI-first development rationale - 4-6 implementation approaches - 5 good/bad example pairs with working code - 6 related principles with relationships - 7 common pitfalls with examples - Tools organized by category - 12 actionable checklist items Statistics: - 44 specifications totaling ~10,000+ lines - 220+ good/bad code example pairs - 240+ implementation approaches - 300+ documented anti-patterns - 500+ tools and frameworks - 250+ cross-principle relationships Created through parallel AI agent execution demonstrating Principle microsoft#13 (Parallel Exploration by Default). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Joi Ito (Joi) pushed a commit
to Joi/amplifier
that referenced
this pull request
Oct 31, 2025
…icrosoft#30) * docs: add comprehensive Claude Code session documentation and tools Import complete Claude Code session documentation including technical specifications, parser implementations, and practical guides based on analysis of 114 session files across 3 projects. Key additions: - Core specifications for DAG structure and message format - Working parser examples with test session files - Implementation guidance for building session tools - Operations reference with validated patterns - Troubleshooting guide for common issues - Example transcript builder for human-readable output This documentation corrects fundamental misconceptions about DAG behavior: - Clarifies that all branches remain permanently in the DAG - Explains active branch determination by file line number - Documents message duplication for complete history preservation - Confirms no mechanism exists to reactivate old branches Provides developers with accurate, actionable documentation for building tools that work with Claude Code's actual session structure. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge branch 'main' of https://github.com/microsoft/amplifier into claude-code-session-docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Import complete Claude Code session documentation including technical specifications,
parser implementations, and practical guides based on analysis of 114 session files
across 3 projects.
Key additions:
This documentation corrects fundamental misconceptions about DAG behavior:
Provides developers with accurate, actionable documentation for building
tools that work with Claude Code's actual session structure.
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com