analyzer

# Codebase Analysis Skill

## Overview

Analyze a TypeScript codebase to produce a reconstruction-grade Intermediate Representation (IR) containing domain-level business logic. The IR enables accurate migration to Rust WASM components.

---

## Arguments

1. **TypeScript Source** (`$ARGUMENTS[0]`): Path to the TypeScript source codebase
2. **IR Output Path** (`$ARGUMENTS[1]`): Output path for the IR file (e.g., `./ir/component.ir.md`)

---

## Required Permissions

⚠️ **RECOMMENDED**: For seamless execution, request `required_permissions: ["all"]` on the first Shell command to avoid multiple permission prompts during file analysis.

---

## Principles (Non-Negotiable)

1. **Focus**: Extract only domain/business logic and its inputs/outputs. Exclude infrastructure unless part of a domain rule.
2. **Descriptive, not interpretive**: Produce algorithmic descriptions of what the code does. Do not infer "why" unless present in source.
3. **Zero inference**: Do not invent behavior or semantics. Use explicit `unknown` tokens.
4. **Explicit constants**: List every constant by identifier and semantic availability.
5. **Traceability**: Each statement must be traceable to code. Do not attribute intent not in comments.
6. **Tagging**: Each Business Logic line must include one tag: `[domain]`, `[infrastructure]`, `[mechanical]`, or `[unknown]`.
7. **Conservatism**: Prefer `unknown` over guessing.

---

## Tags

| Tag | Description |
| ----- | ------------- |
| `[domain]` | Business logic semantics explicitly domain-related |
| `[infrastructure]` | Operational code visible in source |
| `[mechanical]` | Deterministic computation visible in source |
| `[unknown]` | Behavior or meaning cannot be deduced |

---

## Unknown Tokens (Use Exactly)

- `unknown — not present in source`
- `unknown — referenced symbol defined outside repo`
- `unknown — ambiguous control flow`
- `unknown — semantics not documented in source comments or code`

---

## Process

### Step 1: Identify Component St