agentsclimarketplace
Sign in

Architecture

Skill ariaxhan/kernel-claude/skills/architecture

System architecture and design patterns. Modular design, interface stability, dependency management, AI-code health nexus. Triggers: architecture, design, structure, modules, dependencies, coupling, system design.From its SKILL.md

Install
npx -y skills add ariaxhan/kernel-claude --skill architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

<skill id="architecture"> <purpose> Architecture is about managing change over time. Good architecture makes easy things easy and hard things possible. AI-generated code amplifies existing patterns—good or bad. </purpose> <prerequisite> Understand existing codebase structure before proposing changes. Check for established patterns. Follow them unless explicitly changing. </prerequisite> <reference> Skill-specific: skills/architecture/reference/architecture-research.md </reference>

<core_principles>

  1. FOLLOW EXISTING PATTERNS: Don't introduce new patterns without justification.
  2. INTERFACE STABILITY: Changing interfaces breaks everything. Stabilize them first.
  3. MODULAR BOUNDARIES: Clear separation. Each module has one reason to change.
  4. DEPENDENCY DIRECTION: Depend on abstractions, not concretions. Core doesn't know about edges.
  5. SMALLEST CHANGE: Prefer minimal changes that achieve the goal. </core_principles>

<ai_code_health_nexus> From research: 30%+ defect risk when AI applied to unhealthy code. AI amplifies existing patterns. If code is messy, AI makes it messier. Before adding AI to a codebase:

  1. Identify health score (coupling, complexity, test coverage)
  2. Fix critical health issues first
  3. Establish clear interfaces
  4. Then apply AI within those boundaries </ai_code_health_nexus>

<design_heuristics>

  • If you can't explain it simply, the design is too complex
  • Three concrete examples before abstraction
  • Composition over inheritance
  • Make illegal states unrepresentable
  • Parse, don't validate </design_heuristics>

<anti_patterns>

  • Premature abstraction (abstract before 3 concrete uses)
  • Leaky abstractions (implementation details bleeding through)
  • Circular dependencies
  • God objects (one class doing everything)
  • Feature envy (methods that use another class more than their own) </anti_patterns>

<on_complete> agentdb write-end '{"skill":"architecture","decision":"X","coupling_reduced":true,"adr":"path|none"}' </on_complete>

</skill>

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.