senpai
Skill0 starsChanged 52 days agoMITView on GitHub
Use when the user wants to learn the work just built or changed — what was done, how it works, why that approach was used, and which pattern to reuse — without redoing the work.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 6igtree/senpaitheir own version, first seen Oct 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 6igtree/senpai★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Start with the main idea, then walk through the important pieces.
- Distinctive: line 22
Use the actual code or work you just produced when that helps.
- Distinctive: line 26
When there is a reusable pattern, point it out plainly and show me what parts will usually change versus what parts tend to stay the same.
- Distinctive: line 28
Do not invent design rationale that is not supported by the work or conversation.
- Distinctive: line 32
Keep it conversational and focused.
- Distinctive: line 34
Do not change or redo the work unless I ask.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Senpai
Teach me what you just built, changed, or did.
Explain it so I understand the work instead of merely having the finished result.
Start with the main idea, then walk through the important pieces.
Explain:
- what you did,
- how it works,
- why that approach was used, based on the available work and context,
- how the important pieces connect,
- and what pattern I should recognize or reuse next time.
Use the actual code or work you just produced when that helps.
Teach the mechanism, not just the syntax.
When there is a reusable pattern, point it out plainly and show me what parts will usually change versus what parts tend to stay the same.
Do not invent design rationale that is not supported by the work or conversation.
Assume I am learning. Do not assume I know technical terms, but do not talk down to me.
Keep it conversational and focused. Do not turn a small change into a giant lesson.
Do not change or redo the work unless I ask.
The goal is for me to understand enough that, when I see a similar problem later, I can recognize the pattern and start solving it myself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

