style▌

Rails code following 37signals conventions: REST purity, fat models, thin controllers, and clarity over cleverness. \n \n Applies DHH style patterns including CRUD controllers, state-as-records instead of booleans, and Current attributes for defaults \n Covers controllers, models, views, architecture, testing, and dependency decisions with specific naming conventions and code examples \n Emphasizes vanilla Rails over gems: Minitest over RSpec, fixtures over factory_bot, Solid Queue over Sidekiq,

Create, extract, and apply portable visual design systems. A visual-style.md file defines colors, typography, layout, motion, and mood in one file that any AI tool can consume.

Korean document style consistency checker that detects tone, terminology, numbering, list formatting, quotation, and date format inconsistencies. \n \n Analyzes seven style categories (tone, terminology, numbers/units, lists, quotation/emphasis, dates/times, links) with priority-based detection \n Applies majority-rule principle to unify repeated expressions within a document or project, with context-aware recommendations based on document type (business, academic, technical, marketing) \n Provi

Battle-tested Mapbox style patterns and layer configurations for six common mapping scenarios. \n \n Includes ready-to-use JSON layer configurations for restaurant finders, real estate, data visualization, navigation, dark mode, and delivery/logistics maps \n Provides decision tree for selecting the right pattern based on content type, environment, user action, and platform \n Covers performance optimization techniques including zoom-based filtering, data-driven styling, and clustering for dense

Modern Python tooling, naming conventions, type checking, and documentation standards for maintainable codebases. \n \n Configure ruff for unified linting and formatting, replacing flake8, isort, and black with a single fast tool \n Set up strict type checking with mypy or pyright to catch errors before runtime \n Follow PEP 8 naming conventions: snake_case for functions/variables, PascalCase for classes, SCREAMING_SNAKE_CASE for constants \n Write Google-style docstrings for all public APIs wit

Swift code style conventions for clean, readable, and idiomatic code. \n \n Enforces naming conventions (UpperCamelCase for types, lowerCamelCase for everything else) and prioritizes clarity over brevity \n Advocates the \"golden path\" pattern: early returns and guards to keep happy-path logic left-aligned, avoiding deep nesting \n Covers code organization with extensions and MARK comments, memory management with weak captures, and access control best practices \n Identifies five common mistake

Generate and maintain Terraform code following HashiCorp's official style conventions. \n \n Enforces two-space indentation, lowercase underscore naming, and standard file organization across terraform.tf , providers.tf , main.tf , variables.tf , outputs.tf , and locals.tf \n Requires type and description on all variables and outputs, with validation rules and sensitive flag support for credentials \n Prioritizes for_each over count for dynamic resources, applies security hardening (encryption,

$21

Analyze one or more Yuque documents to extract writing style characteristics, helping users learn from excellent documents or maintain consistent writing style.