From 43f83995e93b8570c369e171b2e340d82ee4368e Mon Sep 17 00:00:00 2001
From: IndyDevDan <minor7addfloortom@gmail.com>
Date: Fri, 6 Jun 2025 10:26:50 -0500
Subject: [PATCH] progress

---
 .claude/commands/infinite.md           |   74 ++
 ai_docs/claude_code_fresh_tutorials.md | 1328 ++++++++++++++++++++++++
 2 files changed, 1402 insertions(+)
 create mode 100644 .claude/commands/infinite.md
 create mode 100644 ai_docs/claude_code_fresh_tutorials.md

diff --git a/.claude/commands/infinite.md b/.claude/commands/infinite.md
new file mode 100644
index 0000000..afb45f2
--- /dev/null
+++ b/.claude/commands/infinite.md
@@ -0,0 +1,74 @@
+**INFINITE AGENTIC LOOP COMMAND**
+
+Think deeply about this infinite generation task. You are about to embark on a sophisticated iterative creation process.
+
+**Variables:**
+
+spec_file: $ARGUMENTS
+output_dir: $ARGUMENTS
+count: $ARGUMENTS
+
+**ARGUMENTS PARSING:**
+Parse the following arguments from "$ARGUMENTS":
+1. `spec_file` - Path to the markdown specification file
+2. `output_dir` - Directory where iterations will be saved  
+3. `count` - Number of iterations (1-N or "infinite")
+
+**PHASE 1: SPECIFICATION ANALYSIS**
+Read and deeply understand the specification file at `spec_file`. This file defines:
+- What type of content to generate
+- The format and structure requirements
+- Any specific parameters or constraints
+- The intended evolution pattern between iterations
+
+Think carefully about the spec's intent and how each iteration should build upon previous work.
+
+**PHASE 2: OUTPUT DIRECTORY RECONNAISSANCE** 
+Thoroughly analyze the `output_dir` to understand the current state:
+- List all existing files and their naming patterns
+- Identify the highest iteration number currently present
+- Analyze the content evolution across existing iterations
+- Understand the trajectory of previous generations
+- Determine what gaps or opportunities exist for new iterations
+
+**PHASE 3: ITERATION STRATEGY**
+Based on the spec analysis and existing iterations:
+- Determine the starting iteration number (highest existing + 1)
+- Plan how each new iteration will be unique and evolutionary
+- Consider how to build upon previous iterations while maintaining novelty
+- If count is "infinite", prepare for continuous generation until context limits
+
+**PHASE 4: GENERATION EXECUTION**
+For each iteration to generate:
+
+1. **Deep Context Analysis**: Review the spec requirements and all previous iterations
+2. **Evolutionary Planning**: Plan how this iteration will advance beyond previous ones
+3. **Unique Content Creation**: Generate content that fulfills the spec while being distinctly new
+4. **Quality Validation**: Ensure the output meets spec requirements and adds value
+5. **File Naming**: Use the pattern specified in the spec with proper iteration suffixing
+
+**PHASE 5: INFINITE MODE HANDLING**
+If count is "infinite":
+- Continue generating iterations until you approach context window limits
+- Monitor your remaining context capacity
+- Each iteration should become progressively more sophisticated
+- Maintain awareness of when to gracefully conclude the generation cycle
+- Provide a summary of all iterations created in the infinite run
+
+**EXECUTION PRINCIPLES:**
+- Each iteration must be genuinely unique and valuable
+- Build upon previous work while introducing novel elements
+- Maintain consistency with the original specification
+- Ensure proper file organization and naming
+- Think deeply about the evolution trajectory
+- For infinite mode, optimize for maximum valuable output before context exhaustion
+
+**ULTRA-THINKING DIRECTIVE:**
+Before beginning generation, engage in extended thinking about:
+- The deeper implications of the specification
+- How to create meaningful progression across iterations  
+- What makes each iteration valuable and unique
+- The optimal strategy for infinite generation
+- How to balance consistency with innovation
+
+Begin execution with deep analysis and proceed systematically through each phase.
\ No newline at end of file
diff --git a/ai_docs/claude_code_fresh_tutorials.md b/ai_docs/claude_code_fresh_tutorials.md
new file mode 100644
index 0000000..e09aabf
--- /dev/null
+++ b/ai_docs/claude_code_fresh_tutorials.md
@@ -0,0 +1,1328 @@
+[Anthropic home page![light logo](https://mintlify.s3.us-west-1.amazonaws.com/anthropic/logo/light.svg)![dark logo](https://mintlify.s3.us-west-1.amazonaws.com/anthropic/logo/dark.svg)](https://docs.anthropic.com/)
+
+English
+
+Search...
+
+Ctrl K
+
+Search...
+
+Navigation
+
+Claude Code
+
+Tutorials
+
+[Welcome](https://docs.anthropic.com/en/home) [Developer Guide](https://docs.anthropic.com/en/docs/welcome) [API Guide](https://docs.anthropic.com/en/api/overview) [Claude Code](https://docs.anthropic.com/en/docs/claude-code/overview) [Resources](https://docs.anthropic.com/en/resources/overview) [Release Notes](https://docs.anthropic.com/en/release-notes/overview)
+
+This guide provides step-by-step tutorials for common workflows with Claude Code. Each tutorial includes clear instructions, example commands, and best practices to help you get the most from Claude Code.
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#table-of-contents)  Table of contents
+
+- [Resume previous conversations](https://docs.anthropic.com/en/docs/claude-code/tutorials#resume-previous-conversations)
+- [Understand new codebases](https://docs.anthropic.com/en/docs/claude-code/tutorials#understand-new-codebases)
+- [Fix bugs efficiently](https://docs.anthropic.com/en/docs/claude-code/tutorials#fix-bugs-efficiently)
+- [Refactor code](https://docs.anthropic.com/en/docs/claude-code/tutorials#refactor-code)
+- [Work with tests](https://docs.anthropic.com/en/docs/claude-code/tutorials#work-with-tests)
+- [Create pull requests](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-pull-requests)
+- [Handle documentation](https://docs.anthropic.com/en/docs/claude-code/tutorials#handle-documentation)
+- [Work with images](https://docs.anthropic.com/en/docs/claude-code/tutorials#work-with-images)
+- [Use extended thinking](https://docs.anthropic.com/en/docs/claude-code/tutorials#use-extended-thinking)
+- [Set up project memory](https://docs.anthropic.com/en/docs/claude-code/tutorials#set-up-project-memory)
+- [Set up Model Context Protocol (MCP)](https://docs.anthropic.com/en/docs/claude-code/tutorials#set-up-model-context-protocol-mcp)
+- [Use Claude as a unix-style utility](https://docs.anthropic.com/en/docs/claude-code/tutorials#use-claude-as-a-unix-style-utility)
+- [Create custom slash commands](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-custom-slash-commands)
+- [Run parallel Claude Code sessions with Git worktrees](https://docs.anthropic.com/en/docs/claude-code/tutorials#run-parallel-claude-code-sessions-with-git-worktrees)
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#resume-previous-conversations)  Resume previous conversations
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#continue-your-work-seamlessly)  Continue your work seamlessly
+
+**When to use:** You've been working on a task with Claude Code and need to continue where you left off in a later session.
+
+Claude Code provides two options for resuming previous conversations:
+
+- `--continue` to automatically continue the most recent conversation
+- `--resume` to display a conversation picker
+
+1
+
+Continue the most recent conversation
+
+Copy
+
+```bash
+claude --continue
+
+```
+
+This immediately resumes your most recent conversation without any prompts.
+
+2
+
+Continue in non-interactive mode
+
+Copy
+
+```bash
+claude --continue --print "Continue with my task"
+
+```
+
+Use `--print` with `--continue` to resume the most recent conversation in non-interactive mode, perfect for scripts or automation.
+
+3
+
+Show conversation picker
+
+Copy
+
+```bash
+claude --resume
+
+```
+
+This displays an interactive conversation selector showing:
+
+- Conversation start time
+- Initial prompt or conversation summary
+- Message count
+
+Use arrow keys to navigate and press Enter to select a conversation.
+
+**How it works:**
+
+1. **Conversation Storage**: All conversations are automatically saved locally with their full message history
+2. **Message Deserialization**: When resuming, the entire message history is restored to maintain context
+3. **Tool State**: Tool usage and results from the previous conversation are preserved
+4. **Context Restoration**: The conversation resumes with all previous context intact
+
+**Tips:**
+
+- Conversation history is stored locally on your machine
+- Use `--continue` for quick access to your most recent conversation
+- Use `--resume` when you need to select a specific past conversation
+- When resuming, you'll see the entire conversation history before continuing
+- The resumed conversation starts with the same model and configuration as the original
+
+**Examples:**
+
+Copy
+
+```bash
+# Continue most recent conversation
+claude --continue
+
+# Continue most recent conversation with a specific prompt
+claude --continue --print "Show me our progress"
+
+# Show conversation picker
+claude --resume
+
+# Continue most recent conversation in non-interactive mode
+claude --continue --print "Run the tests again"
+
+```
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#understand-new-codebases)  Understand new codebases
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#get-a-quick-codebase-overview)  Get a quick codebase overview
+
+**When to use:** You've just joined a new project and need to understand its structure quickly.
+
+1
+
+Navigate to the project root directory
+
+Copy
+
+```bash
+cd /path/to/project
+
+```
+
+2
+
+Start Claude Code
+
+Copy
+
+```bash
+claude
+
+```
+
+3
+
+Ask for a high-level overview
+
+Copy
+
+```
+> give me an overview of this codebase
+
+```
+
+4
+
+Dive deeper into specific components
+
+Copy
+
+```
+> explain the main architecture patterns used here
+
+```
+
+Copy
+
+```
+> what are the key data models?
+
+```
+
+Copy
+
+```
+> how is authentication handled?
+
+```
+
+**Tips:**
+
+- Start with broad questions, then narrow down to specific areas
+- Ask about coding conventions and patterns used in the project
+- Request a glossary of project-specific terms
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#find-relevant-code)  Find relevant code
+
+**When to use:** You need to locate code related to a specific feature or functionality.
+
+1
+
+Ask Claude to find relevant files
+
+Copy
+
+```
+> find the files that handle user authentication
+
+```
+
+2
+
+Get context on how components interact
+
+Copy
+
+```
+> how do these authentication files work together?
+
+```
+
+3
+
+Understand the execution flow
+
+Copy
+
+```
+> trace the login process from front-end to database
+
+```
+
+**Tips:**
+
+- Be specific about what you're looking for
+- Use domain language from the project
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#fix-bugs-efficiently)  Fix bugs efficiently
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#diagnose-error-messages)  Diagnose error messages
+
+**When to use:** You've encountered an error message and need to find and fix its source.
+
+1
+
+Share the error with Claude
+
+Copy
+
+```
+> I'm seeing an error when I run npm test
+
+```
+
+2
+
+Ask for fix recommendations
+
+Copy
+
+```
+> suggest a few ways to fix the @ts-ignore in user.ts
+
+```
+
+3
+
+Apply the fix
+
+Copy
+
+```
+> update user.ts to add the null check you suggested
+
+```
+
+**Tips:**
+
+- Tell Claude the command to reproduce the issue and get a stack trace
+- Mention any steps to reproduce the error
+- Let Claude know if the error is intermittent or consistent
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#refactor-code)  Refactor code
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#modernize-legacy-code)  Modernize legacy code
+
+**When to use:** You need to update old code to use modern patterns and practices.
+
+1
+
+Identify legacy code for refactoring
+
+Copy
+
+```
+> find deprecated API usage in our codebase
+
+```
+
+2
+
+Get refactoring recommendations
+
+Copy
+
+```
+> suggest how to refactor utils.js to use modern JavaScript features
+
+```
+
+3
+
+Apply the changes safely
+
+Copy
+
+```
+> refactor utils.js to use ES2024 features while maintaining the same behavior
+
+```
+
+4
+
+Verify the refactoring
+
+Copy
+
+```
+> run tests for the refactored code
+
+```
+
+**Tips:**
+
+- Ask Claude to explain the benefits of the modern approach
+- Request that changes maintain backward compatibility when needed
+- Do refactoring in small, testable increments
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#work-with-tests)  Work with tests
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#add-test-coverage)  Add test coverage
+
+**When to use:** You need to add tests for uncovered code.
+
+1
+
+Identify untested code
+
+Copy
+
+```
+> find functions in NotificationsService.swift that are not covered by tests
+
+```
+
+2
+
+Generate test scaffolding
+
+Copy
+
+```
+> add tests for the notification service
+
+```
+
+3
+
+Add meaningful test cases
+
+Copy
+
+```
+> add test cases for edge conditions in the notification service
+
+```
+
+4
+
+Run and verify tests
+
+Copy
+
+```
+> run the new tests and fix any failures
+
+```
+
+**Tips:**
+
+- Ask for tests that cover edge cases and error conditions
+- Request both unit and integration tests when appropriate
+- Have Claude explain the testing strategy
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#create-pull-requests)  Create pull requests
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#generate-comprehensive-prs)  Generate comprehensive PRs
+
+**When to use:** You need to create a well-documented pull request for your changes.
+
+1
+
+Summarize your changes
+
+Copy
+
+```
+> summarize the changes I've made to the authentication module
+
+```
+
+2
+
+Generate a PR with Claude
+
+Copy
+
+```
+> create a pr
+
+```
+
+3
+
+Review and refine
+
+Copy
+
+```
+> enhance the PR description with more context about the security improvements
+
+```
+
+4
+
+Add testing details
+
+Copy
+
+```
+> add information about how these changes were tested
+
+```
+
+**Tips:**
+
+- Ask Claude directly to make a PR for you
+- Review Claude's generated PR before submitting
+- Ask Claude to highlight potential risks or considerations
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#handle-documentation)  Handle documentation
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#generate-code-documentation)  Generate code documentation
+
+**When to use:** You need to add or update documentation for your code.
+
+1
+
+Identify undocumented code
+
+Copy
+
+```
+> find functions without proper JSDoc comments in the auth module
+
+```
+
+2
+
+Generate documentation
+
+Copy
+
+```
+> add JSDoc comments to the undocumented functions in auth.js
+
+```
+
+3
+
+Review and enhance
+
+Copy
+
+```
+> improve the generated documentation with more context and examples
+
+```
+
+4
+
+Verify documentation
+
+Copy
+
+```
+> check if the documentation follows our project standards
+
+```
+
+**Tips:**
+
+- Specify the documentation style you want (JSDoc, docstrings, etc.)
+- Ask for examples in the documentation
+- Request documentation for public APIs, interfaces, and complex logic
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#work-with-images)  Work with images
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#analyze-images-and-screenshots)  Analyze images and screenshots
+
+**When to use:** You need to work with images in your codebase or get Claude's help analyzing image content.
+
+1
+
+Add an image to the conversation
+
+You can use any of these methods:
+
+1. Drag and drop an image into the Claude Code window
+2. Copy an image and paste it into the CLI with cmd+v (on Mac)
+3. Provide an image path claude "Analyze this image: /path/to/your/image.png"
+
+2
+
+Ask Claude to analyze the image
+
+Copy
+
+```
+> What does this image show?
+> Describe the UI elements in this screenshot
+> Are there any problematic elements in this diagram?
+
+```
+
+3
+
+Use images for context
+
+Copy
+
+```
+> Here's a screenshot of the error. What's causing it?
+> This is our current database schema. How should we modify it for the new feature?
+
+```
+
+4
+
+Get code suggestions from visual content
+
+Copy
+
+```
+> Generate CSS to match this design mockup
+> What HTML structure would recreate this component?
+
+```
+
+**Tips:**
+
+- Use images when text descriptions would be unclear or cumbersome
+- Include screenshots of errors, UI designs, or diagrams for better context
+- You can work with multiple images in a conversation
+- Image analysis works with diagrams, screenshots, mockups, and more
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#use-extended-thinking)  Use extended thinking
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#leverage-claude%E2%80%99s-extended-thinking-for-complex-tasks)  Leverage Claude's extended thinking for complex tasks
+
+**When to use:** When working on complex architectural decisions, challenging bugs, or planning multi-step implementations that require deep reasoning.
+
+1
+
+Provide context and ask Claude to think
+
+Copy
+
+```
+> I need to implement a new authentication system using OAuth2 for our API. Think deeply about the best approach for implementing this in our codebase.
+
+```
+
+Claude will gather relevant information from your codebase and
+use extended thinking, which will be visible in the interface.
+
+2
+
+Refine the thinking with follow-up prompts
+
+Copy
+
+```
+> think about potential security vulnerabilities in this approach
+> think harder about edge cases we should handle
+
+```
+
+**Tips to get the most value out of extended thinking:**
+
+Extended thinking is most valuable for complex tasks such as:
+
+- Planning complex architectural changes
+- Debugging intricate issues
+- Creating implementation plans for new features
+- Understanding complex codebases
+- Evaluating tradeoffs between different approaches
+
+The way you prompt for thinking results in varying levels of thinking depth:
+
+- "think" triggers basic extended thinking
+- intensifying phrases such as "think more", "think a lot", "think harder", or "think longer" triggers deeper thinking
+
+For more extended thinking prompting tips, see [Extended thinking tips](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/extended-thinking-tips).
+
+Claude will display its thinking process as italic gray text above the
+response.
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#set-up-project-memory)  Set up project memory
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#create-an-effective-claude-md-file)  Create an effective CLAUDE.md file
+
+**When to use:** You want to set up a CLAUDE.md file to store important project information, conventions, and frequently used commands.
+
+1
+
+Bootstrap a CLAUDE.md for your codebase
+
+Copy
+
+```
+> /init
+
+```
+
+**Tips:**
+
+- Include frequently used commands (build, test, lint) to avoid repeated searches
+- Document code style preferences and naming conventions
+- Add important architectural patterns specific to your project
+- CLAUDE.md memories can be used for both instructions shared with your team and for your individual preferences.
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#set-up-model-context-protocol-mcp)  Set up Model Context Protocol (MCP)
+
+Model Context Protocol (MCP) is an open protocol that enables LLMs to access external tools and data sources. For more details, see the [MCP documentation](https://modelcontextprotocol.io/introduction).
+
+Use third party MCP servers at your own risk. Make sure you trust the MCP
+servers, and be especially careful when using MCP servers that talk to the
+internet, as these can expose you to prompt injection risk.
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#configure-mcp-servers)  Configure MCP servers
+
+**When to use:** You want to enhance Claude's capabilities by connecting it to specialized tools and external servers using the Model Context Protocol.
+
+1
+
+Add an MCP Stdio Server
+
+Copy
+
+```bash
+# Basic syntax
+claude mcp add <name> <command> [args...]
+
+# Example: Adding a local server
+claude mcp add my-server -e API_KEY=123 -- /path/to/server arg1 arg2
+
+```
+
+2
+
+Add an MCP SSE Server
+
+Copy
+
+```bash
+# Basic syntax
+claude mcp add --transport sse <name> <url>
+
+# Example: Adding an SSE server
+claude mcp add --transport sse sse-server https://example.com/sse-endpoint
+
+```
+
+3
+
+Manage your MCP servers
+
+Copy
+
+```bash
+# List all configured servers
+claude mcp list
+
+# Get details for a specific server
+claude mcp get my-server
+
+# Remove a server
+claude mcp remove my-server
+
+```
+
+**Tips:**
+
+- Use the `-s` or `--scope` flag to specify where the configuration is stored:
+
+  - `local` (default): Available only to you in the current project (was called `project` in older versions)
+  - `project`: Shared with everyone in the project via `.mcp.json` file
+  - `user`: Available to you across all projects (was called `global` in older versions)
+- Set environment variables with `-e` or `--env` flags (e.g., `-e KEY=value`)
+- Configure MCP server startup timeout using the MCP\_TIMEOUT environment variable (e.g., `MCP_TIMEOUT=10000 claude` sets a 10-second timeout)
+- Check MCP server status any time using the `/mcp` command within Claude Code
+- MCP follows a client-server architecture where Claude Code (the client) can connect to multiple specialized servers
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#understanding-mcp-server-scopes)  Understanding MCP server scopes
+
+**When to use:** You want to understand how different MCP scopes work and how to share servers with your team.
+
+1
+
+Local-scoped MCP servers
+
+The default scope ( `local`) stores MCP server configurations in your project-specific user settings. These servers are only available to you while working in the current project.
+
+Copy
+
+```bash
+# Add a local-scoped server (default)
+claude mcp add my-private-server /path/to/server
+
+# Explicitly specify local scope
+claude mcp add my-private-server -s local /path/to/server
+
+```
+
+2
+
+Project-scoped MCP servers (.mcp.json)
+
+Project-scoped servers are stored in a `.mcp.json` file at the root of your project. This file should be checked into version control to share servers with your team.
+
+Copy
+
+```bash
+# Add a project-scoped server
+claude mcp add shared-server -s project /path/to/server
+
+```
+
+This creates or updates a `.mcp.json` file with the following structure:
+
+Copy
+
+```json
+{
+  "mcpServers": {
+    "shared-server": {
+      "command": "/path/to/server",
+      "args": [],
+      "env": {}
+    }
+  }
+}
+
+```
+
+3
+
+User-scoped MCP servers
+
+User-scoped servers are available to you across all projects on your machine, and are private to you.
+
+Copy
+
+```bash
+# Add a user server
+claude mcp add my-user-server -s user /path/to/server
+
+```
+
+**Tips:**
+
+- Local-scoped servers take precedence over project-scoped and user-scoped servers with the same name
+- Project-scoped servers (in `.mcp.json`) take precedence over user-scoped servers with the same name
+- Before using project-scoped servers from `.mcp.json`, Claude Code will prompt you to approve them for security
+- The `.mcp.json` file is intended to be checked into version control to share MCP servers with your team
+- Project-scoped servers make it easy to ensure everyone on your team has access to the same MCP tools
+- If you need to reset your choices for which project-scoped servers are enabled or disabled, use the `claude mcp reset-project-choices` command
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#connect-to-a-postgres-mcp-server)  Connect to a Postgres MCP server
+
+**When to use:** You want to give Claude read-only access to a PostgreSQL database for querying and schema inspection.
+
+1
+
+Add the Postgres MCP server
+
+Copy
+
+```bash
+claude mcp add postgres-server /path/to/postgres-mcp-server --connection-string "postgresql://user:pass@localhost:5432/mydb"
+
+```
+
+2
+
+Query your database with Claude
+
+Copy
+
+```
+# In your Claude session, you can ask about your database
+
+> describe the schema of our users table
+> what are the most recent orders in the system?
+> show me the relationship between customers and invoices
+
+```
+
+**Tips:**
+
+- The Postgres MCP server provides read-only access for safety
+- Claude can help you explore database structure and run analytical queries
+- You can use this to quickly understand database schemas in unfamiliar projects
+- Make sure your connection string uses appropriate credentials with minimum required permissions
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#add-mcp-servers-from-json-configuration)  Add MCP servers from JSON configuration
+
+**When to use:** You have a JSON configuration for a single MCP server that you want to add to Claude Code.
+
+1
+
+Add an MCP server from JSON
+
+Copy
+
+```bash
+# Basic syntax
+claude mcp add-json <name> '<json>'
+
+# Example: Adding a stdio server with JSON configuration
+claude mcp add-json weather-api '{"type":"stdio","command":"/path/to/weather-cli","args":["--api-key","abc123"],"env":{"CACHE_DIR":"/tmp"}}'
+
+```
+
+2
+
+Verify the server was added
+
+Copy
+
+```bash
+claude mcp get weather-api
+
+```
+
+**Tips:**
+
+- Make sure the JSON is properly escaped in your shell
+- The JSON must conform to the MCP server configuration schema
+- You can use `-s global` to add the server to your global configuration instead of the project-specific one
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#import-mcp-servers-from-claude-desktop)  Import MCP servers from Claude Desktop
+
+**When to use:** You have already configured MCP servers in Claude Desktop and want to use the same servers in Claude Code without manually reconfiguring them.
+
+1
+
+Import servers from Claude Desktop
+
+Copy
+
+```bash
+# Basic syntax
+claude mcp add-from-claude-desktop
+
+```
+
+2
+
+Select which servers to import
+
+After running the command, you'll see an interactive dialog that allows you to select which servers you want to import.
+
+3
+
+Verify the servers were imported
+
+Copy
+
+```bash
+claude mcp list
+
+```
+
+**Tips:**
+
+- This feature only works on macOS and Windows Subsystem for Linux (WSL)
+- It reads the Claude Desktop configuration file from its standard location on those platforms
+- Use the `-s global` flag to add servers to your global configuration
+- Imported servers will have the same names as in Claude Desktop
+- If servers with the same names already exist, they will get a numerical suffix (e.g., `server_1`)
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#use-claude-code-as-an-mcp-server)  Use Claude Code as an MCP server
+
+**When to use:** You want to use Claude Code itself as an MCP server that other applications can connect to, providing them with Claude's tools and capabilities.
+
+1
+
+Start Claude as an MCP server
+
+Copy
+
+```bash
+# Basic syntax
+claude mcp serve
+
+```
+
+2
+
+Connect from another application
+
+You can connect to Claude Code MCP server from any MCP client, such as Claude Desktop. If you're using Claude Desktop, you can add the Claude Code MCP server using this configuration:
+
+Copy
+
+```json
+{
+  "command": "claude",
+  "args": ["mcp", "serve"],
+  "env": {}
+}
+
+```
+
+**Tips:**
+
+- The server provides access to Claude's tools like View, Edit, LS, etc.
+- In Claude Desktop, try asking Claude to read files in a directory, make edits, and more.
+- Note that this MCP server is simply exposing Claude Code's tools to your MCP client, so your own client is responsible for implementing user confirmation for individual tool calls.
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#use-claude-as-a-unix-style-utility)  Use Claude as a unix-style utility
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#add-claude-to-your-verification-process)  Add Claude to your verification process
+
+**When to use:** You want to use Claude Code as a linter or code reviewer.
+
+**Steps:**
+
+1
+
+Add Claude to your build script
+
+Copy
+
+```json
+// package.json
+{
+    ...
+    "scripts": {
+        ...
+        "lint:claude": "claude -p 'you are a linter. please look at the changes vs. main and report any issues related to typos. report the filename and line number on one line, and a description of the issue on the second line. do not return any other text.'"
+    }
+}
+
+```
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#pipe-in%2C-pipe-out)  Pipe in, pipe out
+
+**When to use:** You want to pipe data into Claude, and get back data in a structured format.
+
+1
+
+Pipe data through Claude
+
+Copy
+
+```bash
+cat build-error.txt | claude -p 'concisely explain the root cause of this build error' > output.txt
+
+```
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#control-output-format)  Control output format
+
+**When to use:** You need Claude's output in a specific format, especially when integrating Claude Code into scripts or other tools.
+
+1
+
+Use text format (default)
+
+Copy
+
+```bash
+cat data.txt | claude -p 'summarize this data' --output-format text > summary.txt
+
+```
+
+This outputs just Claude's plain text response (default behavior).
+
+2
+
+Use JSON format
+
+Copy
+
+```bash
+cat code.py | claude -p 'analyze this code for bugs' --output-format json > analysis.json
+
+```
+
+This outputs a JSON array of messages with metadata including cost and duration.
+
+3
+
+Use streaming JSON format
+
+Copy
+
+```bash
+cat log.txt | claude -p 'parse this log file for errors' --output-format stream-json
+
+```
+
+This outputs a series of JSON objects in real-time as Claude processes the request. Each message is a valid JSON object, but the entire output is not valid JSON if concatenated.
+
+**Tips:**
+
+- Use `--output-format text` for simple integrations where you just need Claude's response
+- Use `--output-format json` when you need the full conversation log
+- Use `--output-format stream-json` for real-time output of each conversation turn
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#create-custom-slash-commands)  Create custom slash commands
+
+Claude Code supports custom slash commands that you can create to quickly execute specific prompts or tasks.
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#create-project-specific-commands)  Create project-specific commands
+
+**When to use:** You want to create reusable slash commands for your project that all team members can use.
+
+1
+
+Create a commands directory in your project
+
+Copy
+
+```bash
+mkdir -p .claude/commands
+
+```
+
+2
+
+Create a Markdown file for each command
+
+Copy
+
+```bash
+echo "Analyze the performance of this code and suggest three specific optimizations:" > .claude/commands/optimize.md
+
+```
+
+3
+
+Use your custom command in Claude Code
+
+Copy
+
+```bash
+claude > /project:optimize
+
+```
+
+**Tips:**
+
+- Command names are derived from the filename (e.g., `optimize.md` becomes `/project:optimize`)
+- You can organize commands in subdirectories (e.g., `.claude/commands/frontend/component.md` becomes `/project:frontend:component`)
+- Project commands are available to everyone who clones the repository
+- The Markdown file content becomes the prompt sent to Claude when the command is invoked
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#add-command-arguments-with-%24arguments)  Add command arguments with $ARGUMENTS
+
+**When to use:** You want to create flexible slash commands that can accept additional input from users.
+
+1
+
+Create a command file with the $ARGUMENTS placeholder
+
+Copy
+
+```bash
+echo "Find and fix issue #$ARGUMENTS. Follow these steps: 1.
+Understand the issue described in the ticket 2. Locate the relevant code in
+our codebase 3. Implement a solution that addresses the root cause 4. Add
+appropriate tests 5. Prepare a concise PR description" >
+.claude/commands/fix-issue.md
+
+```
+
+2
+
+Use the command with an issue number
+
+Copy
+
+```bash
+claude > /project:fix-issue 123
+
+```
+
+This will replace $ARGUMENTS with "123" in the prompt.
+
+**Tips:**
+
+- The $ARGUMENTS placeholder is replaced with any text that follows the command
+- You can position $ARGUMENTS anywhere in your command template
+- Other useful applications: generating test cases for specific functions, creating documentation for components, reviewing code in particular files, or translating content to specified languages
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#create-personal-slash-commands)  Create personal slash commands
+
+**When to use:** You want to create personal slash commands that work across all your projects.
+
+1
+
+Create a commands directory in your home folder
+
+Copy
+
+```bash
+mkdir -p ~/.claude/commands
+
+```
+
+2
+
+Create a Markdown file for each command
+
+Copy
+
+```bash
+echo "Review this code for security vulnerabilities, focusing on:" >
+~/.claude/commands/security-review.md
+
+```
+
+3
+
+Use your personal custom command
+
+Copy
+
+```bash
+claude > /user:security-review
+
+```
+
+**Tips:**
+
+- Personal commands are prefixed with `/user:` instead of `/project:`
+- Personal commands are only available to you and not shared with your team
+- Personal commands work across all your projects
+- You can use these for consistent workflows across different codebases
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#run-parallel-claude-code-sessions-with-git-worktrees)  Run parallel Claude Code sessions with Git worktrees
+
+### [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#use-worktrees-for-isolated-coding-environments)  Use worktrees for isolated coding environments
+
+**When to use:** You need to work on multiple tasks simultaneously with complete code isolation between Claude Code instances.
+
+1
+
+Understand Git worktrees
+
+Git worktrees allow you to check out multiple branches from the same
+repository into separate directories. Each worktree has its own working
+directory with isolated files, while sharing the same Git history. Learn
+more in the [official Git worktree\\
+documentation](https://git-scm.com/docs/git-worktree).
+
+2
+
+Create a new worktree
+
+Copy
+
+```bash
+# Create a new worktree with a new branch
+git worktree add ../project-feature-a -b feature-a
+
+# Or create a worktree with an existing branch
+git worktree add ../project-bugfix bugfix-123
+
+```
+
+This creates a new directory with a separate working copy of your repository.
+
+3
+
+Run Claude Code in each worktree
+
+Copy
+
+```bash
+# Navigate to your worktree
+cd ../project-feature-a
+
+# Run Claude Code in this isolated environment
+claude
+
+```
+
+4
+
+In another terminal:
+
+Copy
+
+```bash
+cd ../project-bugfix
+claude
+
+```
+
+5
+
+Manage your worktrees
+
+Copy
+
+```bash
+# List all worktrees
+git worktree list
+
+# Remove a worktree when done
+git worktree remove ../project-feature-a
+
+```
+
+**Tips:**
+
+- Each worktree has its own independent file state, making it perfect for parallel Claude Code sessions
+- Changes made in one worktree won't affect others, preventing Claude instances from interfering with each other
+- All worktrees share the same Git history and remote connections
+- For long-running tasks, you can have Claude working in one worktree while you continue development in another
+- Use descriptive directory names to easily identify which task each worktree is for
+- Remember to initialize your development environment in each new worktree according to your project's setup. Depending on your stack, this might include:
+  - JavaScript projects: Running dependency installation ( `npm install`, `yarn`)
+  - Python projects: Setting up virtual environments or installing with package managers
+  - Other languages: Following your project's standard setup process
+
+* * *
+
+## [​](https://docs.anthropic.com/en/docs/claude-code/tutorials\#next-steps)  Next steps
+
+[**Claude Code reference implementation** \\
+\\
+Clone our development container reference implementation.](https://github.com/anthropics/claude-code/tree/main/.devcontainer)
+
+Was this page helpful?
+
+YesNo
+
+[SDK](https://docs.anthropic.com/en/docs/claude-code/sdk) [Troubleshooting](https://docs.anthropic.com/en/docs/claude-code/troubleshooting)
+
+On this page
+
+- [Table of contents](https://docs.anthropic.com/en/docs/claude-code/tutorials#table-of-contents)
+- [Resume previous conversations](https://docs.anthropic.com/en/docs/claude-code/tutorials#resume-previous-conversations)
+- [Continue your work seamlessly](https://docs.anthropic.com/en/docs/claude-code/tutorials#continue-your-work-seamlessly)
+- [Understand new codebases](https://docs.anthropic.com/en/docs/claude-code/tutorials#understand-new-codebases)
+- [Get a quick codebase overview](https://docs.anthropic.com/en/docs/claude-code/tutorials#get-a-quick-codebase-overview)
+- [Find relevant code](https://docs.anthropic.com/en/docs/claude-code/tutorials#find-relevant-code)
+- [Fix bugs efficiently](https://docs.anthropic.com/en/docs/claude-code/tutorials#fix-bugs-efficiently)
+- [Diagnose error messages](https://docs.anthropic.com/en/docs/claude-code/tutorials#diagnose-error-messages)
+- [Refactor code](https://docs.anthropic.com/en/docs/claude-code/tutorials#refactor-code)
+- [Modernize legacy code](https://docs.anthropic.com/en/docs/claude-code/tutorials#modernize-legacy-code)
+- [Work with tests](https://docs.anthropic.com/en/docs/claude-code/tutorials#work-with-tests)
+- [Add test coverage](https://docs.anthropic.com/en/docs/claude-code/tutorials#add-test-coverage)
+- [Create pull requests](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-pull-requests)
+- [Generate comprehensive PRs](https://docs.anthropic.com/en/docs/claude-code/tutorials#generate-comprehensive-prs)
+- [Handle documentation](https://docs.anthropic.com/en/docs/claude-code/tutorials#handle-documentation)
+- [Generate code documentation](https://docs.anthropic.com/en/docs/claude-code/tutorials#generate-code-documentation)
+- [Work with images](https://docs.anthropic.com/en/docs/claude-code/tutorials#work-with-images)
+- [Analyze images and screenshots](https://docs.anthropic.com/en/docs/claude-code/tutorials#analyze-images-and-screenshots)
+- [Use extended thinking](https://docs.anthropic.com/en/docs/claude-code/tutorials#use-extended-thinking)
+- [Leverage Claude's extended thinking for complex tasks](https://docs.anthropic.com/en/docs/claude-code/tutorials#leverage-claude%E2%80%99s-extended-thinking-for-complex-tasks)
+- [Set up project memory](https://docs.anthropic.com/en/docs/claude-code/tutorials#set-up-project-memory)
+- [Create an effective CLAUDE.md file](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-an-effective-claude-md-file)
+- [Set up Model Context Protocol (MCP)](https://docs.anthropic.com/en/docs/claude-code/tutorials#set-up-model-context-protocol-mcp)
+- [Configure MCP servers](https://docs.anthropic.com/en/docs/claude-code/tutorials#configure-mcp-servers)
+- [Understanding MCP server scopes](https://docs.anthropic.com/en/docs/claude-code/tutorials#understanding-mcp-server-scopes)
+- [Connect to a Postgres MCP server](https://docs.anthropic.com/en/docs/claude-code/tutorials#connect-to-a-postgres-mcp-server)
+- [Add MCP servers from JSON configuration](https://docs.anthropic.com/en/docs/claude-code/tutorials#add-mcp-servers-from-json-configuration)
+- [Import MCP servers from Claude Desktop](https://docs.anthropic.com/en/docs/claude-code/tutorials#import-mcp-servers-from-claude-desktop)
+- [Use Claude Code as an MCP server](https://docs.anthropic.com/en/docs/claude-code/tutorials#use-claude-code-as-an-mcp-server)
+- [Use Claude as a unix-style utility](https://docs.anthropic.com/en/docs/claude-code/tutorials#use-claude-as-a-unix-style-utility)
+- [Add Claude to your verification process](https://docs.anthropic.com/en/docs/claude-code/tutorials#add-claude-to-your-verification-process)
+- [Pipe in, pipe out](https://docs.anthropic.com/en/docs/claude-code/tutorials#pipe-in%2C-pipe-out)
+- [Control output format](https://docs.anthropic.com/en/docs/claude-code/tutorials#control-output-format)
+- [Create custom slash commands](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-custom-slash-commands)
+- [Create project-specific commands](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-project-specific-commands)
+- [Add command arguments with $ARGUMENTS](https://docs.anthropic.com/en/docs/claude-code/tutorials#add-command-arguments-with-%24arguments)
+- [Create personal slash commands](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-personal-slash-commands)
+- [Run parallel Claude Code sessions with Git worktrees](https://docs.anthropic.com/en/docs/claude-code/tutorials#run-parallel-claude-code-sessions-with-git-worktrees)
+- [Use worktrees for isolated coding environments](https://docs.anthropic.com/en/docs/claude-code/tutorials#use-worktrees-for-isolated-coding-environments)
+- [Next steps](https://docs.anthropic.com/en/docs/claude-code/tutorials#next-steps)
\ No newline at end of file