architecture-foundations

Plugin architecture-foundations from marketplace kaizen-plugins in kaizenanalytix/kaizen-claude-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• clean-architecture

  Applies a framework-agnostic three-zone model (core, modules, shared) for organizing any application's codebase, and enforces a one-way dependency flow between zones so business domains stay decoupled and reusable code stays free of business logic. This skill should be used when the user asks to "st

• existing-codebase-adoption

  Decides, once and explicitly, whether to impose this suite's conventions for a given discipline on a project that already has its own existing structure, or to defer to that structure instead — then records the decision so later work stays consistent, and keeps handling one-off inconsistencies disco

• project-kickoff

  Orchestrates the start of a brand-new project end to end — asks the shape of the build up front, establishes the design system before any component exists, then routes to the framework bootstrap, the architecture skeleton, the API contract, and finally seeds the codebase-map cache. Writes nothing in

• state-philosophy

  Applies the framework-agnostic distinction between server state (remote data fetched and cached locally, subject to staleness and invalidation) and client/UI state (session-local state genuinely owned by the app), and the general concepts of cache invalidation and optimistic updates. This skill shou

• test-pyramid

  Applies the tooling-agnostic test pyramid — unit, integration, and end-to-end/contract tests — to decide what kind of test a given piece of behavior needs and in what proportion each layer should be written. This skill should be used when the user asks "what should I test", "testing strategy", "test

• ui-architecture

  Applies the three-zone model (core/modules/shared) specifically to a UI application, in framework-neutral terms — no React, Vue, Angular, or any other library vocabulary. Use for a UI codebase whose framework is unknown, not yet chosen, or has no adapter skill in this suite, when the user asks thing

• working-agreement

  How work gets done regardless of stack: verification is batched and asked for rather than run continuously, pre-existing problems found near a change are surfaced rather than silently fixed, a model tier is recommended at decision points, and no implementation detail is assumed without checking exis

Hooks (2)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/working-agreement.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/adoption-gate.js"

Similar plugins