Use this skill when designing REST API responses or handling returned values. It helps keep business data, user messages, empty values, and status codes consistent, reducing mismatches between server responses and frontend expectations.
- Designing a REST API response structure
- Checking whether message and data fields are used consistently
- Choosing consistent responses for missing or empty data
doccker/cc-use-exp☆ 1.1KUpdated Aug 26, 2026
Review REST API response structures, status handling, null conventions, and business errors. For exports and downstream deliveries, check required fields before generating files or sending data, so missing values produce clear errors instead of apparently successful but unusable output.
- Reviewing API response fields and status codes
- Checking null and empty-list conventions
- Validating required data before file exports
doccker/cc-use-exp☆ 1.1KUpdated Aug 26, 2026
Use this skill when implementing safety checks in gateway, proxy, WAF, or CDN middleware. It explains how to combine HTTP status and response structure with strong and weak keyword signals, reducing false error detections in long user content.
- Reviewing proxy response error detection
- Handling Cloudflare or gateway terms in long text
- Designing keyword matching for middleware
doccker/cc-use-exp☆ 1.1KUpdated Aug 26, 2026
Design long-running API or data tasks as asynchronous jobs that return promptly and expose their status. The guidance covers duplicate triggers, expiring stored state, carrying request context into worker threads, and frontend progress polling so users can track completion.
- Turning a slow API operation into a background task
- Preventing repeated clicks from starting duplicate jobs
- Adding task status and progress polling
doccker/cc-use-exp☆ 1.1KUpdated Aug 26, 2026
Use this skill to write and maintain Bash commands in shell scripts, Dockerfiles, Makefiles, YAML files, and Markdown examples. It sets practical conventions for comments, variables, heredocs, file writing, paths, and safer command patterns.
- Writing or editing a Bash script
- Adding shell commands to a Dockerfile or Makefile
- Documenting Bash commands in Markdown
doccker/cc-use-exp☆ 1.1KUpdated Aug 26, 2026
Apply consistent conventions to Bash scripts and system commands, including quoted variables, explicit paths, safe file writing, and logging for complex commands. The guidance helps keep scripts easier to follow and maintain.
- Set conventions for a Bash script
- Review shell commands for safer path and variable handling
- Add logging to a complex command
doccker/cc-use-exp☆ 1.1KUpdated Aug 26, 2026