skills.rest
sjc786526-coder
sjc786526-coderCOMMUNITY
Explore all skills by this author →
GitHub

path-types

Selects Rust path types for app-server and exec-server protocol code.

Updated Aug 4, 2026
Search Tags:#codex#rust#protocol design#backwards compatibility#path types#uri migration#type selection
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill path-types-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: path-types
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/path-types
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill path-types-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the wrong Rust type for operating system paths causes protocol incompatibilities, broken cross-platform path handling, and failed URI migrations in the Codex repository. This Skill provides clear decision rules for which path type to use in each context. ## Core Features & Use Cases - Type Selection Rules: Defines when to use LegacyAppPathString, PathUri, AbsolutePathBuf, or PathBuf across app-server, exec-server, and shared dependencies. - Migration Requirements: Lists constraints for the ongoing URI migration, including backwards compatibility with legacy native-path strings and fail-closed error handling for security-relevant paths. - Use Case: When adding a new path-bearing field to an exec-server protocol type, apply the guidance to use PathUri at the boundary and convert internally, keeping model-visible text unchanged. ## Quick Start Ask the assistant to apply the path-types guidance when defining a new path-bearing type in the app-server or exec-server protocol code.

Frequently Asked Questions about path-types

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

FAQPage Schema
How do I choose a Rust path type for protocol code?▼

Use LegacyAppPathString in app-server protocol types for backwards compatibility, PathUri in exec-server protocol types, and AbsolutePathBuf or PathBuf for host-local logic like config values. Convert to PathUri at the protocol boundary.

What is the difference between PathUri and AbsolutePathBuf in Rust?▼

PathUri represents paths as URIs and is used at protocol boundaries and in exec-server APIs, while AbsolutePathBuf is a host-local filesystem path type used for internal logic such as configuration values.

Should model tool call arguments use PathUri or String?▼

Tool call arguments that the model generates should be deserialized as regular Strings with feature-specific path handling code, since models may produce raw relative or absolute paths for any operating system.

How should path conversion errors be handled during URI migration?▼

Path conversion errors should be fail-closed for security-relevant paths and fail-open for UI and diagnostics. Migration should avoid adding significant new failure modes, surfacing errors only where necessary.

When should existing path code be migrated to PathUri?▼

Existing code should only be changed when explicitly requested, with minimal and proportional edits. The guidelines describe the target state of an ongoing migration, not a mandate to rewrite working code.

Related Skills

Explore More Software Engineering Skills→
VKirillVKirill
15

codex

Configure and run OpenAI Codex CLI with sandbox and approval policies.

Community
Advanced
openharmonyopenharmony

ohtest

Generate Hypium-compatible unit-test suites from .d.ts typings for OpenHarmony.

Official
Intermediate
BarisSozenBarisSozen
1

code-consistency-validator

Validate cross-language type consistency across Rust, TypeScript, and PostgreSQL boundaries.

Community
Advanced
githubgithub
38.5k

mcp-copilot-studio-server-generator

Generates MCP server implementations and Power Platform connector files for Copilot Studio integration.

Official
Intermediate