feat: add flycatch-website ECC bundle

.agents/skills/flycatch-website/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: flycatch-website-conventions
+description: Development conventions and patterns for flycatch-website. Python project with conventional commits.
+---
+
+# Flycatch Website Conventions
+
+> Generated from [flycatch/flycatch-website](https://github.com/flycatch/flycatch-website) on 2026-08-17
+
+## Overview
+
+This skill teaches Claude the development patterns and conventions used in flycatch-website.
+
+## Tech Stack
+
+- **Primary Language**: Python
+- **Architecture**: type-based module organization
+- **Test Location**: mixed
+- **Test Framework**: vitest
+
+## 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 3 analyzed commits.
+
+### Commit Style: Conventional Commits
+
+### Prefixes Used
+
+- `feat`
+
+### Message Guidelines
+
+- Average message length: ~152 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
+
+
+*Commit message example*
+
+```text
+feat(auth-rbac): add comprehensive data model, implementation plan, quickstart guide, and research documentation for authentication and authorization using JWT and RBAC
+```
+
+## Architecture
+
+### Project Structure: Monorepo
+
+This project uses **type-based** module organization.
+
+### Configuration Files
+
+- `.github/workflows/quality-gates.yml`
+- `apps/Administration-FE/Dockerfile`
+- `apps/Administration-FE/package.json`
+- `deployment/docker-compose.yml`
+
+### Guidelines
+
+- Group code by type (components, services, utils)
+- Keep related functionality in the same type folder
+- Avoid circular dependencies between type folders
+
+## Code Style
+
+### Language: Python
+
+### Naming Conventions
+
+| Element | Convention |
+|---------|------------|
+| Files | camelCase |
+| Functions | camelCase |
+| Classes | PascalCase |
+| Constants | SCREAMING_SNAKE_CASE |
+
+### Import Style: Relative Imports
+
+### Export Style: Mixed Style
+
+
+*Preferred import style*
+
+```typescript
+// Use relative imports
+import { Button } from '../components/Button'
+import { useAuth } from './hooks/useAuth'
+```
+
+## Testing
+
+### Test Framework: vitest
+
+### File Pattern: `*.spec.ts`
+
+### Test Types
+
+- **Unit tests**: Test individual functions and components in isolation
+- **Integration tests**: Test interactions between multiple components/services
+- **E2e tests**: Test complete user flows through the application
+
+
+*Test file structure*
+
+```typescript
+import { describe, it, expect } from 'vitest'
+
+describe('MyFunction', () => {
+  it('should return expected result', () => {
+    const result = myFunction(input)
+    expect(result).toBe(expected)
+  })
+})
+```
+
+## Error Handling
+
+### Error Handling Style: Try-Catch Blocks
+
+This project uses **custom error classes** for specific error types.
+
+
+*Standard error handling pattern*
+
+```typescript
+try {
+  const result = await riskyOperation()
+  return result
+} catch (error) {
+  console.error('Operation failed:', error)
+  throw new Error('User-friendly message')
+}
+```
+
+## Best Practices
+
+Based on analysis of the codebase, follow these practices:
+
+### Do
+
+- Use conventional commit format (feat:, fix:, etc.)
+- Write tests using vitest
+- Follow *.spec.ts naming pattern
+- Use camelCase for file names
+- Prefer mixed exports
+
+### Don't
+
+- Don't write vague commit messages
+- Don't skip tests for new features
+- Don't deviate from established patterns without discussion
+
+---
+
+*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*

.agents/skills/flycatch-website/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Flycatch Website"
+  short_description: "Repo-specific patterns and workflows for flycatch-website"
+  default_prompt: "Use the flycatch-website repo skill to follow existing architecture, testing, and workflow conventions."
+policy:
+  allow_implicit_invocation: true