doccker/cc-use-exp

API Design Safety helps you design REST API responses and generated outputs with consistent field semantics, null handling, and status codes. It also checks required fields before exporting files or sending downstream payloads to avoid silent failures.

Api Design Safety helps prevent REST API response design mistakes such as field mix-ups, ambiguous return types, and inconsistent empty values. Use it when designing or changing API responses and handling returned data.

Api Proxy Safety defines safe keyword matching for gateways, proxies, WAFs, and CDNs so normal content is not misclassified as an error. It is used when implementing heuristic checks for response bodies, status codes, and error schemas.

Async Task Pattern provides a standard triggerAsync/getStatus flow for operations that may run longer than 10 seconds. Use it for batch processing, remote API fan-out, or scans that would otherwise time out or be triggered twice.

Bash Style provides shell scripting and command-writing conventions for .sh files, Dockerfiles, Makefiles, YAML, and Markdown bash blocks. Use it to format commands, heredocs, file writes, permissions, and script safety.

Code Quality Principles provides a checklist for modular design, refactoring, and code review. Use it to assess module size, call depth, fan-in/fan-out, boundaries, scope cohesion, and predictability.

External System Debugging helps debug code that depends on browsers, editors, CDNs/WAFs, IM platforms, clipboards, or third-party SaaS. It requires collecting real environment data first, then using that evidence to diagnose paste, rendering, API, and cross-platform issues.

Field Mapping Safety helps prevent incorrect field-name guesses when refactoring table columns, enum mappings, and data transforms. Use it when similar fields or incomplete mappings could cause runtime blanks or Invalid Date issues.

Field Mapping Safety prevents mistakes when refactoring table columns, enum maps, and type conversions. It is used to verify real field names and complete mappings before changing code.

Frontend Development defines Vue 3, TypeScript, and UI style rules for building frontend pages and admin interfaces. Use it when you need consistent components, state handling, API typing, and performance patterns.

Frontend Development Standards defines Vue 3, TypeScript, UI, and state management conventions for building frontend apps. Use it when you need consistent component structure, error handling, and style rules.

Go Development Standards describes naming, error handling, concurrency, testing, and performance practices for Go code. Use it when writing or reviewing Go services and libraries.

Java Development Guidelines defines naming, exception handling, concurrency, testing, and Spring Boot usage rules for Java projects. Use it when writing or reviewing Java code to follow the repo’s development standards.

Java Development Standards defines naming, exception handling, null handling, concurrency, testing, and Spring Boot practices for Java code. Use it when writing or reviewing Java services and data access code.

Multi-Tenant Safety covers checks for tenant isolation in multi-tenant systems. Use it when code touches TenantContext, tenantId, tenant headers, filters, or repository access to prevent cross-tenant data leaks.

Ops Safety provides guardrails for system-level and server operations. Use it when planning sysctl, iptables, systemctl, Docker, or database DDL changes and need impact, risk, rollback, and confirmation steps.

Python Dev provides Python coding standards for style, type hints, error handling, logging, testing, and project structure. Use it when writing or reviewing Python code that should follow consistent conventions.

Redis Safety provides security and performance rules for Redis usage across languages. Use it when working with go-redis, Jedis, redis-py, or ioredis to avoid blocking commands, large keys, and missing TTLs.

Refactor Safety provides a checklist for code refactors so you can preserve original structure, branches, and data while changing implementation. Use it when extracting components, merging logic, renaming fields, or simplifying conditionals.

Ruanzhu generates DOCX source-code documents for software copyright filings when the user runs /ruanzhu or requests a source-code document. It follows a fixed generation workflow and output format.

Size Check reviews changed code for reuse, quality, and efficiency, then flags issues to fix. It also scans project files for line-count limit violations and CSS extraction needs.

Storage URL Safety helps choose between public, CDN, and presigned URLs for MinIO, OSS, and S3 objects. Use it when designing uploads, downloads, or long-lived file access to avoid expiry and access errors.

UI/UX Pro Max defines professional interface design rules for creating polished front-end layouts. Use it when a high-quality UI, strong visual hierarchy, or refined interaction details are needed.