minbzk-mijn-bureau-infra-documentation-instructions.ocm.json json {
"ocm": "1",
"id": "minbzk-mijn-bureau-infra-documentation-instructions",
"kind": "skill",
"name": "documentation",
"description": "Documentation Guidelines",
"publisher": "MinBZK",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Documentation Guidelines"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/MinBZK/mijn-bureau-infra",
"path": ".github/instructions/documentation.instructions.md",
"ref": "b2ae545013c153b9a3fb0aebcb51d22f348e1573",
"url": "https://github.com/MinBZK/mijn-bureau-infra/blob/b2ae545013c153b9a3fb0aebcb51d22f348e1573/.github/instructions/documentation.instructions.md",
"key": "MinBZK/mijn-bureau-infra/.github/instructions/documentation.instructions.md"
},
"applies_to": "**/*.md"
},
"instructions": "## Documentation Guidelines\n\n- Write clear and concise documentation.\n- Use consistent terminology and style.\n- Include examples where applicable.\n\n## Grammar\n\n- Use present tense verbs (is, open) instead of past tense (was, opened).\n- Write factual statements and direct commands. Avoid hypotheticals like \"could\" or \"would\".\n- Use active voice where the subject performs the action.\n- Write in second person (you) to speak directly to readers.",
"cost": {
"context_tokens": 111
}
}