klausborges
- 17 skills
- 0 followers
- 6 hours ago last updated
- ▌ Effect V4 · klausborges bundleEffect v4 (4.0.0-beta.x) patterns and architecture judgment for TypeScript. Use when writing or reviewing Effect services, layers, schemas, typed errors, boundaries, config, CLIs, runtimes, or tests; when shaping or reviewing the structure of an Effect project, proposing a service or boundary, or arguing a wrapper is unnecessary — or when a project depends on `effect@4`. Effect v4 differs sharply from v3 and from plain TypeScript; verify APIs against the project's pinned source instead of recalling them.
- ▌ Manage Pr · klausborges bundleCreate and update GitHub pull requests, including stacked PRs and the stack merge loop. Use when the user wants a PR opened or updated, work delivered as a stack, or says "let's get the PRs merged" or "merged
- ▌ Plan Work · klausborges bundlePlan substantial work when explicitly requested or when material ambiguity, coordination, cross-cutting scope, irreversibility, or risk warrants planning.
- ▌ Commit Work · klausborges bundleWrite conventional commit messages from local git evidence and commit when asked. Use when the user wants changes committed or a commit message written.
- ▌ Review Work · klausborges bundleRead-only review of Plans, implementation, continuation rounds, or other scoped artifacts against intended behavior, docs, acceptance criteria, tests, and risk. Use for balanced, adversarial, multi-aspect, compliance, architecture, test, library, performance, or security review.
- ▌ Use Workflow · klausborges bundleLightweight workflow router. Use for substantial planning, implementation, simplification, handoff, review, diagnosis, explanation, architecture discovery, or prototyping work in repos that follow this workflow; honor explicit skill requests and repo-local instructions.
- ▌ Simplify Work · klausborges bundleSimplify an already-bounded code or documentation area without changing intended behavior. Use for deletion, direct-flow refactors, wrapper or branch reduction, clearer data models, reduced mutable state, or concrete simplification findings; use improve-architecture when the opportunity or design is still unclear.
- ▌ Write Handoff · klausborges bundleWrite a bounded fresh-context prompt or file for continuation, implementation, research, refactor, bugfix, review, or review-fix work.
- ▌ Diagnose Issue · klausborges bundleDiagnose bugs, failing tests, build failures, flaky behavior, unexpected output, or performance regressions. Read-only unless the user explicitly asks for a fix.
- ▌ Implement Work · klausborges bundleImplement an already-decided bounded scope from a Plan, handoff, review findings, direct brief, docs task, fix, or refactor. Use for implementation or continuation work; use diagnose-issue first when the cause is unknown.
- ▌ Plan Prototype · klausborges bundleBuild the smallest throwaway visual or logic prototype needed to answer a planning question before production implementation.
- ▌ Git Conventions · klausborges bundleShared git conventions for personal repos covering remote naming, primary remote choice, conventional commit shape, worktree placement, and commit/PR writing style. Use when setting up or renaming remotes, choosing where to push or open PRs, deciding where a worktree lives, or when another git skill points here.
- ▌ Coding Standards · klausborges bundleGeneric engineering standards for designing, implementing, refactoring, or reviewing code. Use when deciding how to structure or verify new code, when a standards question comes up, or when another skill needs the user's coding standards.
- ▌ Explain Codebase · klausborges bundleExplain how an unfamiliar codebase area fits together by mapping its purpose, entry points, modules, callers, flows, tests, and important terms. Read-only.
- ▌ Explain Workflow · klausborges bundleExplain how to invoke and use the workflow skills for a concrete situation without starting the work unless the user asks.
- ▌ Manage Worktrees · klausborges bundleCreate, reuse, and clean up git worktrees consistently. Use when work needs an isolated checkout, when the user asks for a worktree, or when stale worktrees need cleanup.
- ▌ Improve Architecture · klausborges bundleDiscover and shape architecture improvement or simplification opportunities in hard-to-understand, hard-to-test, shallow, scattered, or over-coupled code. Use when the opportunity or interface shape still needs discovery, not for an already-decided bounded change.