My Claude Code Setup on Windows

I find Claude Code repeatedly trying to use wrong commands so i wrote this Claude.md ay user level in ~/ to guide it. use it based on your needs.

# User Environment Configuration

## Platform Information
- **Operating System**: Windows
- **Shell**: PowerShell (not Linux/Mac terminal)
- **Command Style**: Use PowerShell cmdlets and Windows commands

## PowerShell Command Discovery

### Listing Available Commands
- `Get-Command` - Lists all available cmdlets, functions, aliases, and applications
- `Get-Command | Out-GridView` - Searchable GUI for all commands
- `Get-Command Get-*` - Filter commands starting with 'Get-'
- `Get-Module -ListAvailable` - Lists all installed modules
- `Get-Command -Module <ModuleName>` - Lists commands from specific module
- `Get-Command -Type Application` - Lists traditional Windows commands (ipconfig, dir, etc.)

### Getting Help
- `Get-Help <command-name>` - Basic command help
- `Get-Help <command-name> -Detailed` - Detailed help with examples
- `Get-Help <command-name> -Examples` - Just usage examples
- `Get-Help <command-name> -Online` - Opens web documentation
- `Update-Help` - Updates local help files (may require admin)

## Windows Tool Alternatives

### JSON Handling
- Use `ConvertFrom-Json` and `ConvertTo-Json` instead of `jq`
- If `jq` needed: `winget install jq`
- Alternative: Enable WSL for Linux tool compatibility

### Common Commands
- Use `dir` or `Get-ChildItem` instead of `ls`
- Use `type` or `Get-Content` instead of `cat`
- Use `where` or `Get-Command` instead of `which`

## Reference Resources
- [PowerShell Cmdlets Documentation](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/?view=powershell-7.4)
- [Windows Commands Reference](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands)
- [PowerShell Community Resources](https://www.pdq.com/powershell/)

## Development Preferences (Inferred from Projects)

### Technology Stack
- **Framework**: Next.js 15+ with App Router pattern
- **React**: Version 19+ (latest stable)
- **TypeScript**: Strict mode enabled, path mapping with `@/*` → `./src/*`
- **Styling**: Tailwind CSS v4 with inline theme configuration
- **Fonts**: Geist Sans and Geist Mono from Google Fonts

### Project Structure Patterns
- **Source Organization**: `src/app/` for pages, `src/components/` for shared components, `src/lib/` for utilities
- **Component Structure**: Separate files for each component, co-locate app-specific components in `src/app/components/`
- **Content Management**: Markdown-based with frontmatter (in `content/` directory)
- **API Routes**: RESTful endpoints in `app/api/` following Next.js conventions

### Code Standards
- **TypeScript Config**: Strict mode, ES2017 target, modern module resolution
- **Import Style**: Use `@/` path mapping for clean imports
- **Component Naming**: PascalCase for components, descriptive names
- **File Extensions**: `.tsx` for React components, `.ts` for utilities

### Development Workflow
- **Dev Server**: Use Turbopack (`npm run dev --turbopack`) for faster development
- **Build Process**: Standard Next.js build pipeline
- **Linting**: ESLint with Next.js configuration (`npm run lint`)

### Styling Approach
- **CSS Variables**: Use for theming (background/foreground with dark mode support)
- **Responsive Design**: Mobile-first approach
- **Theme System**: CSS variables with system preference detection

### Content & Data Patterns
- **Static Content**: Markdown files with frontmatter metadata
- **Data Processing**: Native frontmatter parsing without external dependencies
- **API Design**: JSON endpoints for dynamic data

### SEO & Metadata Practices
- **Metadata**: Comprehensive OpenGraph, structured data, keywords
- **Sitemap**: Dynamic generation for content pages
- **Author Attribution**: Include author information in metadata

## Instructions for Claude Code
When working with this user:
1. Always use PowerShell syntax and cmdlets
2. Prefer native PowerShell commands over Linux equivalents
3. Use `Get-Help` commands to discover available options
4. Suggest Windows-native alternatives for Linux tools
5. Consider WSL when Linux-specific tools are essential
6. Follow Next.js 15+ App Router patterns
7. Use TypeScript strict mode and proper typing
8. Implement responsive, accessible designs with Tailwind CSS
9. Prefer native implementations over external dependencies when possible
10. Always run `npm run lint` after code changes