everything-react-native-expo: Skill for Claude Code

.claude/skills/component/SKILL.md

component is a skill for Claude Code from JubaKitiashvili/everything-react-native-expo. It costs 17 tokens per session (684 once invoked), scanned A, original, MIT.

A workflow for designing and testing user-interface components, such as cards, buttons, or panels. It assigns design and test work to separate agents in parallel.

In plain words
What is it for?
Use it to clarify component behavior and states, design the component with NativeWind, and create tests for it.
Why use it?
It helps cover both the component’s appearance and its automated tests during development.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is JubaKitiashvili/everything-react-native-expo's own configuration. It tells Claude Code how to work on everything-react-native-expo 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 everything-react-native-expo configures →

Part of the erne-universal plugin — 45 skills, 12 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to JubaKitiashvili/everything-react-native-expo. 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/JubaKitiashvili/everything-react-native-expo/main/.claude/skills/component/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expo

Made for: Claude Code.

Or install erne-universal, the plugin that ships this one along with the rest of its 45 skills, 12 agents.

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 component

README.md
[![agentmods](https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/component.svg)](https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/component)
Your own site
<a href="https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/component"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/component.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 684 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.00017 $0.00684
Opus 5 $0.00009 $0.00342
Sonnet 5 $0.00003 $0.00137
Haiku 4.5 $0.00002 $0.00068

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

Security

Grade A, and why

component 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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/component/SKILL.md · 94 lines

How it starts

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

/component — Design + Test Component

You are executing the /component command. Run ui-designer and tdd-guide in parallel. One designs the component, the other writes tests.

Parallel Execution

Agent 1: ui-designer — Component Design

  1. Clarify requirements — What does the component do? What states does it have?
  2. Design with NativeWind — Use Tailwind classes for styling:
import { View, Text, Pressable } from 'react-native';

interface CardProps {
  title: string;
  subtitle?: string;
  onPress?: () => void;
  variant?: 'default' | 'outlined' | 'elevated';
}

export function Card({ title, subtitle, onPress, variant = 'default' }: CardProps) {
  return (
    <Pressable
      onPress={onPress}
      className={cn(
        'rounded-2xl p-4',
        variant === 'default' && 'bg-card',
        variant === 'outlined' && 'border border-border bg-transparent',
        variant === 'elevated' && 'bg-card shadow-md',
      )}
    >
      <Text className="text-lg font-semibold text-foreground">{title}</Text>
      {subtitle && (
        <Text className="mt-1 text-sm text-muted-foreground">{subtitle}</Text>
      )}
    </Pressable>
  );
}
  1. Handle all states — Loading, error, empty, populated, disabled
  2. Add accessibilityaccessibilityRole, accessibilityLabel, accessibilityState
  3. Platform adaptation — Use Platform.select or NativeWind responsive for platform differences
  4. Consider agent-device — If available, render on simulator and screenshot for visual verification

Agent 2: tdd-guide — Component Tests

Write comprehensive tests alongside the component:

import { render, screen, fireEvent } from '@testing-library/react-native';
import { Card } from './Card';

describe('Card', () => {
  it('renders title', () => {
    render(<Card title="Test Title" />);
    expect(screen.getByText('Test Title')).toBeTruthy();
  });

  it('renders subtitle when provided', () => {
    render(<Card title="Title" subtitle="Subtitle" />);
    expect(screen.getByText('Subtitle')).toBeTruthy();
  });

  it('hides subtitle when not provided', () => {
    render(<Card title="Title" />);
    expect(screen.queryByText('Subtitle')).toBeNull();
  });

  it('calls onPress when tapped', () => {
    const onPress = jest.fn();
    render(<Card title="Title" onPress={onPress} />);
    fireEvent.press(screen.getByText('Title'));
    expect(onPress).toHaveBeenCalledTimes(1);
  });

  it('applies variant styles', () => {
    // Test each variant renders correctly
  });
});

Read the full file on GitHub · 94 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. 8d ago First seen · 94 lines · 17 tokens per session scan A e41f52288272

Subscribe to this mod's changes

component is a skill published in the GitHub repository JubaKitiashvili/everything-react-native-expo (44 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 684 once invoked, about $0.0001 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

qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

davila7/claude-code-templates · 34 tokens

design-qa

Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to…

XiaomiMiMo/MiMo-Code · 68 tokens

health

Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…

tw93/Waza · 71 tokens

hunt

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…

tw93/Waza · 70 tokens

chrome-cdp

Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…

mattzcarey/shippie · 91 tokens

ui-craft-checks

Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…

Orkas-AI/Orkas · 5 tokens