agentleFS
cubxxwcubxxw/agent-kit/.claude/skills/agent-kit/SKILL.md

agent-kit-conventions

Skill2 starsChanged 3 months agoMITView on GitHub

Development conventions and patterns for agent-kit. Python project with freeform commits.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these commit message conventions based on 1 analyzed commits.

    line 30
  2. Distinctive:

    Keep first line concise and descriptive

    line 37
  3. Distinctive:

    Use imperative mood ("Add feature" not "Added feature")

    line 38
  4. Distinctive:

    Follow existing patterns when adding new code

    line 56
  5. Distinctive:

    Use camelCase for file names

    line 99
  6. Distinctive:

    Don't deviate from established patterns without discussion

    line 104

≈ “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

Agent Kit Conventions

Generated from cubxxw/agent-kit on 2026-08-05

Overview

This skill teaches Claude the development patterns and conventions used in agent-kit.

Tech Stack

  • Primary Language: Python
  • Architecture: hybrid module organization
  • Test Location: separate

When to Use This Skill

Activate this skill when:

  • Making changes to this repository
  • Adding new features following established patterns
  • Writing tests that match project conventions
  • Creating commits with proper message format

Commit Conventions

Follow these commit message conventions based on 1 analyzed commits.

Commit Style: Free-form Messages

Message Guidelines

  • Average message length: ~29 characters
  • Keep first line concise and descriptive
  • Use imperative mood ("Add feature" not "Added feature")

Commit message example

add taste skill and top radar

Architecture

Project Structure: Single Package

This project uses hybrid module organization.

Guidelines

  • This project uses a hybrid organization
  • Follow existing patterns when adding new code

Code Style

Language: Python

Naming Conventions

ElementConvention
FilescamelCase
FunctionscamelCase
ClassesPascalCase
ConstantsSCREAMING_SNAKE_CASE

Import Style: Relative Imports

Export Style: Named Exports

Preferred import style

// Use relative imports
import { Button } from '../components/Button'
import { useAuth } from './hooks/useAuth'

Preferred export style

// Use named exports
export function calculateTotal() { ... }
export const TAX_RATE = 0.1
export interface Order { ... }

Best Practices

Based on analysis of the codebase, follow these practices:

Do

  • Use camelCase for file names
  • Prefer named exports

Don't

  • Don't deviate from established patterns without discussion

This skill was auto-generated by ECC Tools. Review and customize as needed for your team.

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.