multica-technical-design SKILL.md skillA
multica-technical-design from it235/multica-best-practices is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add it235/multica-best-practices/multica-technical-design@git:20260910.8db057cPins git:20260910.8db057c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/architect/multica-technical-design/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260910.8db057c, committed Sep 10, 2026
- Size
- 1,006 bytes
- Repository stars
- 237
- License
- MIT
Produce a minimal technical plan based on the existing code. Used for architecture analysis, impact assessment, and implementation-plan design.
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
# Technical Design ## Purpose Produce the smallest viable technical plan based on the existing codebase. ## Process 1. Inspect the current implementation. 2. Identify the relevant modules. 3. Identify the existing patterns. 4. Determine the smallest viable change. 5. Identify dependencies. 6. Identify risks. 7. Define the verification method. ## Principles ```text Existing patterns > new abstractions Small changes > big refactors Reuse > new dependencies ``` ## Output - Current architecture - Proposed changes - Affected components - Implementation steps - Verification plan - Risks ## Why this works "The smallest viable change" is a verifiable principle: the smaller the change, the easier it is to verify (Leader rerun / Tester regression), and the lower the regression risk.
Read the whole file at its exact version.
How to install
mdr add it235/multica-best-practices/multica-technical-design@sha256:d5a2161f61eb698bThe line at the top of this page pins the label git:20260910.8db057c, 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_x4gyo3lm465rcbsm)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 10, 2026.
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 (1006 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
it235/multica-best-practices · 237 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x4gyo3lm465rcbsm GET https://markdownregistry.com/api/v1/resolve?ref=it235/multica-best-practices/multica-technical-design GET https://markdownregistry.com/api/v1/blob/d5a2161f61eb698bc55b2b683f0f2ef5af5fe485450fbc2c6b0796f003358b11
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 it235/multica-best-practices
Every file in it235/multica-best-practices