prime-frontend

prime-frontend is a skill for Claude Code from coleam00/skills. It costs 70 tokens per session (951 once invoked), scanned A, original, MIT.

A focused codebase-reading guide for frontend work, covering UI components, page routing, application state, and styling. It can also load related Jira tasks or Confluence pages before examining the code.

In plain words
What is it for?
Use it at the start of work on user interfaces or client-side features, optionally using details from linked Atlassian work items.
Why use it?
It helps an agent understand the client-side parts relevant to a task without loading unrelated backend code.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md.

Part of the skills plugin — 34 skills shipped together

Good fit Use it at the start of work on user interfaces or client-side features, optionally using details from linked Atlassian work items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/coleam00/skills/prime-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 coleam00/skills --skill prime-frontend
Clone the repo
git clone --depth 1 https://github.com/coleam00/skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 34 skills.

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 prime-frontend

README.md
[![agentmods](https://agentmods.dev/badge/skills/coleam00/skills/prime-frontend/github.svg)](https://agentmods.dev/skills/coleam00/skills/prime-frontend)
Your own site
<a href="https://agentmods.dev/skills/coleam00/skills/prime-frontend"><img src="https://agentmods.dev/badge/skills/coleam00/skills/prime-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 prime-frontend

Your own site · 80×15
<a href="https://agentmods.dev/skills/coleam00/skills/prime-frontend"><img src="https://agentmods.dev/badge/skills/coleam00/skills/prime-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 951 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00070 $0.00951
Opus 5 $0.00035 $0.00476
Sonnet 5 $0.00014 $0.00190
Haiku 4.5 $0.00007 $0.00095

Measured 11d ago against content hash e4c468b2df43, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

prime-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 11d 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.

.claude/skills/prime-frontend/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prime Frontend: Load Frontend Context

Objective

Build targeted understanding of the frontend codebase by analyzing its structure, components, and conventions. Loading only frontend context keeps the context window light on complex full-stack codebases. If external task references are provided, load them first so the analysis is anchored to the actual work.

Process

Step 0: Load External Context

Run this step BEFORE the codebase analysis. It accepts optional arguments: [jira-issue-keys] [confluence-page-ids].

  • Jira keys may be a single key (ACC-2) or comma-separated (ACC-2,ACC-3).
  • Confluence page ids are numeric page ids.

If Jira issue keys are provided:

  1. Call mcp__atlassian__getAccessibleAtlassianResources to obtain the cloudId.
  2. For each Jira key, call mcp__atlassian__getJiraIssue with that cloudId, the issue key, and responseContentFormat: "markdown".
  3. Treat the returned issue summary, description, and acceptance criteria as the task context for everything that follows.

If Confluence page ids are provided:

  1. Call mcp__atlassian__getConfluencePage for each page id with contentFormat: "markdown" (use the cloudId from above, fetching it via mcp__atlassian__getAccessibleAtlassianResources if it was not already retrieved).
  2. Treat the returned page content as supporting context (specs, design docs, requirements).

If no arguments are provided: Skip this step entirely and proceed to Step 1.

Briefly summarize any external context loaded before continuing — this frames the rest of the priming.

1. Locate the Frontend

List all tracked files to find the frontend root:

!git ls-files

Common frontend roots: frontend/, client/, web/, src/ (when project is frontend-only), app/ (Next.js). Identify the correct root before proceeding.

2. Read Frontend Documentation

  • Read CLAUDE.md or similar global rules file (for project-wide conventions)
  • Read any README inside the frontend root
  • Read .claude/references/frontend-component-best-practices.md if it exists — it contains project-specific component conventions

Read the full file on GitHub · 100 lines

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. 11d ago First seen · 100 lines · 70 tokens per session scan A e4c468b2df43

Subscribe to this mod's changes

prime-frontend is a skill published in the GitHub repository coleam00/skills (496 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 951 once invoked, about $0.0003 per session on Opus 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-08-30.

Related

Other skills, from other repositories

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens

menu-transitions-rtl

Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…

asmyshlyaev177/react-horizontal-scrolling-menu · 137 tokens