why
Recover why a Roblox design or implementation exists from project decisions, source history, current code, and authored context.
- License 许可
- MIT
- 最近更新
- 2026-09-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- why
- description
- Recover why a Roblox design or implementation exists from project decisions, source history, current code, and authored context.
02 资源文件 1
- 参考文档agents/openai.yaml193 B
03 SKILL.md 正文
Explain why the Roblox design exists
Build an evidence chain in this order:
- Repository design, architecture, security, authoring, and handoff documents.
- Current source and the constraints visible in its call sites, data shapes, remotes, lifecycle, and tests.
- Git history for the relevant files, commits, and blame lines when the current tree does not preserve the reason.
- Roblox Studio context inspection, or scoped non-playtest fallback edits when Repository mode is unavailable and the task explicitly requires an authored change.
- External sources only when the user asks or the decision depends on current Roblox platform behavior.
Return the decision, supporting evidence, rejected or likely alternatives, current tradeoff, and confidence. Label inference. Do not turn absence of evidence into a confident rationale. Use $how when the question is about runtime behavior rather than motivation. Never use Roblox Studio MCP playtest controls.
04 同仓库更多 Skills
unslop
Cut AI tells from any writing. Must always apply.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use for explicit TDD or when Roblox logic has a cheap deterministic Luau regression target that can fail before the fix.
swarm
Coordinate independent routine execution or exploration batches and return one reviewed report. Use for $swarm or large separable work that justifies parallel overhead.
show-me-your-work
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for $show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.