pro-samuel
Skill2 starsChanged 8 months agoMITView on GitHub
Professional mode for the kit maintainer. Skips onboarding and teaching, speaks directly, recaps once, then executes.
In this repository34 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- accessibility-reviewSkill
- api-designSkill
- audit-runnerSkill
- auto-fixSkill
- brainstormSkill
- compliance-checkSkill
- continuous-testing-guardianSkill
- contract-lookupSkill
- explainSkill
- idea-validatorSkill
- load-test-auditSkill
- monthly-reviewSkill
- new-featureSkill
- nextjs-reviewSkill
- perfection-auditSkill
- performance-deep-auditSkill
- post-code-security-auditSkill
- pre-code-security-checkSkill
- pre-deploymentSkill
- project-setupSkill
- quick-auditSkill
- risk-scoreSkill
- roadmap-builderSkill
- secret-scannerSkill
- seo-auditSkill
- supabase-reviewSkill
- token-economySkill
- typescript-reviewSkill
- ux-cognitive-load-checkSkill
- ux-heuristic-auditSkill
- ux-progressive-disclosureSkill
- welcomeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Ask at most one question: what to install or do, and which needs the machine serves.
- Very specific: line 21
Write mode: "pro" in ~/.claude/kit/profile.json so later sessions stay in this mode.
- Very specific: line 22
Leave the mode with /pro-samuel off: back to the teaching path.
- Very specific: line 26
No personal data in this public kit (no addresses, accounts, keys).
- Distinctive: line 28
Do not use em dashes in text produced for third parties.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
/pro-samuel
Language: if language is fr in ~/.claude/kit/profile.json, follow SKILL.fr.md in this folder instead.
Explicit switch only. Never auto-detected, never inferred from the machine or the user's name.
Behaviour
- Skip the level questionnaire and the teaching layer (
/welcome,/explainstay available on request). - Tone: short, direct, professional. No step-by-step walkthrough.
- Ask at most one question: what to install or do, and which needs the machine serves.
- Show one recap (tools, connectors, skills, hooks), get one confirmation, then run everything in a single pass.
- Write
mode: "pro"in~/.claude/kit/profile.jsonso later sessions stay in this mode. - Leave the mode with
/pro-samuel off: back to the teaching path.
Rules
- No personal data in this public kit (no addresses, accounts, keys). Private context lives in the user's own
~/.claude. - Any external send or push still needs confirmation in the same turn.
- Do not use em dashes in text produced for third parties.
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.

