docs: add software-vision and android-backup-restore skills with android scripts

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
BluscreamandClaude Opus 5.5 committed 2026-10-30 13:00:44 +01:00
1 parent a16a879b1e
commit 5e6abadb95
12 files changed
+1261 -1

No files matched your search

+11 -1
View File
@@ -26,6 +26,14 @@ reasons attached, not style trivia — most exist because ignoring them caused a
> When in doubt about which mode you are in, **ask** — it changes the answer on strictness,
> file size, typing, and test policy all at once.
> [!IMPORTANT]
> **A new software idea starts with research, not code.** When the user describes a tool, app,
> service, or other project they want built, follow
> [`software-vision.md`](skills-public/software-vision.md) first: find existing projects to use,
> extend, or fork (web searches and user reviews first, then training-data recall, then
> throwaway clones), and present the options before scaffolding anything — unless the user
> explicitly opted out of research.
Per-language specifics live in [`code-languages/`](skills-public/code-languages/):
| Language | Rules |
@@ -115,7 +123,9 @@ a fresh implementation will rediscover slowly and incompletely.
Before hand-rolling any subsystem — a protocol client, a parser, a date formatter, a
debounce, a retry/backoff, a semver comparator — **search first and state the finding.**
Prefer official/first-party SDKs over third-party wrappers.
Prefer official/first-party SDKs over third-party wrappers. The same ordering applies to a
whole project idea, not just a subsystem — see
[`software-vision.md`](skills-public/software-vision.md).
### The corollary: new generic code becomes its own package