plugins/khuym/skills/xia/SKILL.md
Research-first feature discovery for unfamiliar, ambiguous, or high-risk implementation work. Use when Codex should map the real repo stack, find reusable local code, check upstream patterns, and verify current official docs before planning or implementing a feature.
npx skillsauth add hoangnb24/skills xiaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Xia is the anti-reinvention scout. Use it before unfamiliar, ambiguous, version-sensitive, or high-risk implementation work when a research brief should come before planning or code.
Do not write code or edit files until the research brief is complete, unless the user explicitly waives research or directly asks for immediate implementation.
If two viable paths differ materially in behavior, risk, or migration cost, finish the brief and ask one targeted question instead of guessing.
Quick: low-risk questions with an obvious local seam.Standard: default; map repo, search local reuse, check upstream patterns, check current official docs.Deep: cross-cutting, version-sensitive, or architecture-heavy work.If unsure, use Standard.
references/research-brief-template.md.Load references/xia-protocol.md for stack-ledger guidance, local reuse targets, DeepWiki/Exa roles, recommendation rules, follow-up question criteria, and red flags.
Every non-trivial claim in the brief must be labeled:
Local for findings from this repositoryUpstream for public GitHub repository patternsDocs for official documentationInference for conclusions drawn from evidenceDo not blur these categories.
Choose the lightest credible path:
Explain why the chosen path beats the next-best alternative.
| File | When to Load |
|---|---|
| references/xia-protocol.md | Detailed research flow, tool roles, guardrails |
| references/research-brief-template.md | Required brief structure |
| references/pressure-scenarios.md | RED/GREEN validation scenarios |
tools
Use when the user asks to commit everything, smart commit, group commits, organize staged or unstaged changes, create logical commits, push current work, or preserve a clean commit stack from an existing working tree.
development
Use when starting or resuming any Khuym project session, choosing the next Khuym skill, running go mode, checking onboarding/scout state, or enforcing workflow gates. Bootstrap meta-skill for routing across the Khuym agentic development ecosystem.
development
Use when the user wants to turn a rough idea, vague task, feature wish, bug-fix intent, or Codex /goal objective into a clear verifiable goal prompt. Use when the user mentions goal mode, /goal, set_goal, long-running autonomous Codex work, or asks to be interviewed/grilled before creating a goal.
tools
Use when Codex should turn a concept, topic, tutorial, lesson, algorithm, system, workflow, or abstract idea into a playable browser game that teaches through interaction. Use for planning or implementing educational web games with the Game Studio plugin, including concept-to-mechanic translation, gameplay loop design, learning progression, and browser-game QA.