Skill

platform-backend

Guides server-side architecture and security: API design, error handling with fail-fast guards, validation, logging. Use for building APIs, server logic, or backend security reviews.

backend

security

npx claudepluginhub ravnhq/ai-toolkit

Tool Access

This skill is limited to using the following tools:

BashReadWriteEditGrepGlobAgent

Preview

- Throw early with guard clauses — fail fast at the top of functions

Supporting Assets

references/endpoint-blueprint.mdrules/_sections.mdrules/api-authorization-vs-authentication.mdrules/api-output-schemas.mdrules/api-request-lifecycle.mdrules/api-select-sensitive-fields.mdrules/error-domain-specific.mdrules/error-http-codes.mdrules/logging-structured.mdrules/security-dont-expose-internals.mdrules/security-dont-log-secrets.mdrules/security-filter-by-tenant.mdrules/security-never-commit-secrets.mdrules/security-procedure-hierarchy.mdrules/validation-at-boundary.mdrules/validation-strict-schemas.md

SKILL.md

Similar Skills

api-security-best-practices

36.4k

Implements secure API patterns: authentication (JWT/OAuth/API keys), authorization (RBAC), input validation, rate limiting, and defenses against injection/DDoS/OWASP Top 10 for REST/GraphQL/WebSocket APIs.

antigravity-awesome-skills

api-error-handling

180

Implements API error handling with standardized responses, logging, monitoring, retry logic, circuit breakers, and validation patterns for Node.js and Python APIs.

4 files

aj-geddes-useful-ai-prompts-4

backend

Guides backend tasks like REST/GraphQL API design, database query optimization, authentication, microservices building, code review, migrations, and load testing across detected stacks.

3 files

ucai

Stats

Stars14

Forks12

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Rules

See rules index for detailed patterns.

Examples

Positive Trigger

User: "Design error handling and validation strategy for this API endpoint."

Expected behavior: Use platform-backend guidance, follow its workflow, and return actionable output.

Non-Trigger

User: "Create a Tailwind design token scale."

Expected behavior: Do not prioritize platform-backend; choose a more relevant skill or proceed without it.

Troubleshooting

Skill Does Not Trigger

Error: The skill is not selected when expected.

Cause: Request wording does not clearly match the description trigger conditions.

Solution: Rephrase with explicit domain/task keywords from the description and retry.

Guidance Conflicts With Another Skill

Error: Instructions from multiple skills conflict in one task.

Cause: Overlapping scope across loaded skills.

Solution: State which skill is authoritative for the current step and apply that workflow first.

Output Is Too Generic

Error: Result lacks concrete, actionable detail.

Cause: Task input omitted context, constraints, or target format.

Solution: Add specific constraints (environment, scope, format, success criteria) and rerun.

Workflow

Identify whether the request clearly matches platform-backend scope and triggers.

Apply the skill rules and referenced guidance to produce a concrete result.

Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.

Principles

Throw early with guard clauses — fail fast at the top of functions
Never swallow errors silently — log or propagate every failure