Skip to content

imMamdouhaboammar/anti-slop-engineering / skills/repo-memory-and-invariant-steward

repo-memory-and-invariant-steward

Verified

Maintains the repository's architectural memory and enforces invariant preservation across sessions. Use when syncing historical decision records into a living compact Invariant Ledger, checking PRs/branches for architectural drift, verifying Gate 0 invariant constraints, or validating formal Reassessment Triggers — even if they don't explicitly say "invariant steward". Do NOT use for routine cosmetic edits or non-consequential scripts.

references/reassessment-protocol.md

View on GitHub
# Reassessment Trigger Protocol & Schema

> Formal protocol for proposing, reviewing, and approving modifications or retirement of active architectural invariants.

## Protocol Purpose

Invariants are permanent by default, but architectures must evolve. The Reassessment Protocol ensures that changes to architectural invariants are intentional, documented, and backed by evidence—never accidental.

## Reassessment Trigger Schema

A valid `reassessment-trigger.json` must contain:

```json
{
  "schema_version": "1.0.0",
  "target_invariant_id": "INV-PARANOID-IDEMPOTENCY",
  "action": "supersede | waive | deprecate",
  "justification": "Comprehensive explanation of why the existing invariant is being altered",
  "trade_off_delta": {
    "gain": "Concrete operational or performance improvement achieved",
    "risk": "Risk or edge cases introduced and how they are mitigated"
  },
  "authority": {
    "author": "Architect Name",
    "pr_or_issue": "PR or Issue reference",
    "approved_at": "ISO-8601 Timestamp"
  },
  "verification_proof": "Empirical evidence (e.g. load test result, security audit, benchmark) proving the new approach satisfies reliability requirements"
}
```

## Lifecycle Actions

1. **`supersede`**: Replaces the old invariant with a new, superior invariant. The old invariant status moves to `superseded` in the ledger upon merge.
2. **`waive`**: Grants a temporary scoped exception (e.g. for an isolated legacy migration or temporary prototype). Must include an issue milestone or expiry date.
3. **`deprecate`**: Marks the invariant as no longer enforced. The invariant remains in historical records with status `deprecated`.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall