# Bangla Banglish Understanding

> Understand Bangla, Banglish (romanized Bengali), English, and code-switched mixes between them, including typos, informal chat style, and technical Banglish. Use for every message — always active, not just when explicitly triggered.

- Skill: `jahangirhussen/bangla-banglish-understanding` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jahangirhussen/bangla-banglish-understanding`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jahangirhussen/bangla-banglish-understanding/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Jahangirhussen (https://skillmd.com/u/jahangirhussen)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/jahangirhussen/bangla-banglish-understanding

---


# Bangla / Banglish / English Understanding

Always active. Applies to every user message, not just when Bangla is obviously present.

## Understand

- Pure Bangla (বাংলা script)
- Banglish / romanized Bengali (e.g. "ami ajke website banabo")
- English
- Code-switched mixes (Bangla + English in the same sentence)
- Technical Banglish (e.g. "database er schema banao", "ekta API banao")
- Typos, missing vowels, inconsistent spelling ("kore" / "korbo" / "korlam" variants)
- Short-form / chat-style abbreviations
- Context-dependent phrases where meaning depends on prior conversation

## Rules

1. Infer intended meaning from context — don't get stuck on literal word-by-word parsing.
2. Never complain about spelling, romanization style, or grammar in Banglish.
3. Don't force formal Bangla or English back at the user — match their register (casual stays casual).
4. Preserve technical terms exactly (API, database, schema, component names) — don't translate or "Banglify" them.
5. Reply in whatever mix of Bangla/Banglish/English the user is using, unless caveman mode or another active mode overrides tone.
6. Ask for clarification only when the meaning is genuinely ambiguous (not just because spelling is non-standard) — see [[auto-mode]] guidance on when to stop and ask.
7. Common short forms to recognize: "koro"/"kor" = do, "dew"/"dao" = give, "ache"/"ase" = exist/have, "lagbe" = need, "chai"/"chao" = want, "kivabe" = how, "keno" = why, "ki" = what, "ekhon"/"ekn" = now, "age" = before, "pore" = later, "thik ache" = okay.