Enforce consistent public API naming across the OpenLark Rust SDK.
npx skills add https://github.com/foxzool/open-lark --skill openlark-naming
Please help me install this Agent Skill. Skill: openlark-naming Source: https://github.com/foxzool/open-lark/tree/main/.agents/skills/openlark-naming Command: npx skills add https://github.com/foxzool/open-lark --skill openlark-naming
OpenLark naming conventions provide a standardized approach for public API types (Client/Service/Resource/Request/Builder) to improve readability, maintainability, and onboarding when designing or refactoring APIs. It helps manage meta call chains and module exports/preludes to avoid semantic clashes like DocsService in related crates.
Review a target module and propose naming changes that align with the OpenLark naming conventions.
High-intent search queries and answers about installing and using this skill.
To enforce consistent API naming across an OpenLark Rust SDK, apply standardized conventions to Client, Service, Resource, Request, and Builder types, ensuring clear export paths and prelude organization.
Naming collisions in versioned Rust modules happen when semantic clashes occur across related crates, such as overlapping DocsService types. You prevent them by guiding versioned naming and clarifying meta call chains.
The best way to organize a Rust SDK prelude to avoid API name collisions is to establish explicit naming rules for Service and Resource types, detecting and resolving conflicts across module exports.
Yes, you can use naming conventions to clarify meta call chains like client.xxx.v1.yyy in Rust by applying versioned naming rules that prevent collisions and maintain a clean API surface.
To review a Rust module and propose API naming changes for better readability, identify target types and align their Client, Service, Resource, Request, and Builder names with OpenLark conventions.
Standardizing public API types does improve onboarding when refactoring a Rust SDK by providing a standardized approach for Client, Service, and Builder types, which enhances overall maintainability and readability.
modrinthGenerate type-safe TypeScript API client modules from OpenAPI schemas.
marcosd4hResolve PE import and export relationships across analyzed modules.
qol-toolsStandardize Rust coding conventions for error handling, filesystem operations, and cross-platform layout.
CallMeLuigiv2Enforce Rust naming, formatting, and lint conventions during code reviews.
