quality-contracts
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when changing cross-surface verification policy, contract-test placement, test selection, or quality gates across frontend and backend.
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
- backend-runtime-governanceSkill
- 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
- 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
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with streaming-contracts and repo-operations.
- Distinctive: line 33
Test selection and contract-test placement decisions.
- Distinctive: line 53
Start from the contract or user-visible behavior that needs proof.
- Distinctive: line 55
Keep frontend and backend contract tests aligned with the same user-visible or policy-visible rule.
- Distinctive: line 56
Do not add one-time, manual, skipped-by-default, or source-string tests to routine suites when a reusable runtime helper, component test, …
- Very specific: line 59
Use Playwright only when a real browser is required.
- Very specific: line 61
Treat CI pipeline ownership as repo-operations unless the primary question is what should be verified.
- Distinctive: line 63
When changing required test sets or gate policy, prove the changed contract through its canonical entrypoint.
- Distinctive: line 64
Treat helper-only drift as advisory unless it weakens runtime, deploy, or test authority.
- Distinctive: line 75
Use focused or release validation for the changed contract and adjacent callers.
≈ “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 Quality Contracts Skill
Purpose and Trigger
- Primary scope:
quality-contracts - Trigger on contract-test placement, test selection, route/browser verification, and cross-surface quality rules.
- Avoid overlap with
streaming-contractsandrepo-operations.
Coverage and Ownership
- Role:
spoke - Owner family:
security-audit
Owned repo surfaces:
docs/development/qualityhushh-webapp/__tests__consent-protocol/tests
Non-owned surfaces:
security-auditfrontendbackend
Do Use
- Test selection and contract-test placement decisions.
- Cross-surface verification policy and quality-gate ownership.
- Reviewing whether a change is missing authoritative checks.
Do Not Use
- Broad security intake where the correct spoke is unclear.
- Repo-wide CI/deploy operations work.
- Narrow streaming-protocol work when the issue is clearly streaming only.
Read First
docs/development/quality/README.mddocs/development/quality/pr-impact-checklist.mddocs/architecture/finance/kai-runtime-smoke-checklist.md.agents/skills/quality-contracts/references/browser-verification-contract.mddocs/development/quality/definition-of-done.md
Workflow
- Start from the contract or user-visible behavior that needs proof.
- Select the smallest authoritative checks across frontend, backend, route, data, and browser surfaces.
- Keep frontend and backend contract tests aligned with the same user-visible or policy-visible rule.
- Do not add one-time, manual, skipped-by-default, or source-string tests to routine suites when a reusable runtime helper, component test, service test, or script-first smoke proves the behavior.
- Source-reading contract tests are allowed only for explicit architecture boundaries with no cheaper runtime surface; delete them when behavior-level coverage becomes available.
- Legacy, migration, and compatibility tests stay only while they protect a live compatibility/removal boundary; otherwise delete or move the durable fact into the canonical contract.
- Use Playwright only when a real browser is required; follow
browser-verification-contract.mdfor protected routes. - For signed-in, vault, PKM, Email Helper, consent, or app-review proof, resolve the reviewer from runtime env (
REVIEWER_UID; deprecated aliases only as migration fallbacks) and assert the browser session, vault owner, workflow owner, and PKM data owner are the same user. Do not validate against copied recipients, counterparty labels, admin fixtures, or a hardcoded UID/email. - Treat CI pipeline ownership as
repo-operationsunless the primary question is what should be verified. - For new tables or data-contract changes, include the repo data-model audit.
- When changing required test sets or gate policy, prove the changed contract through its canonical entrypoint; do not duplicate the same selected identities in a separate direct run. Qualify the completed combined candidate once with retained functional/core checks plus affected boundaries; reuse unchanged evidence.
- Treat helper-only drift as advisory unless it weakens runtime, deploy, or test authority.
Handoff Rules
- Broad or ambiguous security work routes back to
security-audit. - CI or deploy pipeline ownership routes to
repo-operations. - Streaming-specific contract work routes to
streaming-contracts. - Pure frontend or backend implementation routes to
frontendorbackend.
Required Checks
Use focused or release validation for the changed contract and adjacent callers. Diagnostic runs the historical full set. Missing change metadata stays conservative. Explicit browser diagnostics own browser proof, and native changes require native verification. Keep live security, consent, schema and core deployment gates blocking. Secondary feature diagnostics report their actual outcome separately; no diagnostic run is not a pass. Follow the CI readiness policy.
cd hushh-webapp && npm run test:ci
cd hushh-webapp && npm run verify:service-boundary
cd consent-protocol && python3 -m pytest tests/quality -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.

