All authors
Claude Skills by StudyDrift
github.com/StudyDrift13 skills0 installs18 views
- Dont Trust Me BroSkeptical analysis and critique of claims, plans, and code without taking anyone at face value. Use when the user says "don't trust me", wants adversarial review, red-teaming, assumption checking, or verification that generated or proposed code is actually correct. Triggers on skepticism, critique everything, verify claims, challenge assumptions, red team, devil's advocate, prove it, smell test.Votes: 0GitHub stars: 62
- Fix CiFind failing PR checks, inspect logs or external check links, and apply focused fixesVotes: 0GitHub stars: 62
- Fix Merge ConflictsResolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolutionVotes: 0GitHub stars: 62
- Get Pr CommentsFetch and summarize review comments from the active pull requestVotes: 0GitHub stars: 62
- HowUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.Votes: 0GitHub stars: 62
- ImplementImplements a new planned featureVotes: 0GitHub stars: 62
- Make Interfaces Feel BetterDesign engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.Votes: 0GitHub stars: 62
- Next FeatureUse this when the next feature needs to be implemented.Votes: 0GitHub stars: 62
- Next MobileImplements the next mobile storyVotes: 0GitHub stars: 62
- RequirementsTurns a feature request into a full implementation-plan requirements document matching docs/plan/_TEMPLATE.md. Use when the user asks for requirements, a spec, an implementation plan, or wants to flesh out a feature before building. Also use for /requirements or "write requirements for X".Votes: 0GitHub stars: 62
- WhyUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.Votes: 0GitHub stars: 62
- ImplementImplements a new planned featureVotes: 0GitHub stars: 62
- Next FeatureUse this when the next feature needs to be implemented.Votes: 0GitHub stars: 62