Does this skill automatically write code?

No, it is a diagnostic and planning tool. It generates a detailed implementation plan that must be approved before any coding begins.

What architectural guardrails does it check?

It verifies rules such as restricting mDNS-sd imports to specific crates, preventing type duplication in koi-common, and ensuring cross-crate dependencies flow correctly.

How does the Explore skill prevent technical debt?

It forces a check for existing constants and types across all crates, preventing duplication and ensuring that new logic is placed in the correct architectural layer.

Which codebase is this skill optimized for?

This skill is specifically tailored for the Koi project, a local mDNS service discovery tool organized into multiple specialized Rust crates.

What is the main purpose of the Explore skill?

The Explore skill ensures architectural consistency by requiring a structured discovery phase—mapping files, types, and patterns—before any production code is written.

Koi Codebase Explorer

Name: Koi Codebase Explorer
Author: sylin-org

bysylin-org

0•

開発者ツール

Executes a structured pre-implementation analysis to map dependencies, architectural patterns, and guardrails before writing production code.

The Explore skill is a specialized discovery workflow designed specifically for the Koi mDNS service discovery ecosystem. It prevents architectural drift and technical debt by enforcing a mandatory analysis phase before any implementation begins. By systematically scanning across specialized crates—such as koi-mdns, koi-common, and koi-client—it helps Claude identify existing constants, types, and patterns, ensuring new code aligns with project-specific crate hierarchies and domain logic. This skill is essential for maintaining code quality in complex, multi-crate Rust projects where strict adherence to architectural guardrails is required.