syntropic137/software-leverage-points

maintaining-software-leverage-points

Use when maintaining the plugin chassis (not the SLP content): bumping versions, regenerating catalogs, running QA, configuring CI, shipping releases, or onboarding a contributor to the repo's automation surface.

원문 언어: 영어

architecture

Use when reviewing architectural concerns: module boundaries, dependency direction, layer discipline, bounded-context isolation, ADR coverage, premature abstraction, and structural fitness for change

원문 언어: 영어

documentation

Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs

원문 언어: 영어

logging

Use when reviewing logging concerns: structured-vs-unstructured logs, log-level policy, secret and PII redaction, correlation IDs in distributed systems, log/trace linkage, print statements in production code paths

원문 언어: 영어

testing

Use when reviewing testing concerns: pyramid coverage (unit, integration, E2E), test code quality, TDD discipline, regression discipline, FIRST principles, feedback-loop speed

원문 언어: 영어

authoring-skills

Use when authoring or auditing a Claude skill (`SKILL.md` with YAML frontmatter), refining an existing skill, or reviewing a skill against a chassis. Trigger phrases include "write a skill", "author a skill", "audit this skill", "review the skill", "skill…

원문 언어: 영어

software-leverage-review

Use when reviewing a plan document, PR diff, or codebase against multiple software leverage points in parallel; before implementation; during code review

원문 언어: 영어

skill-auditor

Use when reviewing whether a plugin's leverage-point skills still match the codebase or its own documentation; detect drift between SKILL.md claims and current state

원문 언어: 영어

skill-builder

Use when bootstrapping leverage-point skills in a target repo, or when the user asks to "create skills" or "set up leverage skills" in a project

원문 언어: 영어

authoring-software-leverage-points

Use when authoring or refining any skill in the software-leverage-points plugin (the 17 SLPs, the 3 operator skills, operator-synthesis references, or L2 templates). Captures the architectural model, the section shape per skill type, the cross-reference and…

원문 언어: 영어

configuration

Use when reviewing configuration concerns: env-var layering, typed config objects, startup validation, secret/non-secret separation, schema discoverability, environment-dependent defaults, twelve-factor compliance, magic numbers

원문 언어: 영어

continuous-delivery

Use when reviewing delivery concerns: DORA four key metrics, pre-merge gating, trunk-based development, fast feedback, single-artifact promotion, health-gated deploys, automated rollback, deploy/release decoupling via feature flags, deploy frequency, runbook…

원문 언어: 영어

dependencies

Use when reviewing dependency concerns: lockfile health, version pinning, immutable references, maintenance signals, transitive audit gates, monorepo version skew, reviewable lockfiles, license posture

원문 언어: 영어

developer-experience

Use when reviewing developer-experience concerns: single-command onboarding (contributors and end-users), inner-loop speed, task-runner discoverability, recipe-as-thin-wrapper discipline, error-message actionability, formatter/linter automation, AI-agent…

원문 언어: 영어

dry

Use when reviewing DRY concerns: knowledge-vs-text duplication, repeated business rules across boundaries, magic constants, configuration duplication, copy-pasted test fixtures, premature abstraction risk, rule-of-three for extraction

원문 언어: 영어

environments

Use when reviewing environment concerns: dev/staging/prod parity, declarative environment manifests, build vs runtime separation, environment promotion path, secret-loader parity across environments, reproducible local setup, ephemeral / preview environments…

원문 언어: 영어

error-handling

Use when reviewing error-handling concerns: error taxonomy, propagation discipline, swallow-vs-crash, retry semantics with backoff and idempotency, exit codes as API, error messages as contract, cause-chain preservation

원문 언어: 영어

principles-and-patterns

Use when reviewing cross-cutting design principles: SOLID applicability, separation of concerns, dependency direction, composition vs inheritance, coupling and cohesion, OO-vs-functional style consistency, pattern enforcement style, project-level…

원문 언어: 영어

purpose-and-scope

Use when reviewing purpose-and-scope concerns: stated project purpose, declared in-scope and out-of-scope, non-goals, plan-purpose alignment, scope-creep within a single change, project-level bounded contexts, dependency-purpose linkage

원문 언어: 영어

security

Use when reviewing security concerns: secrets in code, SAST coverage, input validation, authn/authz boundaries, sensitive-data handling, dependency CVEs, SSRF, hand-rolled escaping, threat modeling for high-stakes changes, defense in depth, agentic-AI / LLM…

원문 언어: 영어

software-complexity

Use when reviewing software complexity concerns: cognitive load, cyclomatic and cognitive complexity bounds, deep-vs-shallow modules, accidental coupling, premature abstraction, asymmetric simplicity, comments-explain-why

원문 언어: 영어

types

Use when reviewing type-system concerns: type-coverage in public APIs, primitive obsession vs refinement, runtime validation at trust boundaries, soundness gaps and escape hatches, narrow vs wide types, strict-mode discipline

원문 언어: 영어

versioning

Use when reviewing versioning concerns: declared scheme (semver/calver/ZeroVer), changelog hygiene, deprecation policy and migration paths, public-API stability classification, version-bump automation, manifest-drift across multiple files, release process…

원문 언어: 영어