Results for “idioms”

Facilitate a structured conversation to define language-specific idioms and patterns for a repository. Produces a language-idioms.md document consumed by multiple atoms to adapt pseudocode defaults to the project's language. Use when setting up a new project, switching languages, or when the user says 'setup language', 'define language idioms', 'configure language', 'language patterns', or 'adapt for Go/Rust/Python'.

The English summary is being prepared. Showing the original description.

Simplify Rust code in RTK by replacing verbose loops, unnecessary copies, and excessive abstractions with common Rust patterns. Preserve behavior and project requirements, including error context, fallback handling, exit codes, and existing test modules.

• Simplifying verbose loops and string construction
• Removing unnecessary string copies
• Reducing nested conditional and error handling code

Use when writing production-grade GDScript — performance idioms, metaprogramming, @tool lifecycle, async pitfalls, signal/Callable trade-offs, profiler-driven idioms, and common pitfalls

The English summary is being prepared. Showing the original description.

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task; Use when designing processes or debugging BEAM…

The English summary is being prepared. Showing the original description.

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

The English summary is being prepared. Showing the original description.

Modern C# idioms for any .NET project (C# 10+, .NET 6+): nullable reference types, records, readonly structs, primary constructors, pattern matching, async/await with CancellationToken, IDisposable/IAsyncDisposable, file-scoped namespaces, var usage, naming conventions (PascalCase members, _camelCase fields, I-prefixed interfaces), and class design rules. Apply whenever the project is a .NET 6+ project. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write self-documenting immutable value types with records and readonly structs. - Handle nullable reference types explicitly to eliminate NullReferenceException at compile time. - Implement async/await correctly with CancellationToken propagation and ConfigureAwait(false) in libraries. - Dispose unmanaged resources correctly via IDisposable / IAsyncDisposable and using statements. - Apply C# pattern matching (switch expressions, property patterns, list patterns) for cleaner branching logic. Do NOT use this skill for: - Framework-specific idioms (ASP.NET Core controllers, minimal APIs, EF Core — those live in aspnet-core-plugin skills). - Build tooling (dotnet CLI, NuGet, csproj) — see csharp-foundation:dotnet-tooling. - Testing patterns — see csharp-foundation:dotnet-testing.

The English summary is being prepared. Showing the original description.

Modern PHP idioms for any PHP project (PHP 8.1+): readonly properties, enums, match expressions, constructor property promotion, typed properties, named arguments, nullsafe operator, first-class callable syntax, strict_types, PSR-12 style, and null discipline. Apply when the project is a PHP 8.1+ project. Stack-agnostic — referenced by every PHP plugin in the marketplace. Use this skill to: - Write strongly-typed, immutable-by-default value objects with readonly properties and enums. - Replace switch ladders and magic constants with match expressions and backed enums. - Cut constructor boilerplate with property promotion and express optionality with typed nullable returns. - Keep code PSR-12 compliant with declare(strict_types=1) in every file. Do NOT use this skill for: - Framework-specific idioms (Eloquent, Doctrine, Symfony services, Laravel facades — those live in framework plugin skills). - Composer / autoloading / dependency management — see php-foundation:composer-tooling. - Testing patterns — see php-foundation:php-testing.

The English summary is being prepared. Showing the original description.

Modern Java idioms for any JVM project (Java 17+): records, sealed types, text blocks, pattern matching, Optional discipline, streams, immutability, null safety, package layout, var usage, and code organisation. Apply when the project is a Java 17+ project. Stack-agnostic — referenced by every Java plugin in the marketplace. Use this skill to: - Write self-documenting, immutable-by-default value types with records. - Model closed type hierarchies with sealed classes and interfaces. - Handle optionality explicitly with Optional instead of returning null. - Write expressive pipelines with Stream API without performance footguns. - Lay out packages consistently (feature-first or layer-first) and keep class responsibilities tight. Do NOT use this skill for: - Framework-specific idioms (Spring annotations, JPA mappings — those live in framework plugin skills). - Build tooling (Maven/Gradle) — see java-foundation:build-tooling. - Testing patterns — see java-foundation:jvm-testing.

The English summary is being prepared. Showing the original description.

Modern Python idioms for any Python 3.10+ project: PEP 8 style, PEP 484/526 type hints, dataclasses, pathlib, enums, f-strings, structural pattern matching (match/case), context managers, exception handling, and null discipline. Stack-agnostic — referenced by every Python plugin in the marketplace. Use this skill to: - Write strongly-typed code with type hints on every function signature and class attribute. - Replace isinstance chains and magic constants with match/case and enums. - Use dataclasses or NamedTuple for value objects and data containers. - Handle resources safely with context managers and pathlib for all file paths. - Apply PEP 8 naming and structure conventions consistently. Do NOT use this skill for: - Framework-specific idioms (Django ORM, FastAPI routers, Flask blueprints — those live in framework plugin skills). - Packaging and dependency management — see python-foundation:python-tooling. - Testing patterns — see python-foundation:pytest-testing.

The English summary is being prepared. Showing the original description.

Write, review, and modernize Perl 5.36+ applications using clear function parameters, focused error handling, and organized modules. Includes examples for classes, regular expressions, file operations, formatting, code checks, and dependency management.

• Write new Perl code and modules
• Review code against modern Perl conventions
• Update legacy code for Perl 5.36+

Write, review, and refactor Python code using PEP 8 style conventions, type hints that describe expected data types, and clear error handling. Includes package organization and memory-conscious patterns to support readable, maintainable applications.

• Reviewing Python code for readability and style
• Adding type hints and improving error handling
• Organizing Python packages and modules

Review Flutter and Dart code using a checklist that adapts to the project's state management library. Check interface structure, asynchronous operations, performance, tests, accessibility, and security to identify issues across the application.

• Reviewing a Flutter app before release
• Checking state management design
• Investigating unnecessary screen rebuilds

Develop Rust filters for RTK through tests written before implementation. Use real command output as test inputs, check output snapshots and unexpected inputs, verify a minimum reduction target, and complete formatting, linting, and test checks before finishing.

• Adding a new RTK command filter
• Checking filtered output against saved snapshots
• Testing empty, malformed, or ANSI-colored input

Review interface copy for assumptions about disability, gender, or culture. Suggest neutral wording, clearer instructions, and constructive error messages that guide people through problems without blaming them or relying on culturally specific expressions.

• Reviewing interface copy for exclusionary language
• Rewriting error messages that blame users
• Replacing gender assumptions with neutral wording

Learn to examine compiled programs through one interactive lesson per session. Labs and quizzes cover file formats, machine instructions, program behavior, and analysis tools, while recorded observations provide evidence for completing each lesson and resuming later.

• Learn to read programs you compiled yourself
• Study binary formats and machine instructions
• Check analysis claims against observed output

Guide changes to SGLang runtime configuration and shared process state. Identify where resolved settings, runtime flags, resources, and per-forward state belong, and use the documented access patterns and checks when developing or testing.

• Review how server settings are read and updated
• Choose where shared and per-forward state should live
• Check configuration publication order in worker processes

Turn a written traffic situation into a Scenic file, which describes possible scenes using placement rules and constraints. Select suitable maps and actors, then check that the file compiles and can generate at least one scene.

• Create a scenario with a car cutting in from the right
• Describe a pedestrian crossing ahead of the main vehicle
• Build an unsignalized intersection scenario

Translate marketing copy, interface text, social posts, support replies, and documentation while preserving brand voice. Adapt idioms, cultural references, and local conventions for the audience, respect length limits, and keep placeholders and markup intact.

• Translate marketing copy while keeping brand voice
• Localize interface text within character limits
• Adapt social posts for a different region

Tell bedtime fables and explain the stories behind Chinese idioms for children aged 3–12. Offer 20 stories with sources, narrate selected tales in full, and adapt wording and explanations to the child's age.

• Choose a bedtime story from 20 suggestions
• Tell a specific fable in full
• Explain a Chinese idiom through its origin story

Write, review, and refactor Python code using concrete readability rules. Keep functions focused, reduce nested logic, clarify names and expressions, and apply Python features such as comprehensions, dataclasses, and pathlib while respecting existing codebase conventions.

• Refactoring long functions and deeply nested logic
• Reviewing names and complex expressions
• Organizing code with Python standard library features

Fix Native SDK build failures caused by older Zig APIs. Organized by compiler error, this guide shows Zig 0.16 patterns for file access, output, lists, processes, environment variables, clocks, networking, and build configuration.

• Migrating older Zig code to Zig 0.16
• Fixing file access and output errors
• Updating ArrayList allocation calls

Write or modernize C++ with guidance on C++20, C++23, and C++26 features. Review memory ownership, error handling, and template constraints, with recommendations for compiler protections and runtime checks that detect bugs.

• Modernize legacy C++ patterns
• Choose approaches for new C++ code
• Review memory ownership and error handling

Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).

The English summary is being prepared. Showing the original description.

Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, window) map to native. This is the end-to-end migration guide; use the `expo-dom` skill for the DOM-component mechanism itself.

The English summary is being prepared. Showing the original description.