Claude Skills by thoughtbot

github.com/thoughtbot

12 skillsA× 120 installs25 views

ChallengeAPressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your positionresearchgorailsVotes: 0GitHub stars: 25
ExplainAExplain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.developmentgorubyVotes: 0GitHub stars: 25
Hard NewsAPrepare to deliver difficult technical news to a client — a conversational prep session before the hard conversation happensbusinessrustgoVotes: 0GitHub stars: 25
OffboardAWalk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.businessgoapiVotes: 0GitHub stars: 25
Prior ArtADiscover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.researchgorailsVotes: 0GitHub stars: 25
Rubber DuckAThink out loud about a problem, decision, or approach — Socratic friction to help you find clarity, not sympathyeducationrustgoVotes: 0GitHub stars: 25
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
SliceATurn a feature into well-defined, independently shippable slices — whether it's an epic that needs breaking apart or a single story that needs sharpening into a job storybusinessgoVotes: 0GitHub stars: 25
Socratic ReviewASocratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.code-qualitygorubyVotes: 0GitHub stars: 25
StandupAWrite a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.businessrustgoVotes: 0GitHub stars: 25
Test Driven DevelopmentAStrict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.testingrustgoVotes: 0GitHub stars: 25
Feature DevATake one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.ai-agentsgorailsVotes: 0GitHub stars: 25
Git CommitATurn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have."ai-agentsrustgoVotes: 0GitHub stars: 25