Does it recommend third-party packages?

No, its primary philosophy is to use the framework's built-in tools first. It helps identify when you are reaching for an external library for a problem the framework already solves.

Which frameworks does this skill support?

The skill provides specific guidance for Django, Laravel, Next.js, Rails, Phoenix, Spring Boot, FastAPI, Remix, and NestJS, but its universal principles apply to any opinionated framework.

Can I use this for existing projects?

Yes, the skill is excellent for refactoring and code reviews, helping you align legacy code with modern framework standards and native features.

How does this skill help with technical debt?

By enforcing 'the framework way,' it prevents the creation of custom, complex abstractions that are difficult to maintain and ensures the codebase remains familiar to any developer who knows the framework.

Framework Conventions Guide

Name: Framework Conventions Guide
Author: jayteealao

byjayteealao

API Development

Enforces framework-native patterns and idiomatic coding practices to simplify application architecture and reduce technical debt.

About

The Framework Conventions Guide is designed to help developers stop fighting their tools and start embracing 'convention over configuration.' By applying universal principles used by major framework creators, this skill guides Claude to write code that is idiomatic to environments like Django, Laravel, Rails, and Next.js. It focuses on using built-in framework features over external libraries, mapping logic to RESTful resources, and maintaining rich domain models. Whether you are refactoring a complex codebase or starting a new project, this skill ensures your architecture remains simple, maintainable, and aligned with the framework's intended philosophy.

Key Features

Automatic detection and application of framework-specific conventions for Django, Rails, Next.js, and more
Universal RESTful resource mapping to replace custom, non-standard API actions
Domain-driven state management patterns using records and enums instead of fragile boolean flags
0 GitHub stars
Anti-pattern detection to prevent unnecessary third-party dependency bloat
Guidance on 'fat models' and 'thin controllers' to centralize business logic effectively

Use Cases

Refactoring custom service layers into idiomatic framework-native models and controllers
Onboarding developers to a new framework by enforcing standard naming and architectural patterns
Reviewing existing codebases to identify and remove complexity that violates framework opinions

About

Key Features

Automatic detection and application of framework-specific conventions for Django, Rails, Next.js, and more
Universal RESTful resource mapping to replace custom, non-standard API actions
Domain-driven state management patterns using records and enums instead of fragile boolean flags
0 GitHub stars
Anti-pattern detection to prevent unnecessary third-party dependency bloat
Guidance on 'fat models' and 'thin controllers' to centralize business logic effectively

Use Cases

Refactoring custom service layers into idiomatic framework-native models and controllers
Onboarding developers to a new framework by enforcing standard naming and architectural patterns
Reviewing existing codebases to identify and remove complexity that violates framework opinions