All authors
Claude Skills by ronbronstein
github.com/ronbronstein22 skills0 installs41 views
- BlindspotOld name of lets-find-gaps. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- CatchupOld name of lets-catch-up. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- CheckupOld name of lets-check. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- DirectionsOld name of lets-explore. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- Lets AlignUse when you need answers or decisions from the user — a fuzzy ask, a plan's open decisions, or many choices at once. Asks up to 3 questions in chat, one at a time; for more, builds a local review page and reads the answers back. Triggers: "interview me", "what do you need from me", "give me the decisions", "let's align".Votes: 0GitHub stars: 3
- Lets Catch UpUse to get the user back up to speed mid-project — where we are, what was decided, what's next — so they don't lose the thread. Trigger when the user returns to a task, seems lost, or asks to be caught up or re-oriented.Votes: 0GitHub stars: 3
- Lets CheckUse to audit a Claude Code setup for context-engineering problems — what actually loads, what shadows what, what silently never fires, and what contradicts what. Covers rules (CLAUDE.md), skills, slash commands, and hooks. Trigger on "check my setup," "audit my config," "what's actually loaded," "why isn't my skill firing," "checkup," or right after installing or upgrading the harness.Votes: 0GitHub stars: 3
- Lets ExplainExplain a change that landed, in the user's own language level, with a diagram or a local page when that makes it clearer, then check that the user understands it with a short quiz. For when a change is done and the user wants to understand it before they accept or merge it.Votes: 0GitHub stars: 3
- Lets ExploreUse to explore several genuinely different directions before committing to one — the divergent option-space pass, the opposite of converging on a single design. Trigger when the user wants options, isn't sure of the approach, or asks to brainstorm directions before deciding.Votes: 0GitHub stars: 3
- Lets Find GapsUse before starting in an unfamiliar area to surface the user's unknown unknowns and teach the essentials. Trigger when the user is entering new territory, says they don't know much about something, or asks for a "blindspot pass" or help finding what they don't know they don't know.Votes: 0GitHub stars: 3
- Lets Look BackUse to find and recall what happened in earlier Claude Code sessions of this project — what was decided, said, or tried, and when — and to reopen the right session. Trigger on "what did we decide about X," "when did we…," "find the session where…," "we talked about this before," "look back," or when the user refers to earlier work that the project's records do not explain.Votes: 0GitHub stars: 3
- Lets Set UpUse to install, personalize, upgrade, or repair the Don't Run Off harness — writing the method and the user's profile into their CLAUDE.md. Trigger on "set up the harness," "install don't run off," "personalize my CLAUDE.md," "upgrade the harness," or the first run after installing the plugin.Votes: 0GitHub stars: 3
- Lets ShapeUse when deciding whether or what to build or do, sizing or scoping work, shaping an idea into phased slices, or prioritizing. This is the judgment that comes before execution — is this worth doing, how big is it really, how should it be phased. Trigger on "what should I build/do next," "is this worth it," "how big is this," "scope this," "plan this," "prioritize," "phase this," or before committing to any non-trivial piece of work.Votes: 0GitHub stars: 3
- Lets StartUse at the very start of a work session to orient and route before doing anything. Reads where things stand — recent history, open tasks, project status — names the session type, and picks the right next move. Trigger on "let's start," "begin," "what should we do today," or the first substantive message of a session on a new or existing project.Votes: 0GitHub stars: 3
- Lets TrackUse for all task-tracking work in any task tool — Taskwarrior, GitHub Issues, Linear, Jira, a to-do file, or none — adding, listing, starting, parking, completing, or noting tasks; "what's next here," "add a task," "mark X done," "park this." Also use to connect a repo or a new tool ("track this project," "we use <tool> for tasks"). Reads My setup for the tool and opens only that tool's guide.Votes: 0GitHub stars: 3
- Lets WrapUse when ending or pausing a work session — "let's wrap up," "I'm stopping for today," "end the session," "save where we are," "that's it for now." Closes a session cleanly so nothing is lost, and leaves the project's record files accurate so the next session starts instantly. The bookend to starting a session.Votes: 0GitHub stars: 3
- QuizOld name of lets-explain. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- SetupOld name of lets-set-up. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- ShapingOld name of lets-shape. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- StartOld name of lets-start. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- TaskwarriorOld name of lets-track. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3
- Wrap SessionOld name of lets-wrap. Kept for one release so that typed habits still work; it points to the new name.Votes: 0GitHub stars: 3