concept-audit

Audit codebases for conceptual integrity using Daniel Jackson's concept design methodology.

Updated May 3, 2026

Search Tags:#design #architecture #refactoring #audit #software #concepts

Ready to run

npx skills add https://github.com/druejaramillo/skills --skill concept-audit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

Conceptual Inventory: Identify and name the core user-facing concepts within a codebase or system description.
Composition Analysis: Evaluate how concepts interact, detecting synchronization issues and integrity violations.
Evidence-Based Auditing: Map code-level realizations (routes, tables, services) to conceptual boundaries to pinpoint design misfits.
Use Case: Use this when refactoring a legacy service to determine if a specific module is an independent concept or an overloaded implementation detail.

Quick Start

Use the concept-audit skill to analyze the current codebase and identify potential conceptual design flaws.

Frequently Asked Questions about concept-audit

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

FAQPage Schema

How do I audit software conceptual integrity and identify design decay?▼

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.

What is conceptual drift and how do I evaluate it during an architectural review?▼

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.

When should I use a concept design methodology for refactoring a legacy codebase?▼

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.

Does concept auditing work for analyzing service boundaries and system synchronization?▼

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.

What is the best way to map code-level realizations to conceptual boundaries?▼

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.

What are the limitations of using a conceptual inventory for system design audits?▼

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.