smithery/spences10

advanced-prompting

High-leverage prompts that challenge Claude's defaults. Use for \"grill me\", \"prove it works\", \"scrap this\", \"what would 10x engineer do\", \"find ways this fails\".

Installation

$ npx skills add smithery/spences10 --skill advanced-prompting

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/spences10 · top by installs.

npx skills add smithery/spences10

Browse all from smithery/spences10

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,072 B
  • docs SUMMARY.md 187 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Advanced Prompting Patterns

Quick Start

Use these when Claude's first response feels safe/generic:

  1. Challenge - "Grill me on these changes"
  2. Verify - "Prove to me this works"
  3. Reset - "Scrap this and implement the elegant solution"

Pattern Categories

Challenge Prompts

Force Claude to critique rather than accept:

  • "Grill me on these changes" - Get pushback on your approach
  • "What would a 10x engineer do differently" - Surface better patterns
  • "Find 3 ways this could fail" - Adversarial review

Verification Prompts

Demand evidence over assertions:

  • "Prove to me this works" - Request test output, diffs
  • "Show me the before/after" - Force concrete comparison
  • "Walk through this line by line" - Prevent hand-waving

Reset Prompts

Break out of local optima:

  • "Scrap this and implement the elegant solution" - Fresh approach
  • "You're overcomplicating this" - Simplification pressure
  • "What's the 80/20 version" - Cut scope ruthlessly

When to Use

Situation Prompt Pattern
Code review feels shallow Challenge prompts
Implementation seems fragile Verification prompts
Solution feels hacky Reset prompts
Claude is agreeing too readily "Push back on this"

Anti-Patterns

  • Don't use reset prompts mid-implementation (waste tokens)
  • Challenge prompts need context (share the code first)
  • Verification prompts pointless for trivial changes

References

  • [challenge-prompts.md](references/challenge-prompts.md) - Critique and adversarial review
  • [verification-prompts.md](references/verification-prompts.md) - Evidence and proof patterns
  • [reset-prompts.md](references/reset-prompts.md) - Fresh starts and simplification