logical-component-design SKILL.md skillA
logical-component-design from fabiandistler/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fabiandistler/agents/logical-component-design@git:20261025.ebda69cPins git:20261025.ebda69c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fabiandistler/agents
- Path
skills/logical-component-design/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261025.ebda69c, committed Oct 25, 2026
- First version recorded
- Oct 19, 2026
- Size
- 11,296 bytes
- Repository stars
- 2
- License
- none declared
Decomposes a NEW system or feature into named logical components; not for measuring an existing decomposition. Use when asking what components a new system needs.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Logical Component Design A **logical component** is a building block of the system with a distinct role — represented in code as a namespace or directory (`com.app.order.placement`, `order/placement/`). This skill takes a system or feature you are *about to build* and produces a first set of named components, then refines them. It is the generative front end to the analysis skills: it *creates* the decomposition; `members/coupling-cohesion/SKILL.md` (read via the `architecture` router) *measures* one that already exists. The core idea, from *Fundamentals of Software Architecture* (ch. 8), is that component identification is an **iterative feedback loop**, not a one-shot act of getting it right. You know least about the system at the very start, so trying to perfect the initial components is wasted effort. Make a best guess, assign work to it, see where it strains, and restructure. The loop never fully stops — it runs on greenfield systems and every time a feature is added or changed. Detailed approaches, worked examples, the Going-Going-Gone case study, and a fill-in worksheet live in [references/component-identification.md](references/component-identification.md). …
Read the whole file at its exact version.
How to install
mdr add fabiandistler/agents/logical-component-design@sha256:c9d9d7e212d2d051The line at the top of this page pins the label git:20261025.ebda69c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ljxnvoi7vaij64mp)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 19, 2026 and Oct 25, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.ebda69c latest | 2026-10-25 | ebda69c | 11,296 B | A | view · diff |
| git:20261023.76ca594 | 2026-10-23 | 76ca594 | 11,261 B | A | view · diff |
| git:20261022.e7a86a8 | 2026-10-22 | e7a86a8 | 12,130 B | A | view · diff |
| git:20261021.4bc7222 | 2026-10-21 | 4bc7222 | 12,129 B | A | view · diff |
| git:20261019.8476e53 | 2026-10-19 | 8476e53 | 12,203 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11296 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fabiandistler/agents · 2 stars · license none declared · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ljxnvoi7vaij64mp GET https://markdownregistry.com/api/v1/resolve?ref=fabiandistler/agents/logical-component-design GET https://markdownregistry.com/api/v1/blob/c9d9d7e212d2d051503c6824e394515b3228fbeccf8e954804d85dd820cb1046
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.