agentleFS
nativewindnativewind/react-native-css/.claude/skills/add-test/SKILL.md

add-test

Skill167 starsChanged 8 months agoMITView on GitHub

Scaffold a test for a react-native-css feature following the project's testing conventions.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-pr and review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify CSS → JSON compilation output structure.

    line 38
  2. Distinctive:

    Test runtime style application on native platform.

    line 42
  3. Very specific:

    Find existing tests: Search the appropriate src/__tests__/ subdirectory for similar tests.

    line 50
  4. Distinctive:

    Write the test: Follow the conventions of the domain.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context

react-native-css has three test domains in src/__tests__/:

  • babel/ — Babel plugin tests using babel-plugin-tester
  • compiler/ — CSS compilation tests verifying JSON output
  • native/ — Runtime tests for style application

Conventions by domain

Babel tests (src/__tests__/babel/)

Use babel-plugin-tester:

import { pluginTester } from "babel-plugin-tester";

pluginTester({
  plugin,
  tests: {
    "test name": {
      code: `import { View } from 'react-native';`,
      output: `import { View } from 'react-native-css/components';`,
    },
  },
});

Compiler tests (src/__tests__/compiler/)

Verify CSS → JSON compilation output structure.

Native tests (src/__tests__/native/)

Test runtime style application on native platform.

Steps

  1. Identify the feature: What needs testing? Use $ARGUMENTS as the starting point.
  2. Determine the domain: Is this a babel transform, compiler output, or runtime behavior?
  3. Find existing tests: Search the appropriate src/__tests__/ subdirectory for similar tests.
  4. Write the test: Follow the conventions of the domain.
  5. Run the test: Execute yarn test. Note: ignore ExperimentalWarning: VM Modules warnings — they're expected.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.