SkillsAdd

smithery/neversight

component-architect

Enforces official Claude Code component standards. Use when creating skills, agents, commands, or hooks. Validates existing components and offers remediation. Implements the "one skill = one specialized agent" architecture pattern.

Installation

$ npx skills add smithery/neversight --skill component-architect
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

react:components Similar name
google-labs-code/stitch-skills

Converts Stitch designs into modular Vite and React components using system-level networking an…

50.7K installs
building-components Similar name
vercel/components.build

Guide for building modern, accessible, and composable UI components. Use when building new comp…

12.5K installs
next-cache-components-adoption Similar name
vercel/next.js

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when…

12.4K installs
next-cache-components-optimizer Similar name
vercel/next.js

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Componen…

11.8K installs
create-oo-component-documentation Similar name
github/awesome-copilot

Create comprehensive, standardized documentation for object-oriented components following indus…

7K installs
update-oo-component-documentation Similar name
github/awesome-copilot

Update existing object-oriented component documentation following industry best practices and a…

7K installs

Also in this package

Other skills from smithery/neversight · top by installs.

npx skills add smithery/neversight
zoom-meeting 0 ziwei-doushu 0 zimage-skill 0 zig 0 zhimeng-agent 0 zfc 0 zenbin 0 zeberg-salomon-rotator 0 zdev 0 youtube-transcript 0

Browse all from smithery/neversight

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Edit, Grep, Glob, Bash, WebFetch
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,900 B
  • docs SUMMARY.md 260 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Component Architect

Core Responsibilities

  1. Pre-Creation Validation: Check official docs before generating any component
  2. Existing Component Audit: Scan ~/.claude for non-compliant components
  3. Remediation Orchestration: Spawn subagents to fix non-compliant files
  4. Architecture Enforcement: Apply "one skill = one specialized agent" pattern

Official Frontmatter Reference

Component Required Optional
SKILL.md name, description allowed-tools, model, context, agent, hooks, user-invocable
Agent .md name, description tools, disallowedTools, model, permissionMode, skills, hooks
Command .md (none) description, allowed-tools, model, argument-hint
plugin.json name, description author
hooks.json hooks object description

Validation Commands

Validate All Components

/component-architect validate

Validate Specific Type

/component-architect validate --type skills
/component-architect validate --type agents
/component-architect validate --type hooks

Apply Architecture Pattern

/component-architect apply-pattern --skill skill-name

Architecture Pattern: One Skill = One Agent

For every active skill:

  1. Set context: fork in SKILL.md
  2. Create designated agent with matching name pattern
  3. Configure agent with:

- Intelligent model selection based on task complexity - Appropriate permissionMode for the workflow - Complementary skills that enhance the primary skill - Scoped hooks for lifecycle management - Restricted tools appropriate to the domain

Model Selection Matrix

Complexity Model Indicators
High opus Architecture, debugging, multi-domain reasoning
Medium sonnet Implementation, refactoring, moderate analysis
Low haiku Searches, simple transforms, quick lookups
Inherited inherit When parent context model is appropriate

Permission Mode Selection Matrix

Scenario Mode Use When
Complex multi-step plan High complexity requiring human feedback before implementation
Edge case handling acceptEdits Potential edge cases need user confirmation on edits
Routine execution bypassPermissions Clear requirements, preplanned, or promise completion
Standard workflow default Normal permission checking with prompts
Deny risky ops dontAsk Auto-deny prompts (explicitly allowed tools still work)

Remediation Workflow

  1. Scan component directories for non-compliant files
  2. Generate remediation plan per file
  3. Spawn parallel subagents for batch updates
  4. Verify all changes post-remediation

Integration References

  • [scripts/validate-component.sh](scripts/validate-component.sh) - PreToolUse validation
  • [scripts/log-component.sh](scripts/log-component.sh) - PostToolUse logging
  • [scripts/audit-components.py](scripts/audit-components.py) - Full audit script
  • [references/official-spec.md](references/official-spec.md) - Cached official docs