component-architect

Validate Claude Code component frontmatter and enforce architecture standards.

7|3|Updated Jan 15, 2026

Search Tags:#automation #audit #hooks #remediation #validate #architecture-pattern #component-standards

Ready to run

npx skills add https://github.com/Zpankz/mcp-skillset --skill component-architect-zpankz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: component-architect
Source: https://github.com/Zpankz/mcp-skillset/tree/main/component-architect
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill component-architect-zpankz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Enforces official Claude Code component standards and orchestrates the one-skill-one-agent pattern to improve reliability and maintainability when creating skills, agents, commands, or hooks.

Core Features & Use Cases

Pre-Creation Validation: Check official docs before generating any component
Existing Component Audit: Scan ~/.claude for non-compliant components
Remediation Orchestration: Spawn subagents to fix non-compliant files
Architecture Enforcement: Apply the one skill = one specialized agent pattern to ensure clean separation of concerns

Quick Start

Initiate a project audit with the component-architect Skill to validate components or spawn remediation as needed.

Frequently Asked Questions about component-architect

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

FAQPage Schema

How do I validate Claude Code component frontmatter before creating new skills?▼

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.

How do I audit existing Claude Code components for non-compliant files?▼

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.

What is the one skill one agent architecture pattern in Claude Code?▼

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.

Do I need jq and pyyaml to enforce component standards?▼

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.

Can I automate remediation for non-compliant Claude Code hooks?▼

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.

When should I run a component audit on my Claude Code workflow?▼

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.