All authors
Claude Skills by Univers42
github.com/Univers4244 skills0 installs12 views
- Api EndpointScaffold a new REST endpoint that mirrors the ones already there. Use when a route is missing, a handler needs wiring, a resource has to be reachable over HTTP, or a client calls the API by hand. Auto-triggers on: "add an endpoint", "new API route", "expose this over HTTP", "wire a handler"Votes: 0GitHub stars: 4
- BrainstormDiverge wide on the options, then converge on evidence and cost, ending in one recommendation, a smallest experiment and a kill criterion. Use when a decision has several viable answers and the risk is settling on the first plausible one, or handing back an unranked menu. Auto-triggers on: "what are the options", "how else could we", "give me ideas", "explore approaches", "what would you suggest"Votes: 0GitHub stars: 4
- Browser TestingVerifies a change in a real browser and returns the artifact: the steps, the viewport, the console. Use when a page is claimed to work but only a unit test says so, or when a flow must be clicked through. Auto-triggers on: "test in the browser", "does the page work", "check the console", "screenshot", "click through", "playwright", "verify the UI", "e2e test"Votes: 0GitHub stars: 4
- Commit CraftTurn a working tree into a history someone can read, revert and bisect. Use when changes are uncommitted, one commit mixes several concerns, a message does not say what changed, or a branch needs tidying before review. Auto-triggers on: "commit this", "write a commit message", "split these changes", "prepare a PR", "clean up the history"Votes: 0GitHub stars: 4
- Context BudgetMeasure and cut what a config costs in context every session: always-on rules, invocable descriptions, skills that never fire. Use when the window fills before any work starts, a session compacts mid-task, or it is unclear what loads every session. Auto-triggers on: "reduce token usage", "context is full", "what is loading", "trim the config", "context budget", "why is my context so big"Votes: 0GitHub stars: 4
- DebugFind the actual cause of a failure instead of guessing at fixes. Use when a test fails, a build breaks, a crash has no obvious cause, behaviour differs between machines, or a fix that worked yesterday stopped working. Auto-triggers on: "why is this failing", "debug this", "this test is flaky", "it works locally", "fix this bug", "this crashes"Votes: 0GitHub stars: 4
- Design ReviewJudges an interface by hierarchy, rhythm, type, consistency and the states nobody built, then names the smallest fix for each. Use when a design is described as feeling off, crowded or unfinished and the cause has not been named yet. Auto-triggers on: "review this design", "does this look right", "improve the UI", "critique this", "the design feels off", "make this look better"Votes: 0GitHub stars: 4
- Doc SyncFind the documentation a change just made false and fix exactly that, examples copied from a passing run. Use when a flag was renamed, a path moved, a default changed, a command was removed, or a README example no longer matches what the code prints. Auto-triggers on: "update the docs", "are the docs current", "the README is out of date", "document this change", "the docs are stale"Votes: 0GitHub stars: 4
- FrontendBuilds UI that holds up at every width, in both themes, with real data, and for someone on a keyboard. Use when a page or a component is being added or restyled, when a layout breaks on a narrow screen or in dark mode, or when a view has no empty, loading or error state. Auto-triggers on: "build a component", "add a page", "style this", "make it responsive", "dark mode", "the layout breaks"Votes: 0GitHub stars: 4
- OriginalityFind what already does this job, in the repo and outside it, then say whether to reuse, wrap, borrow or build. Use when something new is about to be written and nobody has checked whether the stdlib, a dependency or the platform already covers it. Auto-triggers on: "has this been done", "is there a library for", "should I build this", "prior art", "am I reinventing", "build it from scratch"Votes: 0GitHub stars: 4
- Perf BudgetFixes a performance target before any optimisation starts, then measures against it until it passes. Use when something is slow and the work should stay bounded, or when an optimisation is proposed with no number attached to it. Auto-triggers on: "make it faster", "is this fast enough", "optimize this", "performance budget", "it feels slow", "reduce latency"Votes: 0GitHub stars: 4
- Write TestGenerate tests for code that already exists. Use when a module has no tests, coverage is thin, a fix needs a regression test, or a change should land with proof it still works. Auto-triggers on: "write tests for", "add test coverage", "this needs tests"Votes: 0GitHub stars: 4
- Api ConventionREST API conventions: resource-oriented and versioned routes, auth and access control on every surface, and one error shape. Use when editing routes, handlers, controllers or router files.Votes: 0GitHub stars: 4
- Api EndpointScaffold a new REST endpoint that mirrors the ones already there. Use when a route is missing, a handler needs wiring, a resource has to be reachable over HTTP, or a client calls the API by hand. Auto-triggers on: "add an endpoint", "new API route", "expose this over HTTP", "wire a handler"Votes: 0GitHub stars: 4
- BrainstormDiverge wide on the options, then converge on evidence and cost, ending in one recommendation, a smallest experiment and a kill criterion. Use when a decision has several viable answers and the risk is settling on the first plausible one, or handing back an unranked menu. Auto-triggers on: "what are the options", "how else could we", "give me ideas", "explore approaches", "what would you suggest"Votes: 0GitHub stars: 4
- Browser TestingVerifies a change in a real browser and returns the artifact: the steps, the viewport, the console. Use when a page is claimed to work but only a unit test says so, or when a flow must be clicked through. Auto-triggers on: "test in the browser", "does the page work", "check the console", "screenshot", "click through", "playwright", "verify the UI", "e2e test"Votes: 0GitHub stars: 4
- CaveatGive every heuristic, sample, regex parser, cache, timeout and derived number the one line saying what it gets wrong. Use when a change adds an approximation, a bounded read, an estimate or a retry bound, or you need to know what a code is bad at. Auto-triggers on: "is this exact", "add a caveat", "what are the limitations", "document the limits", "how accurate is this"Votes: 0GitHub stars: 4
- Commit CraftTurn a working tree into a history someone can read, revert and bisect. Use when changes are uncommitted, one commit mixes several concerns, a message does not say what changed, or a branch needs tidying before review. Auto-triggers on: "commit this", "write a commit message", "split these changes", "prepare a PR", "clean up the history"Votes: 0GitHub stars: 4
- Context BudgetMeasure and cut what a config costs in context every session: always-on rules, invocable descriptions, skills that never fire. Use when the window fills before any work starts, a session compacts mid-task, or it is unclear what loads every session. Auto-triggers on: "reduce token usage", "context is full", "what is loading", "trim the config", "context budget", "why is my context so big"Votes: 0GitHub stars: 4
- DebugFind the actual cause of a failure instead of guessing at fixes. Use when a test fails, a build breaks, a crash has no obvious cause, behaviour differs between machines, or a fix that worked yesterday stopped working. Auto-triggers on: "why is this failing", "debug this", "this test is flaky", "it works locally", "fix this bug", "this crashes"Votes: 0GitHub stars: 4
- Design ReviewJudges an interface by hierarchy, rhythm, type, consistency and the states nobody built, then names the smallest fix for each. Use when a design is described as feeling off, crowded or unfinished and the cause has not been named yet. Auto-triggers on: "review this design", "does this look right", "improve the UI", "critique this", "the design feels off", "make this look better"Votes: 0GitHub stars: 4
- Doc SyncFind the documentation a change just made false and fix exactly that, examples copied from a passing run. Use when a flag was renamed, a path moved, a default changed, a command was removed, or a README example no longer matches what the code prints. Auto-triggers on: "update the docs", "are the docs current", "the README is out of date", "document this change", "the docs are stale"Votes: 0GitHub stars: 4
- FrontendBuilds UI that holds up at every width, in both themes, with real data, and for someone on a keyboard. Use when a page or a component is being added or restyled, when a layout breaks on a narrow screen or in dark mode, or when a view has no empty, loading or error state. Auto-triggers on: "build a component", "add a page", "style this", "make it responsive", "dark mode", "the layout breaks"Votes: 0GitHub stars: 4
- GrillClose the frontier between what is decided and what is still open: the facts are gathered from the repo, the decisions go to the user in short rounds, each with a recommended answer. Use when a request is underspecified, the done-when is not stateable, or a rules/risk.md trigger is unresolved before code starts. Auto-triggers on: "grill me", "what have we decided", "ask me the hard questions"Votes: 0GitHub stars: 4
- OriginalityFind what already does this job, in the repo and outside it, then say whether to reuse, wrap, borrow or build. Use when something new is about to be written and nobody has checked whether the stdlib, a dependency or the platform already covers it. Auto-triggers on: "has this been done", "is there a library for", "should I build this", "prior art", "am I reinventing", "build it from scratch"Votes: 0GitHub stars: 4
- Perf BudgetFixes a performance target before any optimisation starts, then measures against it until it passes. Use when something is slow and the work should stay bounded, or when an optimisation is proposed with no number attached to it. Auto-triggers on: "make it faster", "is this fast enough", "optimize this", "performance budget", "it feels slow", "reduce latency"Votes: 0GitHub stars: 4
- PrototypeAnswer one feasibility question in a throwaway worktree, time-boxed, and end with keep or kill. The spike is measured, never merged. Use when an approach's cost, performance or feasibility is unproven, or when a spike, benchmark or quick prototype is asked for. Auto-triggers on: "prototype this", "spike this", "does this approach work", "how fast is this really"Votes: 0GitHub stars: 4
- Refactor CC norms: file and function shape, manual memory with a named owner for every allocation, header hygiene and the warning-free build. Use when editing C source or header files.Votes: 0GitHub stars: 4
- Refactor GoGo norms: idioms that keep a package boring, hexagonal port boundaries, error values over panics and goroutine leaks. Use when editing Go files.Votes: 0GitHub stars: 4
- Refactor RustRust norms: borrowing over cloning, newtypes over primitive obsession, module layout that mirrors the domain and no panics on a public path. Use when editing Rust files.Votes: 0GitHub stars: 4
- Refactor ShellShell norms: pick the dialect by where the script runs (strict POSIX for portable ones, bash for a gate), quote every expansion, and keep the error path explicit. Use when editing shell scripts.Votes: 0GitHub stars: 4
- Refactor TypescriptTypeScript norms: no `any`, no cast to silence the checker, strict flags on, and domain types that make an illegal state unrepresentable. Use when editing TypeScript files.Votes: 0GitHub stars: 4
- Script Library`library-first` applied to tooling: check the project's own scripts, then `devil <tool>`, then the vetted external registry, before writing a shell or Python utility. Use when editing shell or Python scripts, or a Makefile.Votes: 0GitHub stars: 4
- Write TestGenerate tests for code that already exists. Use when a module has no tests, coverage is thin, a fix needs a regression test, or a change should land with proof it still works. Auto-triggers on: "write tests for", "add test coverage", "this needs tests"Votes: 0GitHub stars: 4
- Api ConventionREST API conventions: resource-oriented and versioned routes, auth and access control on every surface, and one error shape. Use when editing routes, handlers, controllers or router files.Votes: 0GitHub stars: 4
- CaveatGive every heuristic, sample, regex parser, cache, timeout and derived number the one line saying what it gets wrong. Use when a change adds an approximation, a bounded read, an estimate or a retry bound, or you need to know what a code is bad at. Auto-triggers on: "is this exact", "add a caveat", "what are the limitations", "document the limits", "how accurate is this"Votes: 0GitHub stars: 4
- GrillClose the frontier between what is decided and what is still open: the facts are gathered from the repo, the decisions go to the user in short rounds, each with a recommended answer. Use when a request is underspecified, the done-when is not stateable, or a rules/risk.md trigger is unresolved before code starts. Auto-triggers on: "grill me", "what have we decided", "ask me the hard questions"Votes: 0GitHub stars: 4
- PrototypeAnswer one feasibility question in a throwaway worktree, time-boxed, and end with keep or kill. The spike is measured, never merged. Use when an approach's cost, performance or feasibility is unproven, or when a spike, benchmark or quick prototype is asked for. Auto-triggers on: "prototype this", "spike this", "does this approach work", "how fast is this really"Votes: 0GitHub stars: 4
- Refactor CC norms: file and function shape, manual memory with a named owner for every allocation, header hygiene and the warning-free build. Use when editing C source or header files.Votes: 0GitHub stars: 4
- Refactor GoGo norms: idioms that keep a package boring, hexagonal port boundaries, error values over panics and goroutine leaks. Use when editing Go files.Votes: 0GitHub stars: 4
- Refactor RustRust norms: borrowing over cloning, newtypes over primitive obsession, module layout that mirrors the domain and no panics on a public path. Use when editing Rust files.Votes: 0GitHub stars: 4
- Refactor ShellShell norms: pick the dialect by where the script runs (strict POSIX for portable ones, bash for a gate), quote every expansion, and keep the error path explicit. Use when editing shell scripts.Votes: 0GitHub stars: 4
- Refactor TypescriptTypeScript norms: no `any`, no cast to silence the checker, strict flags on, and domain types that make an illegal state unrepresentable. Use when editing TypeScript files.Votes: 0GitHub stars: 4
- Script Library`library-first` applied to tooling: check the project's own scripts, then `devil <tool>`, then the vetted external registry, before writing a shell or Python utility. Use when editing shell or Python scripts, or a Makefile.Votes: 0GitHub stars: 4