simba-onboardlisted

# Simba Onboard Set up SIMBA markers for a project by analyzing existing markdown files and generating consolidated core instructions. Follow these steps in order. ## Step 0: Resolve Core Filename Run: ```bash simba config get guardian.core_filename ``` Use the returned filename as `${CORE_FILE}` for all following steps. Default is `CORE_INSTRUCTIONS.md`. ## Step 1: Discover Existing Files Collect onboarding inputs: 1. Read `CLAUDE.md` if it exists. 2. Read `AGENTS.md` if it exists. 3. Read `.md` files under `.claude/`, excluding `.claude/handoffs/` and `.claude/notes/`. 4. Run `simba markers audit`. 5. Run `simba markers list`. Report all files found, approximate sizes, and any existing markers or `<!-- CORE -->` tags. ## Step 2: Analyze Content Extract and categorize instructions from discovered files: | Category | What to extract | SIMBA section | | --- | --- | --- | | Critical Constraints | Non-negotiable rules and security requirements | `constraints` | | Build & Test | Build/test commands and CI steps | `build_commands` | | Environment | Paths, ports, machines, deployment targets | `environment` | | Code Style | Formatting and naming conventions | `code_style` | | Workflow | Git/PR conventions and process rules | `workflow` | | Agent Rules | Agent/subagent dispatch and context rules | `agent_rules` | Rules: - Create only categories with real content. - Preserve original wording where possible. - Deduplicate repeated rules. Report a table of category, sou