multica-artifact-frontend SKILL.md skillA
multica-artifact-frontend 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-artifact-frontend@v1.0.0Pins v1.0.0 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/frontend/multica-artifact-frontend/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 10, 2026
- Size
- 1,721 bytes
- Repository stars
- 237
- License
- MIT
Frontend artifact sync—push the frontend deliverable set (page/component/state/style) and run-url to Multica frontend-artifact (product-requirement mapping); the preferred mount for @FrontendDev.
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
# Frontend Artifact (frontend-artifact) ## Responsibility As @FrontendDev, after the page is implemented, push the **frontend deliverable set** and **run-url** to Multica `frontend-artifact` (product-requirement mapping surface). This is the input for @Reviewer (G1) and @Tester (T1/T2), and the basis for release/verification. ## Push content (must be complete) - Page list (route + name + screenshot/link) - Component/state/style deliverable set - run-url (reachable after deployment) - Requirement/design traceability (which AC each page covers) ## Flow 1. Implement pages per `multica-frontend-impl`, consuming upstream `multica-design-ui-impl` design links. 2. Assemble the deliverable set + run-url. 3. Push to Multica `frontend-artifact` (product-requirement mapping): `python scripts/import_to_multica.py --artifact frontend --json frontend-artifact.json` (see `references/import-contract.md`). 4. Hand off to @Reviewer (G1 business review) and @Tester (T1/T2). ## Notes - Keep fields 1:1 with requirement/design; do not drift. - run-url must be reachable; otherwise @Tester T3 will be BLOCKED. - Do not confuse with `backend-artifact` (that is @BackendDev's contract surface).
Read the whole file at its exact version.
How to install
mdr add it235/multica-best-practices/multica-artifact-frontend@sha256:c40ef03975eeb900The line at the top of this page pins the label v1.0.0, 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_nwkmwu6tappxvjoz)
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 (1721 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_nwkmwu6tappxvjoz GET https://markdownregistry.com/api/v1/resolve?ref=it235/multica-best-practices/multica-artifact-frontend GET https://markdownregistry.com/api/v1/blob/c40ef03975eeb900011b412a36615ab1809cea6749143de337be5983c46e7484
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