agentleFS
Sign inStart free
e-dule-dul/opencl-lab/.claude/skills/cpp-opencl-dev/SKILL.md

cpp-opencl-dev

Skill0 starsChanged 8 months agoMITView on GitHub

Core engineering guidelines for writing safe, performant C++17 and OpenCL 1.2 code.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read Guidelines: Always review 00_master_specs.md, MEMORY.md and 03-safety.md before writing code.

    line 11
  2. Distinctive:

    Modern C++: Use C++17 (auto, lambdas, filesystem).

    line 13
  3. Very specific:

    Error Handling: Check cl_int err on every OpenCL call.

    line 16
  4. Very specific:

    Utilities: Do not reinvent the wheel.

    line 17
  5. Distinctive:

    Educational Commenting: Write comments that explain *WHY* the code does something, not *WHAT* it does.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

C++ & OpenCL Engineering Skill

You are executing the Tactical Implementation phase.

Instructions

  1. Read Guidelines: Always review 00_master_specs.md, MEMORY.md and 03-safety.md before writing code.
  2. Implementation Rules:
    • Modern C++: Use C++17 (auto, lambdas, filesystem). Do not use C++20 features.
    • OpenCL Wrapper: Strictly use the OpenCL 1.2 C++ wrapper (cl.hpp). NEVER use raw C API calls (like clCreateBuffer).
    • RAII: Rely on destructors for resource cleanup.
    • Error Handling: Check cl_int err on every OpenCL call. Use try-catch blocks where appropriate.
    • Utilities: Do not reinvent the wheel. Use headers from the common/ folder (e.g., openclutils.hpp, stb_image.h wrappers).
  3. Educational Commenting: Write comments that explain WHY the code does something, not WHAT it does. Code must be readable for Mid-level developers.
  4. Verification: You MUST run cmake --build . using the Bash tool before declaring the task complete. Fix any compilation errors.

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