Prompt-sensei
Reduces iteration cycles on AI prompts by surfacing patterns in what works locally, helping teams standardize effective prompt structures before scaling them…
Local-first prompt coach for Claude Code and Codex that improves prompts, observes prompting habits, and analyzes local history with explicit consent.
- Analyze prompt patterns across local project history to identify reusable templates
- Coach developers on prompt clarity before submitting to production systems
- Track which prompt structures yield higher-quality code generation results
Reduces iteration cycles on AI prompts by surfacing patterns in what works locally, helping teams standardize effective prompt structures before scaling them across the organization.
Development teams using Claude Code who want systematic feedback on prompt quality without shipping data externally.
https://github.com/chengzhongwei/Prompt-sensei
By chengzhongwei
How to Get It
git clone https://github.com/chengzhongwei/Prompt-sensei ~/.claude/skills/prompt-sensei (cd ~/.claude/skills/prompt-sensei && npm install && npm run build) Then run /prompt-sensei observe inside Claude Code.
After installing, paste this into Claude:
Help me analyze prompt patterns across local project history to identify reusable templates
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Reddit
- Rio took one look at Anime Sensei and promptly forgot all of her lines [Aris/Ali — Reddit · 2291 pts
- "Can this Guy be our Sensei instead?" [Prompt] — Reddit · 363 pts
- [prompt] "Sensei, Naruto has a bow and I'm scared." — Reddit · 259 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 107 GitHub stars; 2 contributors; last commit 36d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 107 GitHub stars; 2 contributors; last commit 36d ago; license Apache-2.0.