agentleFS
jjenkinsjjenkins/agent-image-skills/CLAUDE.md

agent-image-skills

CLAUDE.md1 starsChanged 9 months agoMITView on GitHub

Multi-language client library monorepo for the Lab Nocturne Images API (https://images.labnocturne.com). Provides installable client packages in Python, Go, Ruby, JavaScript, and PHP, plus Claude Code skills and a ChatGPT Action integration. The API server lives elsewhere (jjenkins/labnocturne). This repo contains only client-side code and skill definitions. All five clients implement the same API surface with language-idiomatic naming: All clients default base_url to https://images.labnocturne.com and authenticate via Authorization: Bearer <key> header. Upload uses multipart/form-data. Skills are in skills/ as symlinks. Each…

  • Reads credentials
  • Installs packages

The file

We split this CLAUDE.md into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All five clients implement the same API surface with language-idiomatic naming:

    line 56
  2. Very specific:

    All clients default base_url to https://images.labnocturne.com and authenticate via Authorization: Bearer <key> header.

    line 66
  3. Distinctive:

    Keep client code simple and beginner-friendly with minimal dependencies

    line 91
  4. Distinctive:

    Use real, working code — not pseudocode

    line 92
  5. Distinctive:

    Follow each language's idiomatic conventions

    line 93
  6. Distinctive:

    Keep dependencies minimal (Go and Ruby clients use only stdlib)

    line 94
  7. Very specific:

    Test examples against the live API before committing (/test-example <language>)

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What This Repo Is

Multi-language client library monorepo for the Lab Nocturne Images API (https://images.labnocturne.com). Provides installable client packages in Python, Go, Ruby, JavaScript, and PHP, plus Claude Code skills and a ChatGPT Action integration.

The API server lives elsewhere (jjenkins/labnocturne). This repo contains only client-side code and skill definitions.

Repository Layout

  • python/ — Python client (labnocturne package, uses requests)
  • go/ — Go client (labnocturne package, stdlib only)
  • javascript/ — Node.js client (ESM, uses form-data)
  • ruby/ — Ruby client (labnocturne gem, stdlib net/http)
  • php/ — PHP client (uses ext-curl, published to Packagist as labnocturne/image-client)
  • examples/curl/ — curl-based usage examples
  • skills/ — Claude Code skill definitions (symlinks to .agents/skills/)
  • integrations/chatgpt-action/ — ChatGPT GPT Action with OpenAPI schema
  • .claude/commands/test-example.md — Custom command to test language examples

Build & Test Commands

Python:

pip install ./python                          # install locally
pip install ./python[dev]                     # install with dev deps (pytest, black, flake8, mypy)
cd python && pytest                           # run tests

Go:

cd go && go build ./...                       # build
cd go && go test ./...                        # test

JavaScript:

cd javascript && npm install                  # install deps
cd javascript && npm test                     # run tests (node --test)

Ruby:

cd ruby && bundle install                     # install deps

PHP:

composer install                              # install from root composer.json

Client Library Conventions

All five clients implement the same API surface with language-idiomatic naming:

OperationEndpointPythonGoJSRubyPHP
Generate keyGET /keygenerate_test_key() (static)GenerateTestKey()generateTestKey() (static)generate_test_key (class)generateTestKey() (static)
UploadPOST /uploadupload(path)Upload(path)upload(path)upload(path)upload(path)
List filesGET /fileslist_files()ListFiles()listFiles()list_files()listFiles()
StatsGET /statsget_stats()GetStats()getStats()get_statsgetStats()
DeleteDELETE /i/:iddelete_file(id)DeleteFile(id)deleteFile(id)delete_file(id)deleteFile(id)

All clients default base_url to https://images.labnocturne.com and authenticate via Authorization: Bearer <key> header. Upload uses multipart/form-data.

Skills (Claude Code)

Skills are in skills/ as symlinks. Each skill is a SKILL.md with YAML frontmatter (name, description, metadata tags). The image-* prefixed skills are the canonical set:

  • image-upload — Upload an image, get CDN URL
  • image-files — List uploaded files with pagination
  • image-stats — View storage usage
  • image-delete — Soft-delete an image
  • image-key — Generate a test API key

Skills auto-detect $LABNOCTURNE_API_KEY env var. If unset, they generate a temporary test key (7-day retention, 10MB limit). Skills use $LABNOCTURNE_BASE_URL if set.

Shared auth logic (API key resolution, base URL, common error codes) lives in .agents/skills/references/auth.md and is referenced by all skills.

The non-prefixed skills (upload, files, stats, delete, generate-key) are legacy aliases that redirect to their image-* counterparts.

API Key Types

  • Test keys (ln_test_*): free, no signup, 10MB file limit, 7-day retention
  • Live keys (ln_live_*): paid, 100MB file limit, permanent storage

Style

  • Keep client code simple and beginner-friendly with minimal dependencies
  • Use real, working code — not pseudocode
  • Follow each language's idiomatic conventions
  • Keep dependencies minimal (Go and Ruby clients use only stdlib)
  • Test examples against the live API before committing (/test-example <language>)

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.