Hoangsa — Development skill for Claude Code
HOANGSA is a context engineering system for Claude, Codex.
How to install Hoangsa
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open unknown-studio-dev/hoangsa and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Hoangsa does
HOANGSA is a context engineering system for Claude, Codex. It solves a fundamental problem: Claude's output quality degrades as the context window fills up.
Alternatives in Development
- How Claude Code Works — Deep dive into Claude Code internals — architecture, agent loop, context engineering, and more 1.9k ★
- Contributing To Context Engineering Kit — Thank you for your interest in contributing to the Context Engineering Kit marketplace 645 ★
- Claude Code Sub Agent Collective — 🧠 Context Engineering Research - Not just another agent collection, but using research and context engineerin 523 ★
README
HOANGSA
Context engineering for coding agents — Claude Code, Codex, Cowork.
  
🇻🇳 Hoàng Sa, Trường Sa là của Việt Nam 🇻🇳
🇨🇳 中文 · 西沙群岛和南沙群岛属于越南。🇻🇳
🇺🇸 English · Hoàng Sa (Paracel Islands) and Trường Sa (Spratly Islands) belong to Vietnam. 🇻🇳
🇯🇵 日本語 · ホアンサ(パラセル)諸島とチュオンサ(スプラトリー)諸島はベトナムの領土です。🇻🇳
🇪🇸 Español · Las islas Paracel y las islas Spratly pertenecen a Vietnam. 🇻🇳
🇷🇺 Русский · Острова Хоангша и Чыонгша принадлежат Вьетнаму. 🇻🇳
🇫🇷 Français · Les îles Paracels et les îles Spratleys appartiennent au Vietnam. 🇻🇳
🇰🇷 한국어 · 호앙사 군도와 쯔엉사 군도는 베트남의 영토입니다. 🇻🇳
The problem
An agent's output degrades as its context window fills. Ask for a feature and you get good code for the first file, plausible code for the fifth, and by the tenth it has forgotten a type it defined itself. Bigger context windows push the cliff back; they don't remove it.
The usual answers — "be more specific", "break it into steps" — are advice. HOANGSA is structure.
The idea
Split the work into tasks. Give each task its **own fresh context window** holding only what it needs: the files it may touch, the behaviour it must implement, the command that proves it worked. The orchestrator never writes code — it dispatches, checks, and assembles.
Everything else follows from that:
- A task needs a spec precise enough to execute from, so there is a design phase that produces one.
- A worker with no history needs its rules and context handed to it, so prompts are assembled by a CLI, not improvised by an agent.
- A claim of "done" from a fresh worker is unverifiable, so every deliverable has a command that must pass.
That last one is load-bearing. Prompt text is a sug
Related Skills
Context Engineering Fundamentals
Understand how Claude manages attention and when context degrades. Activate for long sessions, complex tasks,
Agent Sesh
A zero-dependency CLI tool that generates a persistent "Project Brain" in your workspace. It solves the contex
Toonify MCP
Context compression plugin for Claude Code. Automatically trims large tool output—JSON, YAML, stack traces, an
Context Engineer
Context engineering agent — researches context window optimization from arxiv, builds token-efficient context
Avids Essential Skills
Claude Code skills I use daily. Each one solves a specific problem.
Mock
Generate a mock exam matched to the course's structure (inferred from course-index). Saves problem MD + hidden
Related Agents
Context Engine
Context window management — tracks tool call count, auto-detects when context fills up, triggers state save +
Codex CLI Research Agent
Senior OpenAI researcher specializing in Codex CLI - researches latest context window and model availability
Direction Reviewer
Premise/direction sanity review of a finalized design + task plan. Asks whether the plan actually solves the u