d-o-hub/rust-self-learning-memory

architecture-validation

Dynamically validate that the implemented codebase matches architectural decisions documented in plan files. Use when validating implementation matches planning documents, checking for architecture drift, or preparing for architecture reviews.

First seen Feb 21, 2026

Installation

$ npx skills add d-o-hub/rust-self-learning-memory --skill architecture-validation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from d-o-hub/rust-self-learning-memory · top by installs.

npx skills add d-o-hub/rust-self-learning-memory

Browse all from d-o-hub/rust-self-learning-memory

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 12
License LICENSE
Default branch main
Open issues 3
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,853 B
  • docs SUMMARY.md 274 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 37 installs

SKILL.md

Architecture Validation Skill

Dynamically validate that the implemented codebase matches architectural decisions documented in plan files.

Quick Reference

  • [Dimensions](dimensions.md) - What gets validated (components, dependencies, APIs, etc.)
  • [Workflow](workflow.md) - Step-by-step validation process
  • [Extraction Patterns](extraction.md) - How to extract architectural elements from plans
  • [Compliance](compliance.md) - Compliance levels and report format
  • [Self-Learning](self-learning.md) - Continuous improvement framework

Purpose

Generic, adaptive framework that:

  • Discovers all plan files in plans/ directory
  • Extracts architectural requirements dynamically
  • Validates implementation compliance
  • Reports gaps, drift, and violations

Key Principle: Be architecture-agnostic. Work with ANY project structure.

When to Use

  • Validating implementation matches planning documents
  • Checking for architecture drift after development
  • Ensuring design decisions are followed
  • Identifying missing implementations
  • Preparing for architecture reviews
  • Verifying refactoring didn't break boundaries

Validation Workflow

  1. Discover - Find all plan files
  2. Extract - Pull architectural elements
  3. Analyze - Compare vs codebase
  4. Validate - Check compliance
  5. Gap Analysis - Identify missing/drift/extra
  6. Report - Generate comprehensive report

See [workflow.md](workflow.md) for detailed phases and [dimensions.md](dimensions.md) for validation categories.