Skill UI

This guide details the systematic process for reviewing high-privilege accounts, including Domain Admins, cloud IAM roles, and service accounts. It is a critical identity governance function designed to validate that users only retain the access they absolutely require, thereby enforcing the principle of least privilege. This review is mandatory for compliance frameworks like SOC 2, PCI DSS, and HIPAA, and involves discovery, validation, remediation, and continuous monitoring.

This guide enforces the 'spec-first' principle in software development, treating the specification as a non-negotiable contract. It outlines a rigorous, multi-stage workflow detailing mandatory sections (Functional/Non-Functional Requirements, Acceptance Criteria, API Contracts, Data Models) and bounded autonomy rules. Users learn how to define the system 'must do' before writing a single line of code, thereby minimizing rework and eliminating scope creep.

An automated verification system designed for critical healthcare application deployments (EMR/EHR). This harness enforces stringent patient safety standards by running multiple mandatory test gates, including Clinical Decision Support System (CDSS) accuracy, Protected Health Information (PHI) leakage prevention, and data integrity checks. A single failure in critical gates automatically blocks deployment, ensuring regulatory compliance and optimal patient safety in the CI/CD pipeline.

A comprehensive guide to building HIPAA, GDPR, and other global compliance systems for healthcare applications. This pattern outlines best practices for protecting Protected Health Information (PHI) and Personally Identifiable Information (PII) by implementing robust access controls, Row-Level Security (RLS), and mandatory audit trails. Essential for any feature handling patient or clinical data.

This comprehensive tool generates high-quality Mermaid diagram code (including flowcharts, sequence diagrams, ER diagrams, etc.) directly from natural language user requirements. It handles complex structured output, mandatory syntax validation using dedicated CLI tools, and detailed visual review to ensure the accuracy of all components and connections.

Applies two-axis scoring, mandatory devil’s advocate reasoning, and persistent history to keep post-task self-reviews honest, resistant to inflation, and suitable for Claude Code sessions.

A comprehensive set of specialized tools for deep interaction with source codebases. This context-mode is mandatory for advanced tasks such as running code snippets, analyzing files, batch processing repository commands, indexing knowledge, searching content, and fetching web data. It ensures that interactions are context-aware and highly efficient, moving beyond basic file listing or general chat prompts.

A robust, production-tested pattern for coordinating multiple specialized AI agents. The orchestrator decomposes complex tasks, routes them to the most suitable specialist, prevents redundant or conflicting work (anti-duplication), and enforces mandatory quality gates (e.g., running tests, checking file diffs) to verify results before marking a task as complete. It also includes heartbeat monitoring for task progress.

This skill activates the P7 Senior Engineer mode, designed for rigorous, solution-driven execution under P8 supervision. It is used when the user explicitly requests 'P7模式' or when invoked as a sub-task executor by P8. The process involves three key stages: designing a detailed implementation plan and impact analysis, executing the core coding, and finally, completing a mandatory three-question self-review, ensuring high quality and comprehensive verification.

This document defines the strict, mandatory structure and deterministic rules for creating implementation plans. It ensures that plans for new features, refactoring, or architectural changes are fully self-contained, machine-readable, and structured for automated execution by advanced AI agents or human teams.

This guide outlines the process and mandatory structure for documenting defects found during an Oracle-to-PostgreSQL migration. It details how to write actionable bug reports, covering required elements like Severity, Root Cause, Scenario, and Solution. It emphasizes treating Oracle as the source of truth and handling data layer nuances (e.g., NULL vs. empty string) to ensure accurate defect tracking and remediation.

Defines mandatory contribution guidance for repository work, insisting contributors locate workflow documentation, follow branch/commit/PR templates, and run required linters or tests before submitting changes, without executing forbidden scripts.