junjo: Skill for Claude Code

.agents/skills/studio-frontend-react/SKILL.md

studio-frontend-react is a skill for Claude Code, Codex from mdrideout/junjo. It costs 38 tokens per session (658 once invoked), scanned A, original, Apache-2.0.

A set of instructions for working on Junjo AI Studio's React frontend, including user-interface components, application state, data schemas, tests, and feature organization.

In plain words
What is it for?
Use it when changing or reviewing React components, Redux Toolkit state, frontend schemas, browser-facing API work, or frontend tests.
Why use it?
It keeps frontend changes consistent with the project's rules for state ownership, asynchronous updates, API data, and testing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is mdrideout/junjo's own configuration. It tells Claude Code and Codex how to work on junjo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything junjo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mdrideout/junjo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mdrideout/junjo/master/.agents/skills/studio-frontend-react/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mdrideout/junjo

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 studio-frontend-react

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mdrideout/junjo/studio-frontend-react"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/studio-frontend-react.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 658 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.00038 $0.00658
Opus 5.5 $0.00015 $0.00263
Sonnet 5.5 $0.00008 $0.00132
Haiku 4.5 $0.00004 $0.00066

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

Security

Grade A, and why

studio-frontend-react 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.

.agents/skills/studio-frontend-react/SKILL.md · 79 lines

How it starts

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

Studio Frontend React

Use This Skill When

  • The task touches apps/studio/frontend/.
  • The task changes React component structure, state ownership, Redux Toolkit slices/listeners/selectors, frontend schemas, or frontend tests.
  • The task changes frontend feature organization or a frontend-facing API contract.

Boundaries

  • This skill owns the workflow for Studio frontend work, not the architecture itself.
  • apps/studio/docs/adr/002-redux-toolkit-listener-middleware-pattern.md owns state placement, listener middleware, and feature file roles.
  • apps/studio/docs/adr/004-events-json-contract.md owns the events_json shape.
  • Current code and tests own implementation details.

Before Changing State

Determine:

  1. Which component or feature semantically owns the value?
  2. Which consumers read or change it, and how closely related are they in the component tree?
  3. How long must the value live?
  4. Is there already an authoritative local, URL, Context, or Redux value?
  5. Do props still express a clear contract, or are unrelated components only forwarding them?
  6. Does the transition require only synchronous state mutation, or does it have an asynchronous or external consequence?
  7. Would broader ownership reduce more coordination than it adds?

Start with the narrowest correct owner. Do not move state into Redux merely because a request is asynchronous or because props cross a fixed number of components.

Redux Guardrails

  • Use typed hooks from apps/studio/frontend/src/root-store/hooks.ts.
  • State-transition action types mutate slice state. Listener-trigger action types do not. A single action type must never do both.
  • Reducers own synchronous invariants. Listeners own consequences of Redux trigger actions, including Redux-owned async work and cross-feature effects.
  • Fetch modules own HTTP transport, and schemas parse responses at the runtime contract boundary.
  • Do not introduce RTK Query or TanStack Query.
  • Do not treat existing code that conflicts with the accepted ADR as a new architectural precedent.

Read the full file on GitHub · 79 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. 1mo ago First seen · 79 lines · 38 tokens per session scan A a7a398f3f91f

Subscribe to this mod's changes

studio-frontend-react is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 17d ago), licensed Apache-2.0. It adds 38 tokens to every session and 658 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-08-30.

Related

Other skills, from other repositories

decocms-ui

Build or style React UI with the decocms product design system (@decocms/ui). Use when creating a new screen, page, or component that should look like decocms products, when the user mentions "design system", "@decocms/ui", "decocms style", or asks to make UI consistent with Studio. Covers screen layout (width…

decocms/studio · 95 tokens

design-to-code

Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…

yonatangross/orchestkit · 86 tokens

multi-surface-render

Multi-surface rendering with json-render — one JSON spec produces React web, Next.js, React Native, Ink terminal UIs, PDFs, emails, Remotion videos, OG images, and 3D scenes. Covers renderer target selection, registry mapping, and platform APIs (renderToBuffer, renderToStream, renderToFile). Use when generating output…

yonatangross/orchestkit · 98 tokens

ai-ui-generation

AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality…

yonatangross/orchestkit · 95 tokens

design-import

Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…

yonatangross/orchestkit · 74 tokens

i18n-date-patterns

Implements internationalization (i18n) in React applications. Covers user-facing strings, date/time handling, locale-aware formatting, ICU MessageFormat, and RTL support. Use when building multilingual UIs or formatting dates/currency.

yonatangross/orchestkit · 53 tokens