agentleFS
Sign inStart free
CliMACliMA/Oceananigans.jl/.claude/skills/add-feature/SKILL.md

add-feature

Skill1.4k starsChanged 11 days agoMITView on GitHub

Checklist for adding new physics or features to Oceananigans

27 other projects use a version of this, 1 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 2 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 2 mentionsSep 2026: 1 mentionOct 2026: 4 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the CliMA/Oceananigans.jl repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about CliMA/Oceananigans.jl

The biggest 5 of 45 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 45

Talked about on GitHub, Bluesky and Hacker News (45 times).

On GitHub · 42

37 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow this checklist when adding new physics or features to Oceananigans.

    line 8
  2. Distinctive:

    Implement kernel functions: - must be GPU-compatible:

    line 14
  3. Very specific:

    Use @kernel and @index from KernelAbstractions.jl

    line 15
  4. Distinctive:

    Keep type-stable and allocation-free

    line 16
  5. Very specific:

    Use ifelse instead of short-circuiting if/else

    line 17
  6. Very specific:

    No loops over grid points outside kernels - use launch!

    line 19
  7. Very specific:

    Verify on CPU: Run tests with ENV["TEST_ARCHITECTURE"] = "CPU"

    line 23

“Common” is measured: kept by at least 6 in 10 of the 25 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

Add Feature

Follow this checklist when adding new physics or features to Oceananigans.

Checklist

  1. Create module in the appropriate subdirectory under src/
  2. Define types/structs with docstrings (use jldoctest blocks, never plain julia)
  3. Implement kernel functions - must be GPU-compatible:
    • Use @kernel and @index from KernelAbstractions.jl
    • Keep type-stable and allocation-free
    • Use ifelse instead of short-circuiting if/else
    • Mark inner functions with @inline
    • No loops over grid points outside kernels - use launch!
  4. Add unit tests in test/ following existing group structure
  5. Update exports in src/Oceananigans.jl if the user interface changed
  6. Add validation examples in validation/ or examples/ when appropriate
  7. Verify on CPU: Run tests with ENV["TEST_ARCHITECTURE"] = "CPU"
  8. Check explicit imports: Tests automatically verify proper imports

Key Conventions

  • File names: snake_case
  • Type names: PascalCase
  • Function names: snake_case
  • Kernel names: may be prefixed with underscore (e.g., _compute_tendency_kernel)
  • Model constructors: grid is positional, keyword args after semicolon

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.

Check your setup, free