phylactery-standards

Codify Lich Protocol engineering standards for the Phylactery project.

Updated May 29, 2025

Search Tags:#architecture #governance #standards #engineering #invariants #mutation-testing #phylactery

Ready to run

npx skills add https://github.com/crozzbite/DnDApp --skill phylactery-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phylactery-standards
Source: https://github.com/crozzbite/DnDApp/tree/main/.agent/skills/phylactery-standards
Command: npx skills add https://github.com/crozzbite/DnDApp --skill phylactery-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codify and enforce high-integrity engineering standards to prevent architectural drift and ensure domain invariants across the Phylactery project.

Core Features & Use Cases

Invariant-first modeling: Domain models are immutable truths, with strict typing and complete invariants.
Observable use cases: Use cases orchestrate domain logic, are resilient with retries/backoff, and are infrastructure-agnostic.
Quality gates and governance: Mutation testing, hypothesis-based checks, and ADR governance ensure quality before merge.

Quick Start

Follow the Lich Protocol to audit and apply these standards in your codebase.

Frequently Asked Questions about phylactery-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are invariant-driven engineering standards for preventing architectural drift?▼

Invariant-driven engineering standards codify immutable domain truths and strict typing to prevent architectural drift, ensuring domain invariants remain intact across application and infrastructure layers during code reviews.

How do I enforce zero-dependency domain models and strict interfaces in code reviews?▼

Enforce zero-dependency domain models by applying the Lich Protocol during code reviews, verifying strict interfaces, structured logging, and complete invariants to ensure infrastructure-agnostic use cases.

Does mutation testing with ADR governance work for high-integrity engineering projects?▼

Mutation testing with ADR governance ensures quality before merge by applying hypothesis-based checks and architectural decision records, satisfying high-integrity engineering requirements across domain and infrastructure layers.

What is the best way to orchestrate observable use cases that are infrastructure-agnostic?▼

Orchestrate observable use cases by making them infrastructure-agnostic with built-in retries and backoff, ensuring they orchestrate domain logic independently while maintaining strict domain invariants.

Why does architectural drift happen and when do I need governance standards to stop it?▼

Architectural drift happens when domain invariants erode across layers; governance standards are needed when high-integrity projects require ADR-based governance, mutation testing, and strict interfaces to prevent quality degradation before merge.

Can I apply the Lich Protocol standards to existing codebases or only new projects?▼

Apply the Lich Protocol standards to audit existing codebases by checking invariant-first modeling, observable use cases, and quality gates, ensuring compliance across domain, application, and infrastructure layers.