Full instructions injected when the skill is invoked. Structured as methodology, not rigid rules. Explains why behind every instruction so the model can handle edge cases.
# From the actual Reflect-Code skill body:
## Async/Await Trace (Critical)
For every async function call:
1. Is the call `await`ed?
2. Is the return value used?
3. If missing `await`, trace exact runtime behavior:
- What does Promise object look like used synchronously?
- What happens when you access `.allowed` on pending Promise?
- `!undefined` is `true` — does the conditional pass?
- Write ACTUAL execution path, not intended path
## Attacker Persona (Mandatory Output)
After line-by-line review, answer:
1. "If I wanted unlimited free usage, what would I try?"
2. "If I wanted to use without paying?"
3. "Which identifiers can be rotated, spoofed, omitted?"
4. "Which safety checks exist but aren't called/awaited?"
Why
Theory of mind over rigid MUSTs. LLMs are smart — if you explain why a check matters, the model generalizes to edge cases instead of pattern-matching to specific examples.