agentleFS
SuShuhengSuShuheng/making-things/skills/solution-architecture/SKILL.md

solution-architecture

Skill1 starsChanged 4 months agoMITView on GitHub

Use when an approved Electron PRD needs architecture, process ownership, data flow, IPC contracts, stack decisions, migration, or rollback design. Do not use before PRD approval or for feature coding, independent review, debugging, or release execution.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the smallest implementable, secure design in the sidecar CONTRACT.md.

    line 8
  2. Very specific:

    Read sidecar PROJECT.md, approved PRD.md, repository evidence, and references/electron-architecture.md.

    line 10
  3. Distinctive:

    Do not code from an unapproved contract or use the preload bridge as a generic privileged API.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Solution Architecture

Write the smallest implementable, secure design in the sidecar CONTRACT.md.

  1. Read sidecar PROJECT.md, approved PRD.md, repository evidence, and references/electron-architecture.md.
  2. Detect and preserve the existing stack and commands. Do not select a business stack without user approval.
  3. Assign renderer, preload, main, utility/worker, and shared ownership. Define serializable contracts, runtime validation, sender authorization, cancellation, cleanup, stable errors, data ownership, migration, rollback, development/packaged behavior, and platform differences.
  4. Complete the CONTRACT sections for renderer, main/preload/IPC, errors, permissions, and cross-track acceptance. Make frontend/backend scopes disjoint or state an explicit serialized dependency.
  5. Record alternatives, risks, security/privacy impact, and approval in the sidecar. After approval, route to mts-split.

Do not code from an unapproved contract or use the preload bridge as a generic privileged API. Do not select authority based on host brand.

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.