multica-artifact-frontend

multica-artifact-frontend is a skill for Claude Code, Codex from it235/multica-best-practices. It costs 47 tokens per session (421 once invoked), scanned A, original, MIT.

A documentation workflow for frontend implementation notes. It defines what the notes should contain and uses Jira, Confluence, and Figma integrations to gather links and publish the document.

In plain words
What is it for?
Use it to write and publish an implementation specification for a frontend feature, including loading, empty, error, and permission states.
Why use it?
It keeps the intended pages, routes, states, components, and API connections visible to reviewers and testers. This reduces confusion between the written design and the code being built.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write and publish an implementation specification for a frontend feature, including loading, empty, error, and permission states.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/it235/multica-best-practices/multica-artifact-frontend
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add it235/multica-best-practices --skill multica-artifact-frontend
Clone the repo
git clone --depth 1 https://github.com/it235/multica-best-practices

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for multica-artifact-frontend

README.md
[![agentmods](https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-artifact-frontend/github.svg)](https://agentmods.dev/skills/it235/multica-best-practices/multica-artifact-frontend)
Your own site
<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-artifact-frontend"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-artifact-frontend/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for multica-artifact-frontend

Your own site · 80×15
<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-artifact-frontend"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-artifact-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00421
Opus 5.5 $0.00019 $0.00168
Sonnet 5.5 $0.00009 $0.00084
Haiku 4.5 $0.00005 $0.00042

Measured 1mo ago against content hash c40ef03975ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multica-artifact-frontend scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/en_US/skills/frontend/multica-artifact-frontend/SKILL.md · 36 lines

What it actually 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).
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago Changed · -49 lines · -2 tokens per session c40ef03975ee
  2. 1mo ago First seen · 85 lines · 49 tokens per session scan A 6d0a8ed91204

Subscribe to this mod's changes

multica-artifact-frontend is a skill published in the GitHub repository it235/multica-best-practices (212 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 421 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

material-ui-tailwind

Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.

mui/material-ui · 67 tokens

fuzzy-ranking

Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.

TanStack/table · 62 tokens

r3f-best-practices

React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.

zebbern/claude-code-guide · 74 tokens

git-safety

Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.

tamagui/tamagui · 0 tokens

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens