agent-kit-conventions
Skill2 starsChanged 3 months agoMITView on GitHub
Development conventions and patterns for agent-kit. Python project with freeform commits.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- agent-kit-conventionsSkill
- archifySkill
- boundary-demoSkill
- deepen-designSkill
- design-taste-frontendSkill
- excalidraw-architectureSkill
- frontend-designSkill
- hyperframes-cliSkill
- hyperframes-registrySkill
- hyperframesSkill
- manage-agent-kitSkill
- mcp-builderSkill
- media-useSkill
- product-qaSkill
- source-driven-developmentSkill
- threads-oral-notesSkill
- ui-ux-pro-maxSkill
- youtube-scriptSkill
- youtube-script-writerSkill
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
- Distinctive: line 30
Follow these commit message conventions based on 1 analyzed commits.
- Distinctive: line 37
Keep first line concise and descriptive
- Distinctive: line 38
Use imperative mood ("Add feature" not "Added feature")
- Distinctive: line 56
Follow existing patterns when adding new code
- Distinctive: line 99
Use camelCase for file names
- Distinctive: line 104
Don't deviate from established patterns without discussion
≈ “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.
Files
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 radarArchitecture
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
| Element | Convention |
| Files | camelCase |
| Functions | camelCase |
| Classes | PascalCase |
| Constants | SCREAMING_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.
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
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.

