Audit codebases for conceptual integrity using Daniel Jackson's concept design methodology.
npx skills add https://github.com/druejaramillo/skills --skill concept-audit
Please help me install this Agent Skill. Skill: concept-audit Source: https://github.com/druejaramillo/skills/tree/main/concept-design/concept-audit Command: npx skills add https://github.com/druejaramillo/skills --skill concept-audit
This skill addresses the common issue of conceptual drift and design decay in software systems, helping teams identify overloaded concepts, hidden coupling, and missing abstractions that lead to maintenance debt.
Use the concept-audit skill to analyze the current codebase and identify potential conceptual design flaws.
High-intent search queries and answers about installing and using this skill.
You audit software conceptual integrity by mapping code-level artifacts like routes and tables to user-facing concepts to detect overloaded implementations and hidden coupling. This process identifies missing abstractions and synchronization issues causing maintenance debt.
Conceptual drift is the gradual decay of design integrity where implementation details overload original system concepts. You evaluate it by performing a composition analysis that maps codebase realizations to conceptual boundaries to pinpoint design misfits and integrity violations.
Use concept design methodology for refactoring a legacy codebase when you need to determine if specific modules are independent concepts or overloaded implementation details. It helps identify missing abstractions and hidden coupling before modifying system architecture.
Yes, concept auditing works for analyzing service boundaries by identifying state, actions, and synchronization boundaries within software systems. It produces evidence-backed findings that reveal integrity violations and composition issues across interacting architectural components.
The best way to map code-level realizations to conceptual boundaries is through evidence-based auditing that identifies routes, tables, and services, then evaluates them against user-facing concepts. This generates a read-only report highlighting design misfits and synchronization issues.
A limitation of using a conceptual inventory is that it produces a read-only report with recommendations, meaning it identifies design flaws and conceptual drift but does not automatically refactor code or resolve hidden coupling and overloaded implementations directly.
simonwjacksonMaps modules, primary callers, and key domain concepts from code.
anthony-chaudharyMap overloaded code tokens to distinct grounded concepts and generate GitHub issues.
agnaldo4jDetect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.
i3ringitAnalyzes code changes to validate architectural integrity and component boundaries during PR reviews, refactors, or feature additions.
