Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

ln-23-system-design-proposal-builder

Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.

levnikolaevich · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add levnikolaevich/claude-code-skills --skill ln-23-system-design-proposal-builder

About this skill


name: ln-23-system-design-proposal-builder description: "Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement."

System Design Proposal Builder

Goal: Create a proportionate, evidence-backed target system design that turns requirements into explicit boundaries, contracts, data flow, failure behavior, operations, and tradeoffs. Change only the approved design document; do not implement, audit, or approve the delivery.

Execution contract: The ordered checkboxes are the Definition of Done. Track every item internally as PENDING, PROVEN with concrete evidence, CLEARED with evidence that its condition is absent, or UNPROVEN with a gap; reading, delegation, or tool failure is not proof. Reconcile items after each section. Before returning, resolve all PENDING and count only PROVEN and CLEARED; apply the skill's verdict and approval rules to every gap. Preserve user intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without silently skipping checks. Preserve dependency and safety ordering; otherwise choose the verification method appropriate to each obligation. Treat equivalent user or repository evidence as valid input; another skill, named artifact, or complete lifecycle is not a prerequisite. Preserve source requirement and decision identifiers when available. Bind reused evidence to the relevant source version, dirty changes, configuration, and environment; invalidate only affected claims after a change. On continuation, reconcile the task, existing authorization, current state, and unresolved evidence before resuming. For long work, return a compact continuation record or update an already authorized task artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and authority to perform an external action. Prepare authorized work before any required approval. If an instruction prevents progress, identify its exact source and explain the unresolved boundary; do not invent an approval gate from general caution.

Tool Routing

NeedPreferred capabilityFallback
Requirements and constraintsApproved requirements, baseline, decisions, and direct stakeholder inputMark material gaps and ask the smallest decision question
Current implementation and conventionsRepository search, manifests, entrypoints, and architecture artifactsTreat as greenfield only when the user or repository establishes that fact; otherwise mark current state UNKNOWN and return REVISE or BLOCKED when the gap can change boundaries, compatibility, or migration
External capabilities and limitsCurrent official documentation and specificationsMark claims UNVERIFIED; avoid vendor-dependent commitment
EstimatesReproducible arithmetic from sourced workload assumptionsUse ranges and sensitivity; never present estimates as measurements
Document mutationMinimal patch to the approved target-design artifactReturn BLOCKED if scope or path is unsafe

Use patterns as candidate solutions, not goals. Introduce infrastructure only when a requirement, failure mode, ownership boundary, or measured horizon pays for its lifecycle cost.

Artifact Rules

  • Reuse a clear target-design document; otherwise use docs/architecture/target-design.md.
  • Read available baseline, current-state, decision, interface, diagram, and migration artifacts by path; none is mandatory.
  • Label facts, assumptions, estimates, proposed decisions, and unresolved choices separately.
  • Compare credible alternatives for consequential decisions, including the simplest feasible option; when constraints permit only one, document why rather than inventing another.
  • Prefer reversible choices and the simplest topology fitting the system. For a new application, consider a modular monolith before independent services; do not force that shape onto libraries, plugins, or an established topology.
  • Do not silently change an accepted decision; record the conflict and required governance action.

Checklist

1. Frame the Design

  • Resolve business outcome, actors, journeys, scope, non-goals, horizon, readers, language, and the approved canonical destination before editing.
  • Read repository instructions and inspect relevant architecture artifacts and current implementation.
  • Extract functional requirements and measurable quality drivers, preserving their source and status.
  • Identify architecture-critical unknowns and ask only questions whose answers change the target shape.
  • Return BLOCKED when a required business boundary or safety constraint cannot be responsibly assumed.

2. Estimate Before Choosing Components

  • Estimate average and peak request or event rates, concurrency, payload and bandwidth, storage growth, retention, and recovery volume where relevant.
  • Show formulas, ranges, growth horizon, and assumptions; identify the variables that can reverse a choice.
  • Identify likely first bottlenecks and explicit thresholds for deferred scaling mechanisms.
  • Separate availability, latency, durability, consistency, security, cost, and operability requirements from implementation preferences.
  • Reject speculative scale and list complex mechanisms intentionally deferred.

3. Define Domains, Data, and Contracts

  • Map business capabilities, domains or modules, ownership, invariants, and allowed dependency direction.
  • Define systems of record, data models at architecture depth, lifecycle, retention, consistency, and transaction boundaries.
  • Define public APIs, events, commands, schemas, errors, idempotency, ordering, versioning, and compatibility expectations.
  • Define trust boundaries, identities, authorization, sensitive data, secrets, abuse controls, and audit needs proportionat
Read the complete source ↗