agentleFS
Sign inStart free
ddddjaakddddjaak/ae-skills/CLAUDE.md

ae-skills

CLAUDE.md4 starsChanged 5 months agoMITView on GitHub

This is the ae-skills project — a collection of production-grade engineering skills for AE (Application Engineers) in the embedded systems space. Covers firmware development, RTOS-based design, peripheral drivers, and embedded debugging. Built for engineers working with GCC, Arm toolchains, RTOS (Zephyr/FreeRTOS), BMS, Bluetooth, and other embedded technologies. Define: interview-me, idea-refine, spec-driven-development Plan: planning-and-task-breakdown Build: incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, api-and-interface-design Verify: debugging-and-error-recovery Review: code-review-and-quality, code-simplification, security-and-hardening, performance-optimization Ship: git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, shipping-and-launch Embedded: embedded-debugging, rtos-and-concurrency, peripheral-driver-design, embedded-build-and-toolchain

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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. Very specific:

    Every skill lives in skills/<name>/SKILL.md

    line 28
  2. Distinctive:

    Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification

    line 31
  3. Distinctive:

    Always: Follow the skill-anatomy.md format for new skills

    line 42
  4. Distinctive:

    Never: Add skills that are vague advice instead of actionable processes

    line 43
  5. Distinctive:

    Never: Duplicate content between skills — reference other skills instead

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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

ae-skills

This is the ae-skills project — a collection of production-grade engineering skills for AE (Application Engineers) in the embedded systems space. Covers firmware development, RTOS-based design, peripheral drivers, and embedded debugging. Built for engineers working with GCC, Arm toolchains, RTOS (Zephyr/FreeRTOS), BMS, Bluetooth, and other embedded technologies.

Project Structure

skills/       → Core skills (SKILL.md per directory)
agents/       → Reusable agent personas (code-reviewer, test-engineer, security-auditor)
hooks/        → Session lifecycle hooks
.claude/commands/ → Slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship)
references/   → Supplementary checklists (testing, performance, security, accessibility)
docs/         → Setup guides for different tools

Skills by Phase

Define: interview-me, idea-refine, spec-driven-development Plan: planning-and-task-breakdown Build: incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, api-and-interface-design Verify: debugging-and-error-recovery Review: code-review-and-quality, code-simplification, security-and-hardening, performance-optimization Ship: git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, shipping-and-launch Embedded: embedded-debugging, rtos-and-concurrency, peripheral-driver-design, embedded-build-and-toolchain

Conventions

  • Every skill lives in skills/<name>/SKILL.md
  • YAML frontmatter with name and description fields
  • Description starts with what the skill does (third person), followed by trigger conditions ("Use when...")
  • Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification
  • References are in references/, not inside skill directories
  • Supporting files only created when content exceeds 100 lines

Commands

  • npm test — Not applicable (this is a documentation project)
  • Validate: Check that all SKILL.md files have valid YAML frontmatter with name and description

Boundaries

  • Always: Follow the skill-anatomy.md format for new skills
  • Never: Add skills that are vague advice instead of actionable processes
  • Never: Duplicate content between skills — reference other skills instead

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