agentleFS
Sign inStart free
JOndarzaJOndarza/loadout/.claude/skills/loadout-system-design/SKILL.md

loadout-system-design

Skill2 starsChanged 7 months agoMITView on GitHub

Complete system design reference for the Loadout VSCode extension — a GUI panel for managing Claude Code agents, skills, and commands as swappable equipment loadouts. Use at the start of ANY implementation task to ensure design consistency. Covers: two-process architecture (Extension Host Node.js + Angular 21 Webview), postMessage protocol, data.js filesystem layer, signal-based state services, storage layout, and non-negotiable coding rules. Invoke when implementing stories, adding features, reviewing code, making ANY UI/styling change (design tokens, SCSS, components, animations), or when any system design question arises in Loadout.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When adding a new feature end-to-end, follow this order:

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Loadout — System Design Reference

Quick Navigation

What you needLoad
Two-process overview, file map, state flow, build pipelinereferences/architecture.md
Extension entry, src/ modules, data.js API, security modelreferences/extension-host.md
Angular 21, state services, DataSyncService, shared primitivesreferences/webview-angular.md
Full message catalogue (WebviewMessage + ExtensionMessage types)references/messaging-protocol.md
Domain types, storage paths, profiles, hash/sync mechanicsreferences/domain-storage.md
File size limits, CommonJS rules, Angular rules, git, formattingreferences/coding-rules.md
Design tokens, color palettes, SCSS mixins, animations, a11yreferences/ui-design-system.md

Non-negotiable invariants

These apply everywhere, always — no exceptions.

  1. No VSCode API in webview — never import vscode or use fs/path/os from any file under webview/.
  2. All filesystem mutations go through data.js — no ad-hoc fs.writeFileSync in src/ modules.
  3. Every Angular component: standalone: true + ChangeDetectionStrategy.OnPush — no exceptions.
  4. State in core/state/*.state.ts signal services only — components are dumb views; no component-local mutable state for domain data.
  5. Signals for state, RxJS only for the bridge stream — no BehaviorSubject / ReplaySubject for state.
  6. File size cap ~400 lines — split into a new src/ module or Angular subcomponent when approaching this.
  7. Profiles store filenames only — never copy file content into profiles.json.
  8. Icons: lucide-angular only — no SVG file imports, no inline <svg>.
  9. CommonJS in extension host — require() / module.exports in all .js root files; update-claude.mjs is the sole ESM exception.
  10. Build webview-dist/ before committing UI changes — run cd webview && npm run build.

Feature implementation checklist

When adding a new feature end-to-end, follow this order:

  1. Domain — add or extend types in webview/src/app/core/messages.ts (single source of truth for all shared types).
  2. Storage — decide persistence: profiles.json, ui-state.json, or a new data.js function. Update data.js and src/snapshot.js::buildInitialData if InitialData changes.
  3. Extension messages — add the WebviewMessage union variant and/or ExtensionMessage variant to messages.ts; handle the new case in src/message-handler.js.
  4. data.js — implement the filesystem operation (pure I/O, no VSCode API, no side effects beyond fs).
  5. State service — update the relevant core/state/*.state.ts to expose new signals or a setter; update DataSyncService.applyData() if InitialData fields changed.
  6. Component — create a standalone OnPush component or extend an existing feature. Inject the state service; never own domain state locally. Send actions via bridge.send() in methods, not templates.
  7. Validators — if new user-supplied input crosses the bridge, add a guard in src/validators.js and call it in message-handler.js before acting.
  8. Build — run cd webview && npm run build, verify webview-dist/ is updated.
  9. Git — stage specific files by name; conventional commit in imperative mood.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free