backend-runtime-governance
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when changing backend route placement, service boundaries, runtime ownership, or backend docs/tests alignment.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with backend-api-contracts and backend-agents-operons.
- Distinctive: line 56
Keep backend tests and backend docs aligned with runtime changes.
- Very specific: line 58
Treat consent validation, trust, and audit rules as security-audit concerns when they become the primary boundary.
- Very specific: line 59
Treat uv as the canonical Python toolchain for contributor and CI flows.
- Very specific: line 61
When a backend runtime failure is visible in UAT or CI, use ./bin/hushh agents rca --surface runtime --text or --surface uat --text first …
- Very specific: line 66
If the request is still broad or ambiguous, route it back to backend.
- Very specific: line 67
If the task is primarily a proxy/backend wire contract, use backend-api-contracts.
- Very specific: line 68
If the task is primarily about agents or operons, use backend-agents-operons.
- Very specific: line 69
If the task becomes trust/IAM/vault policy work, route to security-audit.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Backend Runtime Governance Skill
Purpose and Trigger
- Primary scope:
backend-runtime-governance - Trigger on backend route placement, service boundaries, runtime ownership, and backend runtime docs/tests alignment.
- Avoid overlap with
backend-api-contractsandbackend-agents-operons.
Coverage and Ownership
- Role:
spoke - Owner family:
backend
Owned repo surfaces:
consent-protocol/apiconsent-protocol/hushh_mcp/servicesconsent-protocol/hushh_mcp/integrationsconsent-protocol/tests/services
Non-owned surfaces:
backendsecurity-auditrepo-operations
Do Use
- Route and service placement decisions inside the backend runtime.
- Runtime ownership boundaries between routes, services, and integrations.
- Aligning backend runtime docs and service-layer tests with implementation changes.
- Reviewing runtime DB table ownership, data-class posture, retention policy, and access paths when backend migrations or services add durable state.
Do Not Use
- Broad backend intake where the correct spoke is still unclear.
- Agent/operon orchestration work.
- Proxy contract work that primarily belongs to API contracts.
Read First
docs/architecture/system.mddocs/development/contracts/api-contracts.mdconsent-protocol/docs/README.md.agents/skills/backend-runtime-governance/references/async-runtime-performance.mddocs/architecture/schema-migration-discipline.md
Workflow
- Confirm the runtime boundary before moving code between routes, services, or integrations.
- Keep backend tests and backend docs aligned with runtime changes.
- For any migration or durable service table, confirm the runtime DB data-plane contract declares owner, data class, primary access path, expected row growth, retention policy, deletion behavior, and plaintext/ciphertext posture.
- Treat consent validation, trust, and audit rules as
security-auditconcerns when they become the primary boundary. - Treat
uvas the canonical Python toolchain for contributor and CI flows;requirements*.txtare generated runtime artifacts, not the source of dependency truth. - For backend bootstrap, packaging, or runtime-governance changes, rerun the authoritative service checks once directly and once again through the canonical repo entrypoint.
- When a backend runtime failure is visible in UAT or CI, use
./bin/hushh agents rca --surface runtime --textor--surface uat --textfirst so service fixes are anchored to the blocking runtime classification instead of log-chasing. - For slow or intermittently "unreachable" endpoints, run the async runtime performance health check before editing: confirm whether the asyncio event loop is blocked by a synchronous call (DB client, external SDK) rather than a slow DB, then apply the
run_in_threadpool/asyncio.to_threadoffload and the layered caching strategy inreferences/async-runtime-performance.md. Never call the synchronousdb/db_client.pyclient or a blocking SDK directly from anasync defhandler.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
backend. - If the task is primarily a proxy/backend wire contract, use
backend-api-contracts. - If the task is primarily about agents or operons, use
backend-agents-operons. - If the task becomes trust/IAM/vault policy work, route to
security-audit.
Required Checks
cd consent-protocol && python3 -m pytest tests/services -q
./bin/hushh agents data-model-auditDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

