Global Coding Style

Enforce TypeScript and Remotion coding conventions with ESLint rules and path aliases.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/chad3814/cawpile-video-gen --skill global-coding-style-chad3814
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Global Coding Style
Source: https://github.com/chad3814/cawpile-video-gen/tree/main/.claude/skills/spekka-global-coding-style
Command: npx skills add https://github.com/chad3814/cawpile-video-gen --skill global-coding-style-chad3814

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript and Remotion coding style conventions to ensure consistency across projects, improving readability and maintainability.

Core Features & Use Cases

  • Enforces naming standards (camelCase for variables/functions, PascalCase for types/components, UPPER_SNAKE for constants).
  • Sets import organization, frame-based timing conventions, and path alias usage.
  • Use Case: When starting a new Remotion project, apply these conventions to keep codebase consistent across teams.

Quick Start

Follow these guidelines in all new files and during refactoring to align with the Global Coding Style.

Frequently Asked Questions about Global Coding Style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TypeScript naming conventions in a Remotion project?

TypeScript naming conventions in Remotion projects are enforced by applying consistent rules: camelCase for variables and functions, PascalCase for types and components, and UPPER_SNAKE for constants to improve maintainability.

What is the standard way to handle frame-based timing in Remotion?

Frame-based timing in Remotion is standardized through structural guidelines that ensure animations and utilities maintain consistent timing conventions, making the codebase more readable across teams.

Can I use ESLint to enforce coding style for TypeScript and Remotion?

Yes, ESLint with TypeScript rules is implemented to enforce coding conventions, handling import organization and path aliases using the @/ syntax to ensure readable code.

How do I organize imports and path aliases in TypeScript Remotion codebases?

Import organization and path aliases in TypeScript Remotion codebases are structured by using ESLint rules and the @/ path alias, ensuring consistent import ordering and architecture decisions across components.

Does this coding style apply to existing Remotion components and utilities?

Yes, the coding style applies to TypeScript and Remotion codebases across components, animations, and utilities. You can follow these guidelines during refactoring to align with the conventions.