project-conventionslisted

# Project Conventions This skill guides you in discovering and applying project-specific conventions. Every codebase has its own patterns and practices - your job is to find them and follow them. --- ## Convention Discovery Process ### Step 1: Project Configuration Check these files for explicit conventions: **Code Style:** - `.eslintrc*`, `eslint.config.*` - JavaScript/TypeScript linting rules - `.prettierrc*`, `prettier.config.*` - Formatting rules - `pyproject.toml`, `setup.cfg`, `.flake8` - Python config - `.editorconfig` - Editor settings - `ruff.toml`, `.ruff.toml` - Ruff linter config **Project Structure:** - `tsconfig.json` - TypeScript paths and settings - `package.json` - Scripts, dependencies - `pyproject.toml` - Python project config **Documentation:** - `CONTRIBUTING.md` - Contribution guidelines - `CLAUDE.md` or `AGENTS.md` - AI coding guidelines - `README.md` - Project overview - `docs/` - Extended documentation ### Step 2: Existing Code Patterns Study the codebase to find implicit conventions: **File Organization:** - List component directories to understand organization - Search for test file patterns (e.g., `*.test.*`, `*_test.*`, `test_*`) - List utility directories to see how helpers are organized **Naming Patterns:** - Search for exported function declarations to identify naming style - Search for class declarations to identify class naming style **Import Patterns:** - Search for import statements to identify absolute vs relative import style