TomUviandClaude Opus 5
f84852d49c
The skill so far only held what we broke ourselves. Most of what is worth knowing about a new SDK is found rather than suffered — release notes, other people's articles — and that deserves a place too, on terms that stay fair to whoever wrote it. So: entries in our own words, source named and linked, and the one thing no external article can supply — what it would replace in our code and whether it is genuinely a step forward. Attribution answers plagiarism, not copyright, so nothing is pasted; an API signature is a fact, the paragraph explaining it is not ours to take. First four entries come from Natalia Panferova's writing at nilcoalescing .com: the close button role and concentric corners, both of which replace things we hand-built; ScrollPosition, which replaces one wrapper view; and the iOS 27 toolbar APIs, which we cannot use at our deployment target but which would delete a workaround the day we can. A LICENSE was overdue and now says plainly what is ours, what is Apple's and stays out of the repository, and what belongs to the authors we cite. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
25 lines
496 B
JSON
25 lines
496 B
JSON
{
|
|
"name": "pdat-swift-practice",
|
|
"version": "0.2.0",
|
|
"description": "Curated Apple platform findings with sources, plus practices learned from production incidents.",
|
|
"author": {
|
|
"name": "PDAT s.r.o.",
|
|
"email": "tomas.uvira@pdat.cz"
|
|
},
|
|
"license": "MIT",
|
|
"keywords": [
|
|
"swift",
|
|
"swiftui",
|
|
"ios",
|
|
"macos",
|
|
"watchos",
|
|
"core-data",
|
|
"xcodegen",
|
|
"swift-testing"
|
|
],
|
|
"skills": [
|
|
"./skills/xcode-practice",
|
|
"./skills/apple-findings"
|
|
]
|
|
}
|