Claude Skills by gwpicard

github.com/gwpicard

40 skillsA× 39B× 10 installs4 views

Review IssuesARead every open issue in this repository, group them by theme, and name the best next piece to pick up. For a maintainer deciding what to work on. Reports only; it never edits an issue or applies a label. Load it by its path when you want it.developmentgogitVotes: 0GitHub stars: 2
Stack ResearchARead what has changed upstream for every product the kit's recipes name, and what tools that build apps with AI now produce by default, then write a dated note proposing a change to each recipe and part, or none. For a maintainer keeping the recipe menu current. Proposes only; it changes nothing in the kit. Load it by its path when you want it.developmentgogitVotes: 0GitHub stars: 2
RunABuilds the ready pieces with the selected Claude Code or Codex backend; the gate runs the judge; a pass opens a pull request for the person. Use when pieces are ready and the person wants them built.developmentpythongoVotes: 0GitHub stars: 2
SetupBPrepares a project for the loop. Runs the kit's own checks, agrees how the project prepares and tests itself, and records both in AGENTS.md. Use once per project, before the first shape, and again when a check fails.developmentpythongoVotes: 0GitHub stars: 2
ShapeATurns an idea into a piece the gate accepts as ready - a GitHub issue with numbered Contract items and a judge that fails on main. Use when the person describes work to build or brings a rough idea.developmentpythongoVotes: 0GitHub stars: 2
Review IssuesARead every open issue in this repository, group them by theme, and name the best next piece to pick up. For a maintainer deciding what to work on. Reports only; it never edits an issue or applies a label. Load it by its path when you want it.developmentgogitVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Review Public DocsAReview the shipped prose, site pages and release notes before a release. Load by path.developmentVotes: 0GitHub stars: 2
Stack ResearchARead what has changed upstream for every product the kit's recipes name, and what tools that build apps with AI now produce by default, then write a dated note proposing a change to each recipe and part, or none. For a maintainer keeping the recipe menu current. Proposes only; it changes nothing in the kit. Load it by its path when you want it.developmentgonextjsVotes: 0GitHub stars: 2
Build PieceABuild one ready piece to a confirmed, saved change, from the safe start to the updated records. Used by implement for every piece, a repair included, and by the builder agent. Refuses to start on top of uncommitted work. One piece per pass, always.developmentgitdatabaseVotes: 0GitHub stars: 2
ClarifyAInterview the team before work is specified, one question at a time, each with a best guess attached. Used by setup-ai-build-kit for the founding interview and by shape when a request is too vague to size. Do not use for small clear changes or for repairs, and never write code during it.developmentgotestingVotes: 0GitHub stars: 2
Evidence RunAGather fresh evidence before the tool is relied on: promised behaviour, failure, data and access, operations, review, and an honest report. Used by setup-hosting, maintain and merge.developmentgoVotes: 0GitHub stars: 2
Fit CheckAFill the project's risk record, name each risk area with its caution, and give the risk notice where one is due. Used at founding, when a request changes the project, before hosting, at the quarterly visit, and when a repair stalls.developmentgoVotes: 0GitHub stars: 2
ImplementABuild ready pieces. Typed alone, take one free or ask which. Given a piece, request or "auto", follow its route; it does not shape.developmentpythongoVotes: 0GitHub stars: 2
Live CopyAWork with the live copy safely. Pass a secret a check needs by its location, ask before any change to a live service, and roll back to an earlier version on a yes. Used by setup-hosting, maintain, merge, repair and what-now.developmentdatabaseVotes: 0GitHub stars: 2
MaintainAMake the project true and healthy. Every visit checks records and the live copy. Monthly and quarterly work runs only when due. Use after outside work, before a handover, after time away, or when retiring a tool. A session that died part-way goes to what-now first. Do not use for building, repairing or planning.developmentpythongoVotes: 0GitHub stars: 2
MergeATake a finished piece to main. The first upload and, by default, each merge wait for a yes. Used by implement, setup-hosting, maintain and founding.developmentpythongoVotes: 0GitHub stars: 2
Quality ChecksARun the kit's quality reads by script and act on their exit codes. The reach check, the trim, test strength, the check floor, boundary rules, and the structure, waste, document and old-branch reads.developmentpythonrustVotes: 0GitHub stars: 2
RecordsAWrite and keep the project's records true. A piece and its labels, the printout, a piece's change to the masterplan and its checked mark, the coverage read, and the records a finished build updates. Used by every command.developmentgitVotes: 0GitHub stars: 2
RepairAReproduce a fault, then fix one cause at a time, with the risk notice after three failed attempts. Used by shape to reproduce a fault and by implement to build the repair.developmentapiVotes: 0GitHub stars: 2
ResearchACheck one outside fact against its primary source, or search for existing work before anything new is built. Used by shape, clarify and a build, and by the researcher agent.developmentgoapiVotes: 0GitHub stars: 2
Screen CheckAApply the kit's screen rules during a build or review that touches an interface. Read the project's own design system first, report what was applied and what remains for a person to try, and make no claim that the screen is accessible, compliant, or good.developmentgogitVotes: 0GitHub stars: 2
Second OpinionAReview a piece from its review packet in a fresh context. Judge the agreed result, what the change may have broken, and whether the evidence is real.developmentgoshellVotes: 0GitHub stars: 2
Setup Ai Build KitAStart or resume project setup with /setup-ai-build-kit. Use /implement after founding, or /shape for features and repairs.developmentpythonapiVotes: 0GitHub stars: 2
Setup HostingASet up or check how the tool runs live, including moving it to another host or recipe. The first run connects each merge to main to a deploy; this skill never merges code. Run the evidence run and the review first, and record any risk area's caution.developmentpythongoVotes: 0GitHub stars: 2
ShapeATurn a request or fault into one well-scoped piece before building. Typed alone, take the next piece that needs shaping. Shape records work and offers a ready piece to implement; it never builds.developmentapiVotes: 0GitHub stars: 2
TriageASort a request written in plain words before any work happens. Understand it, classify its intent and consequence, find open pieces it overlaps, and choose one route. Used by shape for every request, by implement for work found mid-build, and by maintain for an alert or a bill that becomes a piece.developmentgoapiVotes: 0GitHub stars: 2
What NowAOrient returners. Read state and name steps.developmentpythongoVotes: 0GitHub stars: 2
Build PieceABuild one ready piece to a confirmed, saved change, from the safe start to the updated records. Used by implement for every piece, a repair included, and by the builder agent. Refuses to start on top of uncommitted work. One piece per pass, always.developmentVotes: 0GitHub stars: 2
ClarifyAInterview the team before work is specified, one question at a time, each with a best guess attached. Used by setup-ai-build-kit for the founding interview and by shape when a request is too vague to size. Do not use for small clear changes or for repairs, and never write code during it.developmentVotes: 0GitHub stars: 2
Evidence RunAGather fresh evidence before the tool is relied on: promised behaviour, failure, data and access, operations, review, and an honest report. Used by setup-hosting, maintain and merge.developmentVotes: 0GitHub stars: 2
Fit CheckAFill the project's risk record, name each risk area with its caution, and give the risk notice where one is due. Used at founding, when a request changes the project, before hosting, at the quarterly visit, and when a repair stalls.developmentVotes: 0GitHub stars: 2
Live CopyAWork with the live copy safely. Pass a secret a check needs by its location, ask before any change to a live service, and roll back to an earlier version on a yes. Used by setup-hosting, maintain, merge, repair and what-now.developmentVotes: 0GitHub stars: 2
MergeATake a finished piece to main. The first upload and, by default, each merge wait for a yes. Used by implement, setup-hosting, maintain and founding.developmentVotes: 0GitHub stars: 2
Quality ChecksARun the kit's quality reads by script and act on their exit codes. The reach check, the trim, test strength, the check floor, boundary rules, and the structure, waste, document and old-branch reads.developmentVotes: 0GitHub stars: 2
RecordsAWrite and keep the project's records true. A piece and its labels, the printout, a piece's change to the masterplan and its checked mark, the coverage read, and the records a finished build updates. Used by every command.developmentVotes: 0GitHub stars: 2
RepairAReproduce a fault, then fix one cause at a time, with the risk notice after three failed attempts. Used by shape to reproduce a fault and by implement to build the repair.developmentVotes: 0GitHub stars: 2
ResearchACheck one outside fact against its primary source, or search for existing work before anything new is built. Used by shape, clarify and a build, and by the researcher agent.developmentVotes: 0GitHub stars: 2
Screen CheckAApply the kit's screen rules during a build or review that touches an interface. Read the project's own design system first, report what was applied and what remains for a person to try, and make no claim that the screen is accessible, compliant, or good.developmentgoVotes: 0GitHub stars: 2
Second OpinionAReview a piece from its review packet in a fresh context. Judge the agreed result, what the change may have broken, and whether the evidence is real.developmentVotes: 0GitHub stars: 2
TriageASort a request written in plain words before any work happens. Understand it, classify its intent and consequence, find open pieces it overlaps, and choose one route. Used by shape for every request, by implement for work found mid-build, and by maintain for an alert or a bill that becomes a piece.developmentVotes: 0GitHub stars: 2