菜单
Prevent Claude from gaming tests — no hard-coded values, no helper-script workarounds, no solutions that only pass the specific test cases. Use when tests are involved and you want real, generalizable implementations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Make Claude default to implementing changes rather than just suggesting them. Use when the model keeps proposing edits instead of applying them, or when you want a bias toward action in an agentic coding context.
Raise recall in code review — get Claude to report every bug it finds, including low-confidence ones. Use for code review harnesses, security audits, or any workflow where missing a real bug is worse than a few false positives.
Stop Claude from leaving behind temporary scripts, scratch files, and iteration helpers after a task. Use when you want a clean workspace — no extra files beyond the requested deliverables.
Make Claude's responses shorter and more focused. Use when the model is over-explaining, adding non-essential context, or producing verbose answers for simple lookups.
Make Claude ask before taking destructive or hard-to-reverse actions (rm, force-push, dropping tables, posting publicly). Use in autonomous agents that touch shared systems or in any context where the blast radius of a wrong action is high.
Structured, hypothesis-driven research across large corpora. Use for complex research tasks, literature reviews, competitive analysis, or anywhere Claude needs to synthesize information from many sources with tracked confidence.
| name | vojta-no-hardcode |
| description | Prevent Claude from gaming tests — no hard-coded values, no helper-script workarounds, no solutions that only pass the specific test cases. Use when tests are involved and you want real, generalizable implementations. |
Claude sometimes focuses too narrowly on making tests pass, or reaches for helper scripts instead of solving the actual problem. This prompt keeps the solution principled.
Please write a high-quality, general-purpose solution using the standard tools available. Do not create helper scripts or workarounds to accomplish the task more efficiently. Implement a solution that works correctly for all valid inputs, not just the test cases. Do not hard-code values or create solutions that only work for specific test inputs. Instead, implement the actual logic that solves the problem generally.
Focus on understanding the problem requirements and implementing the correct algorithm. Tests are there to verify correctness, not to define the solution. Provide a principled implementation that follows best practices and software design principles.
If the task is unreasonable or infeasible, or if any of the tests are incorrect, please inform me rather than working around them. The solution should be robust, maintainable, and extendable.
If Claude starts writing one-off scripts, branching on specific fixture values, or inlining test expectations — it's optimizing for the test, not the problem. Re-inject this snippet.