out-dev-kortexa-backend-instructions.ocm.json json {
"ocm": "1",
"id": "out-dev-kortexa-backend-instructions",
"kind": "skill",
"name": "backend",
"description": "Backend-specific guidance:",
"publisher": "out-dev",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Backend-specific guidance:"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/out-dev/kortexa",
"path": ".github/instructions/backend.instructions.md",
"ref": "54bc6a99f389f4b05c83519cc436d0f280cbfe66",
"url": "https://github.com/out-dev/kortexa/blob/54bc6a99f389f4b05c83519cc436d0f280cbfe66/.github/instructions/backend.instructions.md",
"key": "out-dev/kortexa/.github/instructions/backend.instructions.md"
},
"applies_to": "backend/**/*.cs,backend/**/*.csproj,backend/**/*.props,backend/**/*.targets,backend/**/*.json,backend/**/*.yaml,backend/**/*.yml"
},
"instructions": "Backend-specific guidance:\n\n- Follow existing ASP.NET patterns already used in backend/src and backend/tests.\n- Prefer dependency injection and existing service abstractions over direct static usage.\n- Keep controllers/endpoints thin; place business logic in services.\n- Add or update unit/integration tests for behavior changes.\n- Keep appsettings changes environment-safe and avoid hard-coded secrets.\n- For API contract changes, ensure DTOs, validation, and tests stay aligned.",
"cost": {
"context_tokens": 120
}
}