light-system-design

light-system-design is a skill for Claude Code, Codex from Light0305/Light-skills. It costs 134 tokens per session (2,968 once invoked), scanned A, original, MIT.

A guided method for designing or updating a software system, including its parts, data, interfaces, deployment, and changes over time. It starts by documenting what already exists and keeps unknown facts marked as unknown.

In plain words
What is it for?
Use it for new systems or existing monoliths, modular monoliths, services, APIs, and databases. It helps create architecture options, API and data contracts, migration plans, decision records, and checks for whether the design works.
Why use it?
It helps prevent architecture decisions based on guesses or incomplete system knowledge. It also makes alternatives, migration risks, rollback plans, and verification steps explicit.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for new systems or existing monoliths, modular monoliths, services, APIs, and databases. It helps create architecture options, API and data contracts, migration plans, decision records, and checks for whether the design works.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/light0305/light-skills/light-system-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Light0305/Light-skills --skill light-system-design
Clone the repo
git clone --depth 1 https://github.com/Light0305/Light-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for light-system-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/light0305/light-skills/light-system-design/github.svg)](https://agentmods.dev/skills/light0305/light-skills/light-system-design)
Your own site
<a href="https://agentmods.dev/skills/light0305/light-skills/light-system-design"><img src="https://agentmods.dev/badge/skills/light0305/light-skills/light-system-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for light-system-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/light0305/light-skills/light-system-design"><img src="https://agentmods.dev/badge/skills/light0305/light-skills/light-system-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 134 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,968 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00134 $0.02968
Opus 5 $0.00067 $0.01484
Sonnet 5 $0.00027 $0.00594
Haiku 4.5 $0.00013 $0.00297

Measured 9d ago against content hash 0bc3fff35e9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

light-system-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/architecture_lifecycle.py, scripts/contract_validate.py, scripts/design_readiness.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/light-system-design/SKILL.md · 311 lines

How it starts

The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.

System design lifecycle

Own system boundaries, runtime interfaces, operational data stores, system migrations, and architecture decisions. Do not equate a diagram, SQL file, or OpenAPI document with a working, safe, or scalable system.

Read references/system-design-resource-map.md before any existing-system task. It defines the lifecycle, artifact contract, decision stop, evidence states, access tiers, and cross-skill ownership. Read references.md only for the database/API/reliability branch that applies to the selected system.

Non-negotiable boundary

  1. Treat repository, configuration, schema, API, dependency, and deployment intake as read-only access. It is not authorization to rewrite them.
  2. Preserve absent facts as UNKNOWN. Do not infer traffic, SLOs, consistency, budget, compliance, migration windows, or team capability from the phrase “system design.”
  3. Present at least a recommendation, a viable alternative, and explicit rejection/exit conditions. Stop before choosing the database, topology, compatibility policy, or migration strategy for the user.
  4. Bind any later mutation to a user-selected option and exact authorized action IDs. Keep before/after locators, SHA-256, verification, and rollback.
  5. Never mutate a production database or configuration. Apply only to a disposable environment explicitly placed in scope; otherwise deliver a reviewed plan and scripts.
  6. Describe schema_lint.py as a lexical heuristic. It is not a SQL parser, query planner, lock simulator, schema diff engine, or zero-downtime proof.
  7. Keep VERIFIED for checks that actually ran and retain their command, return code, locator, and hash. Use PLANNED, UNKNOWN, or UNAVAILABLE otherwise.
  8. Keep this skill off the research DAG. Emit no light.findings.v1; add no STAGE_GATES, ROUTES, stage number, or back-edge; do not attach _shared.

Choose the mode

Situation Mode
New system with no implementation greenfield requirements and option design
Existing repository/system read-only intake, then current-state inventory
Existing monolith or services changing gradually modernization with compatibility and rollback
API-only change contract and consumer compatibility branch
Schema-only change dialect/version/context-specific migration branch
User supplied a completed package review and evidence verification

Read the full file on GitHub · 311 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 311 lines · 134 tokens per session scan A 0bc3fff35e9a

Subscribe to this mod's changes

light-system-design is a skill published in the GitHub repository Light0305/Light-skills (610 stars, last pushed 2mo ago), licensed MIT. It adds 134 tokens to every session and 2,968 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

ml-paper-writing

Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.

davila7/claude-code-templates · 65 tokens

anti-defensive-writing-en

Stops defensive writing across the entire paper lifecycle — writing, revising, cutting, and organizing experiments. Treats the paper as a press conference, not a project summary, lab log, or self-audit: identify the single most publishable strength of the work and build the most favorable, complete, and persuasive…

Adkid-Zephyr/anti-defensive-writing-Skill · 138 tokens

anti-defensive-writing

A Chinese-language writing guide for presenting a research paper around its strongest supported contribution. It treats the paper as a focused academic presentation rather than a project diary or complete lab record.

Adkid-Zephyr/anti-defensive-writing-Skill · 160 tokens

api-hardening

API hardening for Express, FastAPI, and serverless. Use for rate limiting, CORS, input validation, API keys, or OWASP API Top 10.

jamditis/claude-skills-journalism · 39 tokens

paper-writing

Research paper writing assistant that enforces Arpit Gupta's editorial principles, voice profile, and writing workflow. MANDATORY TRIGGERS: Use this skill whenever the user mentions writing a paper, drafting a section, revising a section, editing a paper, reviewing a draft, rewriting an introduction, writing an…

SNL-UCSB/paper-writing-skill · 153 tokens

research-writing

A collection of 30 prompt templates for writing and reviewing scientific papers. It covers tasks such as translating, editing, summarizing research, writing sections, creating figure captions, and preparing reviewer replies.

alfonso0512/research-writing-skill · 136 tokens