marketing-council-pack-conventions

Marketing Council Pack Conventions

Generated from imMamdouhaboammar/marketing-council-pack on 2026-09-03

Overview

This skill teaches Claude the development patterns and conventions used in marketing-council-pack.

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 33 analyzed commits.

Commit Style: Conventional Commits

Prefixes Used

• fix
• test
• ci
• feat
• docs
• chore

Message Guidelines

• Average message length: ~51 characters
• Keep first line concise and descriptive
• Use imperative mood ("Add feature" not "Added feature")

Commit message example

ci: add plugin release verification workflow

Commit message example

test: define ChatGPT plugin discovery and routing regression gates

Commit message example

feat: add canonical focused-skill routing registry

Commit message example

fix: bump OpenAI plugin release and discovery metadata

Commit message example

chore: align Claude plugin metadata with v1.5.0

Commit message example

test: specify deterministic focused-skill routing behavior

Commit message example

feat: add deterministic dynamic skill router

Commit message example

feat: make Marketing Council the canonical dynamic router

Architecture

Project Structure: Single Package

This project uses hybrid module organization.

Configuration Files

• .github/workflows/plugin-ci.yml

Guidelines

• This project uses a hybrid organization
• Follow existing patterns when adding new code

Code Style

Language: Python

Naming Conventions

Element	Convention
Files	snake_case
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 { ... }

Testing

Test Framework

No specific test framework detected — use the repository's existing test patterns.

File Pattern: *.test.ts

Test Types

• Unit tests: Test individual functions and components in isolation

Common Workflows

These workflows were detected from analyzing commit patterns.

Feature Development

Standard feature implementation workflow

Frequency: ~5 times per month

Steps:

1. Add feature implementation
2. Add tests for feature
3. Update documentation

Files typically involved:

• **/api/**

Example commit sequence:

ci: add plugin release verification workflow
test: define ChatGPT plugin discovery and routing regression gates
test: specify deterministic focused-skill routing behavior

Best Practices

Based on analysis of the codebase, follow these practices:

Do

• Use conventional commit format (feat:, fix:, etc.)
• Follow *.test.ts naming pattern
• Use snake_case for file names
• Prefer named 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. Review and customize as needed for your team.