Claude Coding with Jules White

When using Claude Code, what is the role of the Claude.md file and where should it reside? -------------------------------------------------------------------- I don't have specific information about a Claude.md file or its role in Claude Code from what I know about the product. Since Claude Code is still in research preview, there may be documentation files, configuration files, or project-specific files that I'm not familiar with. For accurate information about: The purpose and role of Claude.md files Where they should be located in your project structure How Claude Code uses them Any specific formatting or content requirements I'd recommend checking: Anthropic's blog post about Claude Code for implementation details The documentation at https://docs.anthropic.com Any README or setup instructions that come with Claude Code Since this is a tool-specific question about a product in research preview, the official documentation will have the most current and...

NOTE : click on the code sections to copy ( Save this as .claude/commands/parallel-work.md) I want to develop features in parallel for my expense tracker app using Git worktrees: $ARGUMENTS Think about how to divide the work up into separate features unless this has been clearly explained already. Please help me set up the worktree environment: 1. For each feature mentioned, create a worktree at ../expense-tracker-[feature-name] with branch feature/[feature-name] 2. Set up the development environment in each worktree 3. List all worktrees to confirm they were created 4. Explain what each worktree will contain and how they're isolated I want to be able to work on all features simultaneously without conflicts. That's for creation. When you're done: (Save this as .claude/commands/integrate-parallel-work.md) I have features developed in parallel worktrees that I need to integrate: $ARGUM...

https://github.com/juleswhite/claude-code

# Project: DataValidator - Python Data Validation Library ## Library Design Principles - **API Design**: Simple, intuitive, and Pythonic - **Dependencies**: Minimal external dependencies - **Compatibility**: Python 3.8+ support - **Performance**: Optimize for speed and memory efficiency - **Documentation**: Comprehensive with examples ## Development Workflow 1. Create feature branch: `feature-[functionality]` or `fix-[issue-number]` 2. Write tests first (TDD approach) 3. Ensure 100% test coverage for new code 4. Update documentation and examples 5. Run full test suite across Python versions: `tox` 6. Update CHANGELOG.md with clear user-facing description ## Code Quality Standards - Follow PEP 8 with line length limit of 88 characters - Use type hints for all public APIs - Docstrings required for all public functions/classes (Google style) - Use dataclasses or Pydantic for structured data - Implement proper error handling with custom exceptions ## Project Structure - `/src/datavalidator...

 # Project: FitnessTracker Mobile App ## Platform Requirements - **Framework**: React Native 0.72+ with TypeScript - **State Management**: Redux Toolkit with RTK Query - **Navigation**: React Navigation v6 - **UI Library**: Native Base for consistent design - **Platform Support**: iOS 14+ and Android API 24+ ## Branch Strategy 1. Create feature branches: `mobile-[feature-name]` 2. Use conventional commits: `feat:`, `fix:`, `refactor:`, etc. 3. Test on both iOS and Android before committing 4. Run `npm run lint` and `npm run type-check` before commits ## Code Organization - **Screens**: `/src/screens/[FeatureName]/[ScreenName]Screen.tsx` - **Components**: `/src/components/[ComponentName]/index.tsx` - **Navigation**: `/src/navigation/[NavigatorName]Navigator.tsx` - **Services**: `/src/services/[serviceName].ts` - **Store**: `/src/store/slices/[featureName]Slice.ts` ## Mobile-Specific Standards - Use React Native's built-in components before third-party libraries - Implement proper er...

# Project: Customer Analytics Pipeline ## Development Standards - **Language**: Python 3.11+ - **Code Style**: Follow PEP 8 strictly, use Black for formatting - **Type Hints**: Required for all function signatures and class definitions - **Documentation**: Docstrings required for all public functions and classes ## Workflow Requirements 1. Create feature branch: `analysis-[description]` or `model-[description]` 2. Write unit tests for all data processing functions 3. Run `pytest` and ensure all tests pass 4. Run `black .` and `flake8` before committing 5. Update relevant documentation in `/docs` if adding new features ## Project Structure - `/src/data`: Data ingestion and preprocessing modules - `/src/models`: ML model definitions and training scripts   - `/src/analysis`: Exploratory analysis notebooks and scripts - `/src/utils`: Shared utility functions - `/tests`: Comprehensive test suite - `/configs`: Configuration files for different environments ## Data Handling Standards...

# Project: TaskFlow Web Application ## Core Principles **IMPORTANT**: Whenever you write code, it MUST follow SOLID design principles. Never write code that violates these principles. If you do, you will be asked to refactor it. ## Development Workflow 1. Before making any changes, create and checkout a feature branch named `feature-[brief-description]` 2. Write comprehensive tests for all new functionality 3. Compile code and run all tests before committing 4. Write detailed commit messages explaining the changes and rationale 5. Commit all changes to the feature branch ## Architecture Overview - **Frontend**: Next.js 14 with TypeScript and Tailwind CSS - **State Management**: Zustand for client state, React Query for server state - **Backend**: Node.js with Express and Prisma ORM - **Database**: PostgreSQL - **Testing**: Jest for unit tests, Playwright for E2E ## Code Standards - Use TypeScript for all new code with strict type checking - Follow the existing component structure in `/...

After introducing Chat (with Claude) + Craft + Scale.. Core Functionality Requirements API Endpoint Structure RESTful HTTP API with clear resource-based endpoints Support for both synchronous and asynchronous execution modes Standardized request/response formats (J SON) Version-controlled API endpoints (e.g., /v1/execute, /v1/tasks ) Execution Capabilities Execute arbitrary code tasks via HTTP requests Support for multi-step coding workflows Handle file uploads and downloads for code projects Stream real-time execution logs and progress updates Support for long-running tasks with proper timeout handling Authentication & Security Access Control API key-based authentication Rate limiting per API key Request size limits and execution time limits Sandboxed execution environment isolation Input validation and sanitization Security Boundaries Restrict file system access to designated directories Network access controls for executed code...