cubxxw 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
| 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.