austek
- 32 skills
- 0 followers
- 7 hours ago last updated
- ▌ Scala Coding Standards · austek bundleScala coding standards and best practices covering null/option handling, effect systems, anti-patterns, concurrency, error handling, immutability, implicits/givens, API design, collections, pattern matching, for-comprehensions, naming, and Scaladoc. Use when writing, reviewing, or refactoring Scala code, or when the user asks about Scala style, design, or best practices.
- ▌ Scala Tooling · austek bundleScala development tooling configuration and best practices for sbt, Mill, compiler flags, Scalafix, Scalafmt, Scalastyle, and Wartremover. Use when setting up a Scala project, configuring the build, compiler warnings, linters, or formatters, or when editing build.sbt or build.mill.
- ▌ Polyglot Tutor · austekSocratic tutor for learning Rust and Python — progressive exercises, compiler/traceback-driven debugging, ownership vs. runtime-model contrasts. Use when the user asks to learn, practice, or debug exercises in Rust or Python, or wants a language concept explained from first principles.
- ▌ Python Testing · austek bundlePython test-writing best practices covering test structure, fixtures, parametrization, and mocking with pytest. Use when writing, reviewing, or refactoring tests, adding test coverage, or working in tests directories and conftest.py.
- ▌ Python Tooling · austek bundlePython development tooling configuration and best practices for ruff, mypy, pytest, pyscn, and uv. Use when setting up a Python project, configuring linters, formatters, type checkers, or test frameworks, or when editing pyproject.toml or tool config files.
- ▌ Claude Settings Split · austekMove uncommitted changes from shared claude/.claude/settings.json to claude-profiles/claude_personal.json, claude_work.json, or claude_homelab.json. Use for profile-specific hooks, plugins, permissions, or absolute paths.
- ▌ Verifying Code Claims · austekVerify code claims before approving diffs, PRs, or refactors (e.g., mechanical cleanup, renames, type swaps, version bumps, security controls, caches, collections, suppressions).
- ▌ Jvm Systems Mentor · austekSocratic staff-level SWE mentor for high-throughput JVM systems, low-latency concurrency, and distributed backend architecture. Use when reviewing code, debugging concurrency/memory issues, or evaluating system design trade-offs.
- ▌ Java Coding Standards · austek bundleJava coding standards and best practices covering anti-patterns, resource management, concurrency, API design, error handling, immutability, object-oriented design, sealed types and pattern matching, Javadoc, records, reflection/serialization, modules, collections/streams, generics, nullability, performance, and naming. Use when writing, reviewing, or refactoring Java code, or when the user asks about Java style, design, or best practices.
- ▌ Rust Coding Standards · austek bundleRust coding standards and best practices covering ownership and borrowing, error handling, async programming, API design, unsafe code, and performance. Use when writing, reviewing, or refactoring Rust code, or when the user asks about Rust style, design, or best practices.
- ▌
- ▌ Grilling · austekGrill the user relentlessly about a plan, decision, or idea to stress-test their thinking.
- ▌ Wait What · austekStop. The last message was not understood. Re-pitch it using simplified language.
- ▌ Nuke Comments · austek bundleMechanically strip every comment from source files in one pass, with zero per-comment review or judgment — a fast syntax-driven deletion, not a quality/cleanup pass. Use whenever the user says to "nuke", "strip", "wipe", "delete all", or "remove all" comments, wants comments gone with "no checking" or "don't review them", or explicitly rejects a judgment-based comment cleanup in favor of blind removal. Do NOT use this for requests like "clean up bad comments", "remove redundant/tutorial comments", or "improve comment quality" — those need per-comment judgment (SAFETY docs, license headers, and public API docs must survive that kind of pass); this skill removes literally all of them, no exceptions, and is for when the user explicitly wants that. Takes an optional argument scoping the pass: a file or directory path, a PR number/URL, a branch name, or "full repo"/"repo". With no argument, scopes to uncommitted changes if there are any, and otherwise reports that there's nothing to strip rather than defaulting to
- ▌ Land Pr Oss · austekShepherd your own open PR on a personal/OSS repo to mergeable: poll CI, pull failing-check logs, fetch reviewer feedback (inline threads + review verdicts), draft fixes, push after confirmation, reply to and resolve the threads that fix actually addresses, re-checking for docs drift each loop. Use for "check my PR", "is my PR green", "address the review comments", or "land this PR".
- ▌ Codebase Design · austek bundleVocabulary and principles for designing deep modules. Use to design interfaces, find deepening opportunities, place seams, or improve testability.
- ▌ Domain Modeling · austek bundleBuild and sharpen project's domain model (glossary/ADRs). Use when modifying CONTEXT.md or ADRs.
- ▌ Idea MCP Tools · austekTool-selection rules for when the IntelliJ IDEA MCP server (`mcp__idea__*` tools) is connected. Consult this whenever exploring code (finding a symbol, its usages, or callers), checking whether a file compiles or lints, doing a multi-site rename or refactor, or debugging a runtime issue — the IDE's index and debugger are cheaper and faster than Bash/grep/Read for these. Always check this before reaching for grep, cat, a full Gradle/Maven/npm build, or a print-statement debugging loop when `mcp__idea__*` tools are present in the session's tool list, even if the user's request doesn't mention the IDE.
- ▌ Prune Comments · austekZero-tolerance comment eradication and structural refactoring. Enforces a strict "code speaks for itself" paradigm. Deletes ALL inline comments. If a comment explains complex logic, a platform quirk, or a constraint, you MUST refactor the code (extract methods, add runtime assertions, use custom exception messages, or rename types) to make that reality executable or structurally obvious. Takes an optional argument scoping the pass: a file or directory path, a PR number/URL, a branch name, or "full repo"/"repo".
- ▌ Grill With Docs · austekRelentless interview to sharpen a plan/design, concurrently generating docs (ADRs/glossary).
- ▌ Create Pr Oss · austekOpen a pull request on a personal or open-source GitHub repo: fork/upstream detection, repo's own contribution conventions (CONTRIBUTING.md, PR template, DCO/CLA sign-off), a docs-drift check, branch naming, and check monitoring. Use for "create/open a PR" or "push & open PR" on a non-Collibra repo.
- ▌ Review Pr Oss · austekReview a PR on a personal or open-source GitHub repo. No CODEOWNERS/team scoping — reviews the full diff, detects languages, applies the repo's own CONTRIBUTING.md/CLAUDE.md rules + language persona skills, checks DCO/CLA sign-off, and delegates to pr-review-toolkit:review-pr.
- ▌ To Questionnaire · austekTurn an unresolved decision into a Markdown questionnaire to extract missing knowledge from a recipient async or in a meeting.
- ▌ Java Testing · austek bundleJava test-writing best practices covering Mockito, JUnit 5 structure, AssertJ assertions, fixtures, Testcontainers, parameterized tests, and test doubles. Use when writing, reviewing, or refactoring Java tests, adding test coverage, or working under src/test.
- ▌ Java Tooling · austek bundleJava development tooling configuration and best practices for Gradle/Maven builds, static analysis, CI quality gates, dependency management, and lint/formatting. Use when setting up a Java project, configuring build tools, static analyzers, or CI gates, or when editing pom.xml or build.gradle(.kts).
- ▌ Rust Testing · austek bundleRust test-writing best practices covering test structure, fixtures, mocking, property-based testing, and benchmarks. Use when writing, reviewing, or refactoring tests, adding test coverage, or working in a tests directory or
- ▌ Rust Tooling · austek bundleRust development tooling configuration and best practices for clippy, rustc lints, and Cargo workspace/project structure. Use when setting up a Rust project, configuring lints, or editing Cargo.toml or workspace layout.
- ▌ Business Analysis · austek bundleProduce business/impact analysis and Acceptance Criteria for a Jira ticket. Anchors on PR diff (post-fix) or HEAD mechanism (pre-fix). Use for impact analysis, bug exposure, or AC generation. Can post to Jira.
- ▌ Scala Testing · austek bundleScala test-writing best practices covering async testing, mocking discipline, ScalaCheck property-based testing, ScalaTest/MUnit structure, and fixtures. Use when writing, reviewing, or refactoring Scala tests, adding test coverage, or working in test sources.
- ▌ Handoff · austekCompact the current conversation into a handoff document for a fresh agent to pick up.
- ▌ Python Coding Standards · austek bundlePython coding standards and best practices covering error handling, performance optimization, async patterns, SOLID design principles, documentation, data validation, and object-oriented programming. Use when writing, reviewing, or refactoring Python code, or when the user asks about Python style, design, or best practices.
- ▌ Improve Codebase Architecture · austek bundleScan codebase for deepening opportunities, present visual HTML report, and grill user on selection.