Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Use when making .NET/framework pattern choices, UX/usability/accessibility decisions, infrastructure/operations changes, architecture decisions, or responding to requests that might conflict with best
Instruction file imported from becauseimclever/HouseholdLedger (.github/instructions/framework-aligned-engineering.instructions.md). Copyright stays with the author.
Framework-Aligned Engineering
Default to platform- and framework-supported mechanisms and established .NET practices over custom reimplementations.
Apply the same standard to usability, accessibility, infrastructure, operations, and architecture decisions.
Use engineering judgment rather than treating every departure from guidance as an approval gate. Explain a meaningful tradeoff when it affects maintainability, accessibility, security, data integrity, or operating cost, then proceed with the user's stated direction unless the action is destructive, irreversible, or still materially ambiguous.
Document architectural exceptions only when the decision is likely to surprise a future maintainer or has a lasting consequence. User direction remains authoritative.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/becauseimclever-householdledger-framework-aligned-engine-7b1b2e/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "becauseimclever-householdledger-framework-aligned-engine-7b1b2e",
"kind": "skill",
"name": "Framework-Aligned Engineering",
"description": "Use when making .NET/framework pattern choices, UX/usability/accessibility decisions, infrastructure/operations changes, architecture decisions, or responding to requests that might conflict with best practices.",
"publisher": "becauseimclever",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Use when making .NET/framework pattern choices, UX/usability/accessibility decisions, infrastructure/operations changes, architecture decisions, or responding to requests that might conflict with best practices."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/becauseimclever/HouseholdLedger",
"path": ".github/instructions/framework-aligned-engineering.instructions.md",
"ref": "e47da8b95e4585b976a5f0cc9ae839039f6ec956",
"url": "https://github.com/becauseimclever/HouseholdLedger/blob/e47da8b95e4585b976a5f0cc9ae839039f6ec956/.github/instructions/framework-aligned-engineering.instructions.md",
"key": "becauseimclever/HouseholdLedger/.github/instructions/framework-aligned-engineering.instructions.md"
},
"applies_to": "**"
},
"instructions": "# Framework-Aligned Engineering\r\n\r\n- Default to platform- and framework-supported mechanisms and established .NET practices over custom reimplementations.\r\n- Apply the same standard to usability, accessibility, infrastructure, operations, and architecture decisions.\r\n- Use engineering judgment rather than treating every departure from guidance as an approval gate. Explain a meaningful tradeoff when it affects maintainability, accessibility, security, data integrity, or operating cost, then proceed with the user's stated direction unless the action is destructive, irreversible, or still materia",
"cost": {
"context_tokens": 196
}
}
Fetch it by URL: GET /api/v1/registry/becauseimclever-householdledger-framework-aligned-engine-7b1b2e/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
