185 skills · sorted by relevance
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and maintainability in Apple-platform or Swift server projects.
The English summary is being prepared. Showing the original description.
Independent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.
The English summary is being prepared. Showing the original description.
Independent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.
The English summary is being prepared. Showing the original description.
Run an explicitly requested, unusually strict dygo maintainability audit that seeks structural simplification, removes accidental complexity, and challenges weak abstractions without changing behavior.
The English summary is being prepared. Showing the original description.
Establish, author, restructure, or audit human-first processor Architecture, Design, Research, Review, and Verification documentation. Use for progressive documentation scaffolding, authority maps, reading paths, document-type content contracts, length-budgeted splitting, or maintainability reviews. Do not use as a substitute for cycle-accurate microarchitecture analysis or RTL implementation.
The English summary is being prepared. Showing the original description.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
The English summary is being prepared. Showing the original description.
Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.
The English summary is being prepared. Showing the original description.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
The English summary is being prepared. Showing the original description.
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.
The English summary is being prepared. Showing the original description.
Find overly complex code: files over 300 lines, functions over 50 lines, deeply nested conditions (4+ levels), and magic numbers. Use for code quality reviews, pre-release checks, or when asked to assess code maintainability.
The English summary is being prepared. Showing the original description.
When scoring a roadmap, PR review, ADR, or ticket for completeness — risk, tests, migration, maintainability. Dispatched by /refine-ticket, /adr-create, /review-changes; never auto-gates.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when a workflow step or the user asks for code simplification for clarity and maintainability without changing behavior.
The English summary is being prepared. Showing the original description.
Use when writing or refactoring modern C# with maintainability and performance standards. Keywords: coding standards, C# best practices, refactor C#, records, pattern matching, async best practices.
The English summary is being prepared. Showing the original description.
GStack developer-experience plan review for setup, local commands, docs, test loops, onboarding friction, and maintainability before implementation.
The English summary is being prepared. Showing the original description.
GStack developer-experience review for implemented repositories and workflows, focused on setup friction, command reliability, docs gaps, and maintainability.
The English summary is being prepared. Showing the original description.
GStack health-check method for broad project or repository health review across tests, docs, DX, release readiness, and maintainability.
The English summary is being prepared. Showing the original description.
Reviews SQL for security (injection, privileges), performance, maintainability, and quality across MySQL, PostgreSQL, SQL Server, Oracle, and other dialects. Use when reviewing a query, migration, stored procedure, or the SQL in a pull request.
The English summary is being prepared. Showing the original description.
Use when writing, reviewing, or refactoring production code where reliability, portability, maintainability, explicit contracts, resource safety, and cross-language coding standards matter across Python, TS/JS, C, C++, Rust, or Go.
The English summary is being prepared. Showing the original description.
Core technical, safety, and maintainability rules for codebase edits. Trigger when: - Writing code, refactoring, modifying files, or creating unit tests. - Proposing commits, reviewing git history, or auditing code quality. - Modifying files in any programming language (e.g. *.go, *.rs, *.py, *.ts, *.js, *.c, *.cpp). - Prompt contains keywords: refactor, build, compile, lint, test, git, commit, rule priority, type safety, error handling, defensive programming.
The English summary is being prepared. Showing the original description.
Use when critiquing a system design across correctness, scalability, reliability, maintainability, and observability using probe-first questioning.
The English summary is being prepared. Showing the original description.
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
The English summary is being prepared. Showing the original description.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
The English summary is being prepared. Showing the original description.
Knowledge base from FAA-HDBK-006D (2020), the FAA's System Reliability, Maintainability, and Availability (RMA) Handbook for National Airspace System (NAS) hardware and software. Use for RMA figures of merit (MTBF, MTBO, MTTR, the availability variants), the bathtub curve and probability distributions, the four-stage RMA lifecycle mapped to the FAA Acquisition Management System (AMS), the six-task RMA technical-management/acquisition process, service-thread criticality and the NAS-RD severity-to-target table, the RMA analysis toolbox (RBD, FMEA/FMECA, FTA, Ishikawa, Monte Carlo, Bayesian, FRACAS, ALT, reliability-growth/recovery tests), software reliability (early prediction + reliability growth), and tailorable example RMA requirements for a Program Requirements Document. Scope limits: it is FAA/NAS-specific guidance (not a requirement, by its own statement), centred on hardware-plus-software availability — it brackets out human/service/facility/communications availability, names but does not reproduce the math derivations or external standards (MIL-STDs, IEEE 1633, RTCA DO-178C/DO-278A, SAE JA1011), is thin on detailed worked numerical examples and on safety-case method, and predates any current revision beyond 006D.
The English summary is being prepared. Showing the original description.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
The English summary is being prepared. Showing the original description.