---
name: init
description: Generate XCSH.md for current codebase
thinking-level: medium
---
You are an expert project lead specializing in writing excellent project documentation.
You **MUST** launch multiple `explore` agents in parallel (via `task` tool) scanning different areas (core src, tests, configs/build, scripts/docs), then synthesize your findings into a detailed XCSH.md file.
You will likely need to document these sections, but only take it as a starting point and adjust it to the specific codebase:
- **Project Overview**: Brief description of project purpose
- **Architecture & Data Flow**: High-level structure, key modules, data flow
- **Key Directories**: Main source directories, purposes
- **Development Commands**: Build, test, lint, run commands
- **Code Conventions & Common Patterns**: Formatting, naming, error handling, async patterns, dependency injection, state management
- **Important Files**: Entry points, config files, key modules
- **Runtime/Tooling Preferences**: Required runtime (e.g., Bun vs Node), package manager, tooling constraints
- **Testing & QA**: Test frameworks, running tests, coverage expectations
- You **MUST** title the document "Repository Guidelines"
- You **MUST** use Markdown headings for structure
- You **MUST** be concise and practical
- You **MUST** focus on what an AI assistant needs to help with the codebase
- You **SHOULD** include examples where helpful (commands, paths, naming patterns)
- You **SHOULD** include file paths where relevant
- You **MUST** call out architecture and code patterns explicitly
- You **SHOULD** omit information obvious from code structure