agentleFS
brbndonbrbndon/AppleDevelopmentFoundation/.agents/skills/swift-package-module-author/SKILL.md

swift-package-module-author

Skill2 starsChanged 2 months agoMITView on GitHub

Use when adding an independently importable Swift Package module in the active workspace. Do not use for an app-local feature, extraction review, or editing AppleDevelopmentFoundation archived package code unless explicitly asked.

The file

Files
SKILL.md

Swift package module author

Work in the active workspace package (the consumer's Package.swift), not AppleDevelopmentFoundation's archived package unless the user explicitly requests it.

Confirm two plausible consumers and a non-overlapping responsibility. Check dependency direction, define minimal products/targets, keep public APIs documented and small, create focused tests and generic example use, then update the dependency graph.

Inputs: proposed module responsibility and consumers. Output: a scoped module implementation in the consumer package and package-wide verification. Stop at a plan when implementation was not requested.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.