coding-standards
Flequit プロジェクトのコーディング標準への準拠をチェックします。命名規則、ファイル構造、型定義、エラーハンドリング、コメント、インポート順序などのコーディング標準チェックに使用します。
coding
standards
SKILL.md.claude/skills/coding-standards
GitHubCoding Standards Skill
Use this skill to check or align code with project conventions.
Naming
- TypeScript:
camelCasefor vars/functions,PascalCasefor types/components. - Rust:
snake_casefor vars/functions,PascalCasefor types/enums. - Constants:
SCREAMING_SNAKE_CASE. - File and directory names:
kebab-caseunless framework conventions require otherwise.
File structure
- Avoid oversized files; split by responsibility when practical.
- Keep one clear responsibility per file/module.
Typing
- Avoid
anyunless explicitly justified. - Model optional vs required fields clearly.
- Keep return types and DTO/domain boundaries explicit.
Error handling
- Handle expected failure paths explicitly.
- Do not swallow exceptions silently.
- Keep error messages actionable and consistent.