About platform-backend
platform-backend is a skill for backend API work. It emphasizes failing early with guard clauses, surfacing every error, and following a workflow to assess requests and validate actionable output.
Key features
- 01Fail early with guard clauses
- 02Log or propagate every error
- 03Check whether requests match the skill scope
- 04Follow a workflow to produce concrete output
- 05Review and refine results when needed
Use cases
- 01Design error handling for an API endpoint
- 02Plan validation for request data
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/platform-backendin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/endpoint-blueprint.mdrules/_sections.mdapi-authorization-vs-authentication.mdapi-output-schemas.mdapi-request-lifecycle.mdapi-select-sensitive-fields.mderror-domain-specific.mderror-http-codes.mdlogging-structured.mdsecurity-dont-expose-internals.mdsecurity-dont-log-secrets.mdsecurity-filter-by-tenant.mdsecurity-never-commit-secrets.mdsecurity-procedure-hierarchy.mdvalidation-at-boundary.mdvalidation-strict-schemas.mdDetails
From the project READMEPrinciples
- Throw early with guard clauses — fail fast at the top of functions
- Never swallow errors silently — log or propagate every failure
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-backendscope 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.
Comments
Markdown supported