architecture-patterns SKILL.md skillA
architecture-patterns from akaszubski/autonomous-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add akaszubski/autonomous-dev/architecture-patterns@git:20260317.e64d556Pins git:20260317.e64d556 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- akaszubski/autonomous-dev
- Path
plugins/autonomous-dev/skills/architecture-patterns/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260317.e64d556, committed Mar 17, 2026
- First version recorded
- Feb 19, 2026
- Size
- 5,525 bytes
- Repository stars
- 34
- License
- none declared
File-by-file architecture planning with ADR format, dependency ordering, and testability gates. Use when designing system architecture or creating ADRs. TRIGGER when: architecture plan, system design, ADR, file breakdown, component design. DO NOT TRIGGER when: simple config edits, single-file bug fixes, documentation-only changes.
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
# Architecture Patterns Enforcement Skill Ensures every architecture plan is thorough, actionable, and testable. Used by the planner agent. ## Decision Framework Every architectural decision MUST follow this structure: ### 1. Problem Statement - What problem are we solving? - What are the constraints (performance, compatibility, timeline)? - What does PROJECT.md say about scope? ### 2. Options Analysis - Minimum 2 alternatives considered - Each option has explicit pros and cons - Effort estimate for each (low/medium/high) ### 3. Recommendation - Which option and why - What tradeoffs are we accepting - What risks remain --- ## Plan Structure Requirements Every architecture plan MUST include: ### File-by-File Breakdown ``` ## Files to Create/Modify ### 1. lib/new_module.py (CREATE) - Purpose: [what this file does] - Key classes/functions: [list] - Dependencies: [what it imports] - Tests: tests/unit/test_new_module.py ### 2. lib/existing_module.py (MODIFY) - Changes: [what changes and why] - Lines affected: ~[range] - Risk: [low/medium/high] ``` ### Ordered Steps with Dependencies ``` ## Implementation Order 1. Create lib/new_module.py (no dependencies) …
Read the whole file at its exact version.
How to install
mdr add akaszubski/autonomous-dev/architecture-patterns@sha256:281571739aeb370aThe line at the top of this page pins the label git:20260317.e64d556, 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_3nh2236wmua2qixl)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Feb 19, 2026 and Mar 17, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260317.e64d556 latest | 2026-03-17 | e64d556 | 5,525 B | A | view · diff |
| v1.0.0 | 2026-03-17 | b108c5a | 5,654 B | A | view · diff |
| v1.0.0 | 2026-03-06 | 3a09c50 | 5,712 B | A | view · diff |
| v1.0.0 | 2026-02-19 | 4f3e7c2 | 5,433 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 (5525 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
akaszubski/autonomous-dev · 34 stars · license none declared · pushed 2026-10-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_3nh2236wmua2qixl GET https://markdownregistry.com/api/v1/resolve?ref=akaszubski/autonomous-dev/architecture-patterns GET https://markdownregistry.com/api/v1/blob/281571739aeb370a0c0dd637c8b2fe3081c5a8c7b90e07e5e584bd79da5c670d
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.
More from akaszubski/autonomous-dev
Every file in akaszubski/autonomous-dev