agentleFS
iadr-deviadr-dev/colab/skills/coding/redis-agent-skills/AGENTS.md

colab / redis-agent-skills

AGENTS.md2 starsChanged 7 months agoMITView on GitHub

A collection of skills for AI coding agents working with Redis. Skills are packaged instructions and resources that extend agent capabilities. Each rule in rules/ follows this structure: python # Good example with comments python # Bad example with comments When to include "Incorrect" examples: - Use **Incorrect:** when the alternative causes real harm (race conditions, security issues, crashes, significant performance problems) - For feature-introduction rules where not using the feature is valid, use **When to use:** / **When NOT…

  • Installs packages

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

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

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

    SKILL.md, AGENTS.md: Always uppercase

    line 31
  2. Very specific:

    Use Incorrect: when the alternative causes real harm (race conditions, security issues, crashes, significant performance problems)

    line 112
  3. Very specific:

    Create skill directory: skills/{skill-name}/

    line 118
  4. Very specific:

    Create SKILL.md with frontmatter and structure above

    line 119
  5. Distinctive:

    Create README.md with user documentation

    line 130
  6. Very specific:

    Create rules/_sections.md defining categories

    line 132
  7. Very specific:

    Create rules/_template.md for contributors

    line 133
  8. Very specific:

    Add rules as rules/{prefix}-{name}.md

    line 134
  9. Very specific:

    Add skill config to packages/redis-development-build/src/config.ts

    line 135
  10. Very specific:

    Run npm run build to generate AGENTS.md

    line 136
  11. Very specific:

    Add SKILL.md to project knowledge or paste contents into conversation.

    line 183

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

AGENTS.md

This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with code in this repository.

Repository Overview

A collection of skills for AI coding agents working with Redis. Skills are packaged instructions and resources that extend agent capabilities.

Creating a New Skill

Directory Structure

skills/
  {skill-name}/               # kebab-case directory name
    SKILL.md                  # Required: skill definition with frontmatter
    AGENTS.md                 # Generated: compiled rules (for rule-based skills)
    README.md                 # Required: user documentation
    metadata.json             # Required: version and metadata
    rules/                    # For rule-based skills
      _sections.md            # Section definitions
      _template.md            # Rule template
      {prefix}-{name}.md      # Individual rules
    scripts/                  # For script-based skills (optional)
      {script-name}.sh

Naming Conventions

  • Skill directory: kebab-case (e.g., redis-development, redis-monitoring)
  • SKILL.md, AGENTS.md: Always uppercase
  • Rule files: {prefix}-{description}.md where prefix maps to section
  • Scripts: kebab-case.sh

SKILL.md Format

---
name: {skill-name}
description: {One sentence describing when to use this skill. Include trigger phrases.}
license: MIT
metadata:
  author: {organization}
  version: "1.0.0"
---

# {Skill Title}

{Brief description of what the skill does.}

## When to Apply

Reference these guidelines when:
- {Use case 1}
- {Use case 2}

## Rule Categories by Priority

| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | {Category} | HIGH | `{prefix}-` |

## Quick Reference

### 1. {Category} (HIGH)

- `{prefix}-{rule-name}` - {Brief description}

## How to Use

{Instructions for reading individual rules}

## Full Compiled Document

For the complete guide with all rules expanded: `AGENTS.md`

Rule File Format

Each rule in rules/ follows this structure:

---
title: Clear, Action-Oriented Title
impact: HIGH|MEDIUM|LOW
impactDescription: Quantified benefit (e.g., "10x faster")
tags: relevant, keywords
description: Clear, Action-Oriented Title
alwaysApply: true
---

## {Title}

{1-2 sentence explanation of the problem and why it matters}

**Correct:** Description of good approach.

```python
# Good example with comments

Incorrect: Description of problematic approach.

# Bad example with comments

Reference: Link


**When to include "Incorrect" examples:**
- Use `**Incorrect:**` when the alternative causes real harm (race conditions, security issues, crashes, significant performance problems)
- For feature-introduction rules where not using the feature is valid, use `**When to use:**` / `**When NOT needed:**` sections instead
- Rules may include multiple `**Correct:**` sections for different valid approaches (see comparison rules like `json-vs-hash.md`)

### Adding a New Skill

1. Create skill directory: `skills/{skill-name}/`
2. Create `SKILL.md` with frontmatter and structure above
3. Create `metadata.json`:
   ```json
   {
     "version": "1.0.0",
     "organization": "Your Org",
     "date": "Month Year",
     "abstract": "Description for AI agents",
     "references": ["https://..."]
   }
  1. Create README.md with user documentation
  2. For rule-based skills:
    • Create rules/_sections.md defining categories
    • Create rules/_template.md for contributors
    • Add rules as rules/{prefix}-{name}.md
    • Add skill config to packages/redis-development-build/src/config.ts
    • Run npm run build to generate AGENTS.md

Build System

The build tooling in packages/redis-development-build/ compiles individual rule files into AGENTS.md:

npm install
npm run validate  # Check rule structure
npm run build     # Generate AGENTS.md

To add a new skill to the build system, update src/config.ts:

export const SKILLS: Record<string, SkillConfig> = {
  'your-new-skill': {
    name: 'your-new-skill',
    title: 'Your New Skill',
    description: 'Description',
    skillDir: join(SKILLS_DIR, 'your-new-skill'),
    rulesDir: join(SKILLS_DIR, 'your-new-skill/rules'),
    metadataFile: join(SKILLS_DIR, 'your-new-skill/metadata.json'),
    outputFile: join(SKILLS_DIR, 'your-new-skill/AGENTS.md'),
    sectionMap: {
      prefix1: 1,
      prefix2: 2,
    },
  },
}

Best Practices for Context Efficiency

  • Keep SKILL.md under 500 lines — put detailed rules in separate files
  • Write specific descriptions — helps agents know when to activate the skill
  • Use progressive disclosure — SKILL.md summarizes, AGENTS.md has full details
  • Quantify impact — "10x faster" helps agents prioritize rules

End-User Installation

Claude Code:

cp -r skills/{skill-name} ~/.claude/skills/

Claude.ai: Add SKILL.md to project knowledge or paste contents into conversation.

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.