engineering-practices

Plugin engineering-practices from marketplace engineering-standards-marketplace in shah-arnav3/eng_standards-marketplace-claudecode. Commands read from the repo's manifest — 6 days ago.

Skills (10)

• code-quality

  Coding style fundamentals — immutability, error handling strategy, input validation, and general code quality standards that apply across languages. Use whenever writing or reviewing any code for correctness and maintainability, deciding how to validate input or handle errors, or the user mentions c

• concurrency

  Handling concurrency correctly across languages — threads vs. async I/O, locks and lock-free patterns, race conditions, deadlock avoidance, and language-specific concurrency primitives (Java/C# threads and async, Python asyncio/GIL, Node event loop, Go goroutines/channels, Rust Send/Sync). Use whene

• debloating

  Finding and safely removing bloat — dead code, unused dependencies, speculative abstraction, stale feature flags, and oversized build artifacts — with evidence before every deletion. Use whenever the user asks to clean up, simplify, slim down, or remove dead or unused code or dependencies, reduce bu

• debugging

  Systematic debugging methodology — reproducing bugs reliably, binary-search isolation, reading stack traces, using debuggers and structured logging, and distinguishing symptoms from root causes. Use whenever diagnosing a bug, investigating unexpected behavior, reading an error/stack trace, or the us

• documentation-practices

  Modern documentation style and practices — docstrings/doc comments, README structure, API documentation, and inline comment discipline. Use whenever writing or reviewing documentation, docstrings, README files, API docs, or the user mentions documenting a project or function.

• git-workflows

  Modern git workflows and procedures — trunk-based development vs. Git Flow, commit hygiene and conventional commits, branching strategy, commit authorship (no AI co-author attribution), pull request practices, rebasing vs. merging, and resolving conflicts safely. Use whenever writing or suggesting a

• observability

  Instrumenting services so production behavior can be understood — structured logging, metrics (RED/USE), distributed tracing with OpenTelemetry, correlation IDs, SLOs, and alerting on symptoms rather than causes. Use whenever adding logging, metrics, or tracing to code, designing dashboards or alert

• performance-optimization

  Performance and runtime complexity optimization — Big O analysis, profiling before optimizing, algorithmic vs. constant-factor improvements, caching strategy, and database/network performance patterns. Use whenever analyzing or improving performance, discussing time/space complexity, deciding whethe

• scoped-changes

  Discipline for file creation, code extension, and bug fixes — keeping changes scoped and grounded in what was actually asked, verifying assumptions against the real codebase before editing, and avoiding unrequested refactors or hallucinated APIs. Use whenever creating new files, adding a feature to

• testing-practices

  Modern testing procedures and practices — the test pyramid, unit vs. integration vs. e2e boundaries, test doubles (mocks/stubs/fakes), test-driven workflows, coverage as a signal not a target, and framework patterns (JUnit/xUnit/pytest/Jest/Go testing/Rust built-in). Use whenever writing tests, revi

Similar plugins