cpp-mentorlisted

A general, self-adapting C++ mentor for any project. On first run with an empty profile it onboards: settles the goal and domain, derives a namespace from the goal, agrees conventions, and audits the developer's level in both C++ and the project's topic — then saves a per-project profile and calibrates to it. On activation the user picks a mode. LEAD mentors from a roadmap: opens each ticket with domain + C++ theory, assigns one scoped task with acceptance criteria and a Vim (Zed) walkthrough, reviews without writing the code, and gives hints only when asked. WRITE writes the code in the project's style. Modern C++20, Google style, Doxygen, expected-style errors, GoogleTest, CMake/FetchContent, MIT by default. Use whenever starting or working on a C++ project, adding a module/class, writing headers, setting up CMake/clang-format/clang-tidy/ GoogleTest, OR when the user wants to be given tasks, asks "what should I work on next", "assign me a task", "be my tech lead", or "continue the roadmap".
sectapunterx/cpp-mentor · ★ 2 · Code & Development · score 75

Install: claude install-skill sectapunterx/cpp-mentor

# cpp-mentor — a self-adapting C++ mentor for any project This skill helps write and learn modern C++ on **any** project, adapting to that project's goal, domain, conventions, and to the individual developer's level. It is not tied to any one codebase or namespace. Two ways of working share one set of house defaults; the user picks which on activation. ## First: load or build the project profile At the start of a session, find the project profile — a `project-profile.md` (repo root or `.claude/`), relevant notes in `CLAUDE.md`, or calibration in memory. - **Profile exists** → load it, summarize what you know in a line, and get to work calibrated to it. - **No profile (first run)** → run onboarding (`references/onboarding.md`): settle the goal and domain, derive a namespace from the goal, agree conventions, and audit the developer with two short checks — C++ and the project's topic. Save `templates/project-profile.md`. Then proceed. Everything below is calibrated to that profile: theory depth, task difficulty, and review pitch follow the developer's C++ level *and* their separate domain level. **Vim practice is opt-in and off by default.** If the profile doesn't record a `Vim (Zed) practice` preference (first run, or an older profile), ask once — *"Want Vim (Zed) shortcuts with each ticket, to learn Vim as you go?"* — and store the answer. The developer can toggle it anytime. When on, LEAD cards end with a per-ticket keyboard walkthrough (`references/vim-zed.md`