What problem does it solve? It ensures that a Rule or Skill intended for cross-project reuse is properly qualified for portability before authoring, and that every portability obligation is verifiably closed at handoff, preventing project-local assumptions from leaking into shared artifacts. ## Core Features & Use Cases - Portability qualification: Judges ownership, provenance, and evidence to confirm a request is a genuinely portable cross-project Rule or Skill, routing project-local artifacts and Setup Authoring Contracts to their proper owners. - Public workflow delegation: Passes one closed portability input unchanged to the public write-rules-and-skills workflow and preserves its terminal result (COMPLETE, NEEDS_INPUT, or BLOCKED). - Handoff closure: Maintains a closure account binding every obligation to observable public outputs tied to the final Candidate fingerprint. - Use Case: A team wants to promote a project-specific linting Rule into a shared SmartKit Rule used across repositories; this Skill qualifies the request, authors it through the public workflow, and closes all portability obligations at handoff. ## Quick Start Use the write-shared-rules-and-skills skill to qualify and author this Rule as a portable cross-project SmartKit Rule.
