mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-03-30 13:43:26 +08:00
Fix markdownlint errors from merge of affaan-m:main into main
Co-authored-by: pangerlkr <73515951+pangerlkr@users.noreply.github.com>
This commit is contained in:
@@ -40,7 +40,7 @@ With lazy loading, the context window issue is mostly solved. But token usage an
|
||||
For sharing memory across sessions, a skill or command that summarizes and checks in on progress then saves to a `.tmp` file in your `.claude` folder and appends to it until the end of your session is the best bet. The next day it can use that as context and pick up where you left off, create a new file for each session so you don't pollute old context into new work.
|
||||
|
||||

|
||||
*Example of session storage -> https://github.com/affaan-m/everything-claude-code/tree/main/examples/sessions*
|
||||
*Example of session storage -> <https://github.com/affaan-m/everything-claude-code/tree/main/examples/sessions>*
|
||||
|
||||
Claude creates a file summarizing current state. Review it, ask for edits if needed, then start fresh. For the new conversation, just provide the file path. Particularly useful when you're hitting context limits and need to continue complex work. These files should contain:
|
||||
- What approaches worked (verifiably with evidence)
|
||||
@@ -129,7 +129,7 @@ Default to Sonnet for 90% of coding tasks. Upgrade to Opus when first attempt fa
|
||||
**Pricing Reference:**
|
||||
|
||||

|
||||
*Source: https://platform.claude.com/docs/en/about-claude/pricing*
|
||||
*Source: <https://platform.claude.com/docs/en/about-claude/pricing>*
|
||||
|
||||
**Tool-Specific Optimizations:**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user