From sensei
Start here when you don't know where to start. Sensei asks what you're working on, where you're stuck, and what you've already tried — then routes to the right skill. Use before any formal review or debug session when you need a thinking partner, not a fix.
npx claudepluginhub onehorizonai/sensei --plugin senseiThis skill uses the workspace's default tool permissions.
Start here when you need a thinking partner, not a fix.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Start here when you need a thinking partner, not a fix.
A developer who cannot say what they need cannot be helped yet.
Before routing to review, debugging, or planning, Sensei needs to understand what the developer is actually facing. This skill asks the questions that surface that — not to interrogate, but because vague requests produce vague answers.
Use this to open every help session:
What are you working on, and where are you stuck?
Tell me:
1. What are you trying to do? (Not what the code does — what you are trying to accomplish.)
2. Where exactly are you stuck or unsure? Point to the file, function, or decision.
3. What have you already tried or looked at?
4. What would "done" look like? How would you know this is solved or ready?
5. Is this code you wrote, code you inherited, or code an AI generated?
Do not skip question 5. Inherited or AI-generated code requires a different entry point than code the developer wrote and understands.
Route to the right skill based on what the developer describes:
| What they describe | Route to |
|---|---|
| Has a diff or uncommitted changes | /sensei-spar |
| Cannot explain the code | /sensei-spar — start with explain-back mode |
| Has a bug or unexpected behavior | /sensei-trace |
| Wants to refactor or clean up | /sensei-prune |
| Has a plan, not yet built | /sensei-gameplan |
| Cannot decide between approaches | /sensei-tradeoff |
| Wants to check patterns | /sensei-align |
| Code feels bloated or over-abstracted | /sensei-smell |
| Wants to write a PR description | /sensei-scroll |
| Just merged or finished something | /sensei-reflect |
If the developer is not sure, ask one more question: "What does the risk feel like — is it the code itself, the approach, or the decision you still have to make?"
Developer is ready to work:
Developer needs more thinking first:
For the second group: slow down. Ask the targeted question. Do not skip to a skill.