Results for “maintainability”

Improves measured performance while preserving correctness, reliability, and maintainability.

Use when restructuring code for maintainability while preserving external behavior.

Improve code structure and readability without changing external behavior through surgical refactoring techniques.

Review and refactor code according to project-specific coding guidelines and instructions.

Reviews cohesion, naming, responsibility, complexity, and maintainability. Do not use as a default companion to every code change.

Refactors Java methods by removing unused or redundant parameters to improve readability and maintainability.

Identifies, classifies, and prioritizes tech debt to build a refactoring roadmap, drawing on twelve classic engineering books.

Refactors Java methods by extracting code blocks into separate, well-named methods to improve readability and maintainability.

Use this skill after completing code changes to review for reuse, quality, and efficiency. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling.

Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building maintainable .NET applications.

Use this skill after completing code changes to review for reuse, quality, and efficiency. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

Vyper Mastery

Applies SOLID principles, clean architecture layers, dependency injection, and patterns like CQRS and event sourcing to design scalable, maintainable systems.

Improves code readability and maintainability by applying SOLID principles, meaningful naming, small functions, proper error handling, and DRY practices.

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

Engineering observability and reliability: SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, reliability review. Use for instrumentation or SLO definition.

Conduct authenticated and unauthenticated vulnerability scans using Tenable Nessus to identify known vulnerabilities, misconfigurations, and missing patches, with prioritized remediation guidance.

Provides production-grade Laravel architecture patterns for building scalable, maintainable applications with controllers, services, Eloquent ORM, queues, events, caching, and API resources.

Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".

Storage management for Zephyr RTOS. Covers Non-Volatile Storage (NVS) for persistent settings, flash partition management in Devicetree, and runtime flash layout access. Trigger when implementing persistent data storage, managing flash wear leveling, or configuring device partitions.

Apply the Aesthetic-Usability Effect to ensure visual consistency and polish translate into user trust and perceived quality without masking genuine usability problems.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Enforces rigorous ML modeling, feature engineering, training, and evaluation standards at principal-engineer level.

Adds logging, metrics, tracing, and alerting to make production behavior visible and diagnosable.

Design secure, scalable Firebase backends with Firestore, Auth, Functions, and Storage, following best practices for security rules, data modeling, and real-time listeners.

Use for writing, reviewing, debugging, or testing bounded retry policies in Python with Tenacity, including retry predicates, stop and wait strategies, jitter, exception propagation, callbacks, Retrying, and AsyncRetrying. Do not use for generic loops, scheduled jobs, domain polling without a retryable operation, or operations whose side effects are not safe to repeat.

Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.

Stores verified cross-session facts, decisions, preferences, and open questions without secrets, speculation, or monitoring.