claude

engineering-mastery

Eighteen skills for professional software engineering: clean code, clean architecture, defensive programming, testing, performance, code review, security, observability, refactoring, API design, concurrency, documentation, AI-native codebase design, ML experimentation, A/B testing, mobile development, frontend development, and algorithms.

1 on GitHubby tswrv1.4.0MITupdated 7 months ago
/

Plugin engineering-mastery from marketplace engineering-mastery-marketplace in tswr/engineering-mastery-plugin. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (18)

  • ab-testing

    Apply when designing, running, or analyzing A/B tests and online controlled experiments: hypothesis formation, metric selection, sample size calculation, statistical analysis, and common pitfalls. Trigger on mentions of A/B testing, experiments, statistical significance, conversion rate, or controll

  • ai-native

    Apply when structuring a codebase for effective AI-assisted development: agent instruction files, context engineering, module boundaries for LLM comprehension, testing as agent feedback, and workflow patterns for human-agent collaboration. Trigger on mentions of AI-native, agentic coding, CLAUDE.md,

  • algorithms

    Apply when choosing data structures, analyzing complexity, or implementing algorithmic solutions: Big O analysis, arrays, trees, graphs, sorting, searching, dynamic programming, and greedy algorithms. Trigger on mentions of time complexity, space complexity, Big O, data structures, sorting, searchin

  • api-design

    Apply when designing, reviewing, or evolving HTTP APIs, gRPC services, or library interfaces: resource modeling, naming, versioning, error handling, pagination, and backward compatibility. Trigger on mentions of REST, API design, endpoints, backward compatibility, API versioning, or contract-first d

  • clean-architecture

    Apply when designing system structure, defining module or package boundaries, choosing layering, deciding where code belongs in a large codebase, or evaluating dependency direction. Trigger on questions about bounded contexts, module depth, interface design, dependency management, or monolith decomp

  • clean-code

    Apply when writing, refactoring, or reviewing code with focus on naming, function design, readability, class structure, error handling, or code smells. Trigger on requests to 'clean up' code, improve readability, reduce complexity, or apply SOLID principles. Not for architecture, performance, securi

  • code-review

    Apply when reviewing a pull request, diff, or code change using a structured multi-pass methodology. Connects to clean-code, clean-architecture, defensive-programming, testing, performance, and security skills as its review checklist. Trigger on requests to review code, evaluate merge readiness, or

  • concurrency

    Apply when writing concurrent, parallel, or distributed code: thread safety, synchronization, async patterns, distributed system reliability, consistency models, and resilience patterns. Trigger on mentions of threads, async, locks, distributed systems, retries, circuit breakers, consensus, eventual

  • defensive-programming

    Apply when writing code that must be hard to misuse: immutability, visibility, contracts, assertions, resource safety, and type-level invariant enforcement. Trigger on mentions of const, encapsulation, access control, defensive coding, RAII, or 'harder to misuse.' Not for security against adversaria

  • documentation

    Apply when writing comments, docstrings, READMEs, ADRs, or any form of technical documentation. Trigger on mentions of documentation, comments, docstrings, ADRs, or explaining code. Focuses on concise, non-obvious documentation that captures business logic and decisions the code cannot express. Not

  • frontend

    Apply when building web frontends: component architecture, state management, rendering strategies, accessibility, performance, styling, and data fetching. Trigger on mentions of React, Vue, frontend, components, CSS, Tailwind, accessibility, web vitals, or single-page application. Framework-specific

  • ml-experimentation

    Apply when building, training, evaluating, or deploying machine learning models: experiment tracking, data validation, feature engineering, model selection, hyperparameter tuning, and MLOps. Trigger on mentions of training, model evaluation, feature engineering, experiment tracking, ML pipeline, or

  • mobile

    Apply when building mobile applications: lifecycle management, navigation, offline support, performance, accessibility, and platform conventions. Trigger on mentions of iOS, Android, React Native, Flutter, mobile app, SwiftUI, Jetpack Compose, or mobile UI. Platform-specific idioms are in references

  • observability

    Apply when adding logging, metrics, tracing, alerting, or debugging production issues. Trigger on mentions of structured logging, distributed tracing, SLIs, SLOs, dashboards, monitoring, or systematic debugging. Not for security logging — use the security skill for that. Language-specific idioms are

  • performance

    Apply when optimizing for speed, throughput, or memory efficiency, writing benchmarks, or profiling applications. Trigger on mentions of benchmarking, profiling, cache misses, memory layout, hot paths, latency, throughput, SIMD, branch prediction, or 'why is this slow.' Language-specific tools and i

  • refactoring

    Apply when restructuring existing code without changing its behavior: extracting methods or classes, moving responsibilities, simplifying conditionals, improving names, or breaking dependencies in legacy code. Trigger on mentions of refactoring, code smells, extract method, legacy code, or technical

  • security

    Apply when code handles untrusted input, authentication, authorization, cryptography, secrets, or crosses a trust boundary. Trigger on mentions of security review, threat modeling, vulnerabilities, injection, XSS, CSRF, SSRF, auth, secrets management, or hardening. Extends the defensive-programming

  • testing

    Apply when writing tests, reviewing tests, deciding what to test, choosing test doubles, structuring test suites, or testing legacy code. Trigger on mentions of TDD, mocking, test coverage, test smells, integration tests, characterization tests, or getting code under test. Language-specific framewor

View source on GitHub

Maintain engineering-mastery?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted