Audit codebase architecture against canonical doctrine and repository implementation.
npx skills add https://github.com/Deadpool042/Creatyss --skill docs-keeper
Please help me install this Agent Skill. Skill: docs-keeper Source: https://github.com/Deadpool042/Creatyss/tree/main/.agents/skills/docs-keeper Command: npx skills add https://github.com/Deadpool042/Creatyss --skill docs-keeper
This skill helps teams verify that architectural decisions and domain boundaries align with the canonical doctrine and the actual repository implementation.
Review the current architecture and doctrine alignment to generate a scoped improvement plan.
High-intent search queries and answers about installing and using this skill.
To audit architecture against canonical doctrine, compare the intended domain boundaries with the actual repository implementation. Identify deltas between doctrine and reality, then propose minimal, scoped actions to restore alignment.
Architectural boundary verification checks if domain alignments and cadrage of lots conform to canonical doctrine. You need it when identifying deltas between planned architecture and the real repository implementation.
Identify deltas between doctrine and repo by performing a targeted architectural audit. Compare domain alignments and boundaries in the codebase against the canonical doctrine to spot discrepancies.
Architectural audit requires canonical doctrine documents to function properly. Without predefined doctrine, the audit cannot identify deltas or propose scoped actions to restore domain alignment within the repository.
The best way to generate scoped improvement plans for architecture governance is to audit the repository against canonical doctrine. This identifies deltas and proposes minimal, targeted actions to restore alignment.
Verify domain alignment within your codebase by applying a targeted architectural audit. Compare the real repository implementation against canonical doctrine to identify deltas and propose scoped corrective actions.
DowwieOrchestrate multi-phase forensic analysis of AI agent frameworks to extract architectural patterns.
souki202Guide modular code changes with explicit interfaces for medium-to-large applications.
Destynova2Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.
cdalsoniiiEvaluate Go project architecture with automated fitness functions for layer boundaries, dependencies, and complexity.
