All authors
Claude Skills by ayberkcansever
github.com/ayberkcansever9 skills2 installs32 views
- LearnLearn a tech topic to a correct 101 level in minimal time. Researches open sources (official docs/releases, engineering blogs, YouTube talks, HN/Reddit, news, papers) restricted to recent material, then produces a brief with a 101 mental model, what changed, tradeoffs, an adopt/trial/hold/avoid verdict, a time-budgeted learn-it-fast resource path, adjacent topics, and a proposed hands-on PoC lab (scaffolded on request; code ships complete, the user predicts, runs, observes and explains back, ...Votes: 0GitHub stars: 2
- Tech RadarBuilds a Thoughtworks-style learning radar of what a principal software + AI engineer should learn next — crawl registry feeds, triage, confirm adoption, place Learn/Try/Watch/Skip blips, save dated HTML. Use when the user asks what to learn, scan the radar, recent topics worth learning, what is moving in tech, or wants learning recommendations without naming a topic. Not for briefing a named topic — that is the learn skill.Votes: 0GitHub stars: 2
- BrainstormUse when the user explicitly asks for brainstorming, pre-ticket discovery, fuzzy product shaping, visual option exploration, or turning an idea into an approved design before implementation planning.Votes: 0GitHub stars: 2
- Execute PlanImplement a written plan (from write-plan or interview-plan). Use when the user says execute or implement the plan. Runs the review gate itself. Do not use while still interviewing or writing the plan.Votes: 0GitHub stars: 2
- Git WorktreesSet up or reuse an isolated git worktree for a ticket so the current checkout stays untouched. Use when the user asks for a worktree; execute-plan calls it when the checkout is not already on the ticket branch (consent implied there).Votes: 0GitHub stars: 2
- Graph RetroPost-merge retrospective on the SDLC skill chain itself, from one ticket's artifacts. Use after merge and deploy, when the user says "retro this ticket", or when an escaped defect traces to an old ticket. Do not run as the next step after execute-plan or the review.Votes: 0GitHub stars: 2
- Interview PlanInterview the user into an ambiguity-free spec and implementation plan. Use only when the user explicitly invokes "interview-plan" or asks to "interview me" / "stress-test the plan" about a plan or design. Runs write-plan itself — do not also invoke /write-plan.Votes: 0GitHub stars: 2
- Thermo Nuclear Code Quality ReviewStrict branch-diff review against the ticket spec. Use after a dev session, before a PR, or when the user asks to review the branch. execute-plan runs it as its review gate — do not also invoke it unless code changed after `Verdict: ship`.Votes: 0GitHub stars: 2
- Write PlanWrite an implementation plan from a spec before touching code. Use when the user invokes write-plan with an existing spec and no interview, or when interview-plan hands off an assembled spec. Do not use to implement.Votes: 0GitHub stars: 2