component-architect

To validate Claude Code component frontmatter, use a component governance skill that checks official docs and enforces standards before generating any skills, agents, or hooks. This pre-creation validation ensures your components are compliant from the start.

You can audit existing Claude Code components by scanning the ~/.claude directory to detect non-compliant files. The audit workflow identifies frontmatter issues and architecture deviations, then orchestrates subagent remediation to automatically fix the non-compliant components.

The one skill one agent architecture pattern enforces a clean separation of concerns by assigning a single specialized agent to each skill. This component governance approach improves reliability and maintainability when creating Claude Code workflows.

Yes, you need jq and pyyaml installed in your environment to enforce component standards. These dependencies are required to parse frontmatter and validate architecture patterns during the component validation and audit workflow.

Yes, you can automate remediation for non-compliant Claude Code hooks by spawning subagents to fix the detected files. The remediation orchestration applies frontmatter validation and architecture enforcement to correct deviations automatically.

You should run a component audit when your Claude Code workflow experiences reliability or maintainability issues. Scanning ~/.claude for non-compliant frontmatter and architecture pattern deviations helps identify components needing remediation before they cause failures.