swift-engineering

Route Swift engineering requests to the canonical skill surface.

3|Updated Mar 24, 2026

Search Tags:#discovery #provenance #swift #engineering #rules #wrapper #canonical-surface

Ready to run

npx skills add https://github.com/ldilov/harness-forge --skill swift-engineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swift-engineering
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/swift-engineering
Command: npx skills add https://github.com/ldilov/harness-forge --skill swift-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovers and routes requests to the canonical Swift engineering skill surface, preventing duplication of guidance and ensuring a single source of truth for Swift engineering tasks.

Core Features & Use Cases

Discovery wrapper that points to the canonical surface for Swift engineering.
Loads deeper rules, knowledge, workflows, and provenance context only when needed to avoid redundancy.
Guards guidance by ensuring the active agent context is loaded from the canonical surface first.

Quick Start

Initialize the Swift engineering discovery wrapper to load the canonical surface and begin guided exploration.

Frequently Asked Questions about swift-engineering

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

FAQPage Schema

How do I avoid duplicating Swift engineering guidance across different projects?▼

A Swift engineering discovery wrapper routes requests to a canonical surface to avoid duplicating guidance and maintain a single source of truth. It ensures the active agent context loads correctly before pulling deeper rules or workflows.

What is a canonical surface for Swift engineering tasks?▼

A canonical surface for Swift engineering acts as the central routing point that prevents guidance duplication by loading rules, knowledge, workflows, and provenance context selectively. It guarantees a single source of truth for platform-specific client code.

How do I discover provenance context for Swift packages?▼

You discover provenance context for Swift packages by initializing a discovery wrapper that loads the canonical Swift engineering surface first. It selectively pulls deeper provenance rules and knowledge only as needed for your specific task.

Does this Swift engineering wrapper support governance contexts for apps?▼

Yes, the Swift engineering wrapper supports governance contexts for apps, packages, and platform-specific client code. It routes governance requests to the canonical surface to load the appropriate rules and provenance context dynamically.

When do I need to load deeper rules from the canonical Swift engineering surface?▼

You load deeper rules from the canonical Swift engineering surface only when the initial discovery wrapper determines that additional context is required for your specific Swift packages or platform-specific client code tasks.