8Dionysus/aoa-property-invariants
.agents/skills/aoa-property-invariants/SKILL.md
Express stable system or domain truths as invariant-oriented tests or checks rather than only fixed examples. Use when correctness depends on behavior that should hold across many inputs or states, such as monotonicity, idempotency, conservation, or structural rules. Do not use when no meaningful invariant is known yet or when the real task is auditing existing coverage instead of writing the properties.
$ install --global
skillsauthnpx skillsauth add 8Dionysus/aoa-skills aoa-property-invariantsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:32 PM3.6s1 file scanned
SKILL.md
- name:
- aoa-property-invariants
- description:
- Express stable system or domain truths as invariant-oriented tests or checks rather than only fixed examples. Use when correctness depends on behavior that should hold across many inputs or states, such as monotonicity, idempotency, conservation, or structural rules. Do not use when no meaningful invariant is known yet or when the real task is auditing existing coverage instead of writing the properties.
- license:
- Apache-2.0
- compatibility:
- Designed for Codex or similar coding agents with repository file access and an interactive shell. Network access is optional and only needed when repository validation or referenced workflows require it.
- aoa_scope:
- core
- aoa_status:
- canonical
- aoa_invocation_mode:
- explicit-preferred
- aoa_source_skill_path:
- skills/aoa-property-invariants/SKILL.md
- aoa_source_repo:
- 8Dionysus/aoa-skills
- aoa_technique_dependencies:
- AOA-T-0017,AOA-T-0007
- aoa_portable_profile:
- codex-facing-wave-3
aoa-property-invariants
Intent
Use invariant-oriented thinking to test broad behavior through properties rather than only through a short list of fixed examples.
Trigger boundary
Use this skill when:
- a rule should hold across many inputs or states
- examples alone feel too narrow
- the system has conservation, monotonicity, idempotency, or structural invariants
- safety or correctness depends on broad input coverage
Do not use this skill when:
- the behavior is mostly about presentation details or narrow snapshots
- the main problem is checking whether existing checks really cover the invariant; use
aoa-invariant-coverage-auditfirst - the main problem is a boundary contract rather than a stable invariant; use
aoa-contract-test - no meaningful invariant is yet understood
Inputs
- target rule or domain truth
- current examples or tests
- input space or generators
- known edge cases
Outputs
- explicit invariants
- property-oriented tests or checks
- notes on generator assumptions
- verification summary
Procedure
- identify what must remain true across many cases
- separate strong invariants from weak hopes or vague expectations
- express those invariants as property-oriented tests or repeated checks
- keep the generators or inputs bounded and reviewable
- run the checks and report what properties now constrain behavior
Contracts
- each property should express a real invariant, not a wish
- the test should broaden coverage beyond a small handpicked set
- generator assumptions should remain understandable
Risks and anti-patterns
- writing weak properties that prove almost nothing
- confusing random data with meaningful coverage
- letting overly broad generators or harness complexity hide the protected domain truth
- using polished invariant language while the actual stable truth remains underspecified
- using property checks where a small set of concrete examples would be clearer
- using invariant language to avoid naming the actual rule or boundary that matters
Verification
- confirm the property expresses a meaningful invariant
- confirm the invariant broadens coverage beyond fixed examples
- confirm the report names which stable truth was violated or protected, not only that generated inputs failed
- confirm the result is understandable to another human or agent
Technique traceability
Manifest-backed techniques:
- AOA-T-0017 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/evaluation/property-invariants/TECHNIQUE.mdand sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation - AOA-T-0007 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/evaluation/signal-first-gate-promotion/TECHNIQUE.mdand sections: summary, Validation
Adaptation points
Project overlays should add:
- local generator tools
- domain-specific invariants
- rules for when property-based checks are mandatory, optional, or out of scope
Related Skills
8Dionysus/aoa-decision
testing
VerifiedTrustedCommunity
--- name: aoa-decision scope: core status: evaluated summary: Route AoA decision-lane work through the workspace decision graph first, then hand off to the smallest find, create, or correct subskill while keeping repo-local decision files authoritative. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0033 - AOA-T-0002 --- # aoa-decision ## Intent Use this skill as the front door for AoA `docs/decisions/` work. It decides whether the task is to find, create, or correct
4SKILL.mdUpdated Jun 5, 2026
8Dionysus/aoa-decision-find
testing
VerifiedTrustedCommunity
--- name: aoa-decision-find scope: core status: evaluated summary: Find AoA decision records through the workspace graph, then verify claims against repo-local source notes and generated decision indexes. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0002 --- # aoa-decision-find ## Intent Use this skill to find decision rationale quickly across AoA repositories while keeping final claims grounded in the owning repository's authored decision note. ## Trigger boundary
4SKILL.mdUpdated Jun 5, 2026
8Dionysus/aoa-decision-create
tools
VerifiedTrustedCommunity
--- name: aoa-decision-create scope: core status: evaluated summary: Create a new AoA decision record in the owning repository by using graph context for placement and repo-local decision law for the actual source note and indexes. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0033 - AOA-T-0002 --- # aoa-decision-create ## Intent Use this skill when a real structural, workflow, tooling, source/export, or authority decision needs a durable repo-local `docs/decisions/`
4SKILL.mdUpdated Jun 5, 2026
8Dionysus/aoa-decision-correct
development
VerifiedTrustedCommunity
--- name: aoa-decision-correct scope: core status: evaluated summary: Correct, supersede, or reindex AoA decision records by editing source notes first, rebuilding repo-local indexes, and refreshing the workspace decision graph. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0001 - AOA-T-0033 - AOA-T-0002 --- # aoa-decision-correct ## Intent Use this skill to repair an existing decision record, its index metadata, supersession links, source-surface list, or generate
4SKILL.mdUpdated Jun 5, 2026