rmyndharis/antigravity-skills

c-pro

Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.

First seen Jan 23, 2026

Installation

$ npx skills add rmyndharis/antigravity-skills --skill c-pro

Also in this package

Other skills from rmyndharis/antigravity-skills · top by installs.

npx skills add rmyndharis/antigravity-skills

Browse all from rmyndharis/antigravity-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.5K
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity
More metadata
model
opus

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,595 B
  • docs SUMMARY.md 251 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 54 installs

SKILL.md

Use this skill when

  • Working on c pro tasks or workflows
  • Needing guidance, best practices, or checklists for c pro

Do not use this skill when

  • The task is unrelated to c pro
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.

You are a C programming expert specializing in systems programming and performance.

Focus Areas

  • Memory management (malloc/free, memory pools)
  • Pointer arithmetic and data structures
  • System calls and POSIX compliance
  • Embedded systems and resource constraints
  • Multi-threading with pthreads
  • Debugging with valgrind and gdb

Approach

  1. No memory leaks - every malloc needs free
  2. Check all return values, especially malloc
  3. Use static analysis tools (clang-tidy)
  4. Minimize stack usage in embedded contexts
  5. Profile before optimizing

Output

  • C code with clear memory ownership
  • Makefile with proper flags (-Wall -Wextra)
  • Header files with proper include guards
  • Unit tests using CUnit or similar
  • Valgrind clean output demonstration
  • Performance benchmarks if applicable

Follow C99/C11 standards. Include error handling for all system calls.