ZacharyZhang-NY
e74dafcd36
Three independently ugly bugs that all fed the same log flood:
* Electron's `WebFrameMain.send` writes every "Render frame was disposed"
to stderr via `console.error`. When the worker fans a second
agent-event past a reloading renderer, we produced thousands of
identical lines and stalled the main loop on stderr I/O. Added a
`mainFrame.detached` guard so the send is short-circuited before
Electron's own catch block fires, and installed a targeted filter in
`suppress-warnings.ts` (now actually imported from the entry point)
so the specific `console.error("Error sending from webFrameMain:"…)`
noise never reaches the terminal. Any other payload still surfaces.
* `dispatchAgentMessage` accepted the human-reader sentinel as a wake
target when an agent replied to `__board__` — `wakeAgentIfPossible`
then called `db.getAgent("__board__")`, threw, and the dispatcher
kept repeating on every send. Strip `HUMAN_SENDER_ID` at
`resolveMessageWakeTargets`, and keep a defense-in-depth guard in the
heartbeat so a stray caller (future automation fan-out) cannot
reintroduce the crash.
* Pi's skills loader rejects any SKILL.md whose frontmatter `name`
diverges from its parent directory. The four bundled `my-writing-style`
copies declared `name: writing-style-skill`, so every install emitted
a warning and dropped the skill. They also lived as orphan gitlinks
(mode 160000 without .gitmodules), and the global `*.md` gitignore
hid every other SKILL.md from version control. Fixed the frontmatter
to match the dir, converted the dangling submodules to plain trees,
and allowlisted `builtin-skills/**/*.md` so a fresh clone carries the
catalogue instead of silently losing it.
102 lines
2.5 KiB
Markdown
102 lines
2.5 KiB
Markdown
---
|
|
name: ios-swift-development
|
|
description: >
|
|
Develop native iOS apps with Swift. Covers MVVM architecture, SwiftUI,
|
|
URLSession for networking, Combine for reactive programming, and Core Data
|
|
persistence.
|
|
---
|
|
|
|
# iOS Swift Development
|
|
|
|
## Table of Contents
|
|
|
|
- [Overview](#overview)
|
|
- [When to Use](#when-to-use)
|
|
- [Quick Start](#quick-start)
|
|
- [Reference Guides](#reference-guides)
|
|
- [Best Practices](#best-practices)
|
|
|
|
## Overview
|
|
|
|
Build high-performance native iOS applications using Swift with modern frameworks including SwiftUI, Combine, and async/await patterns.
|
|
|
|
## When to Use
|
|
|
|
- Creating native iOS applications with optimal performance
|
|
- Leveraging iOS-specific features and APIs
|
|
- Building apps that require tight hardware integration
|
|
- Using SwiftUI for declarative UI development
|
|
- Implementing complex animations and transitions
|
|
|
|
## Quick Start
|
|
|
|
Minimal working example:
|
|
|
|
```swift
|
|
import Foundation
|
|
import Combine
|
|
|
|
struct User: Codable, Identifiable {
|
|
let id: UUID
|
|
var name: String
|
|
var email: String
|
|
}
|
|
|
|
class UserViewModel: ObservableObject {
|
|
@Published var user: User?
|
|
@Published var isLoading = false
|
|
@Published var errorMessage: String?
|
|
|
|
private let networkService: NetworkService
|
|
|
|
init(networkService: NetworkService = .shared) {
|
|
self.networkService = networkService
|
|
}
|
|
|
|
@MainActor
|
|
func fetchUser(id: UUID) async {
|
|
isLoading = true
|
|
errorMessage = nil
|
|
|
|
// ... (see reference guides for full implementation)
|
|
```
|
|
|
|
## Reference Guides
|
|
|
|
Detailed implementations in the `references/` directory:
|
|
|
|
| Guide | Contents |
|
|
|---|---|
|
|
| [MVVM Architecture Setup](references/mvvm-architecture-setup.md) | MVVM Architecture Setup |
|
|
| [Network Service with URLSession](references/network-service-with-urlsession.md) | Network Service with URLSession |
|
|
| [SwiftUI Views](references/swiftui-views.md) | SwiftUI Views |
|
|
|
|
## Best Practices
|
|
|
|
### ✅ DO
|
|
|
|
- Use SwiftUI for modern UI development
|
|
- Implement MVVM architecture
|
|
- Use async/await patterns
|
|
- Store sensitive data in Keychain
|
|
- Handle errors gracefully
|
|
- Use @StateObject for ViewModels
|
|
- Validate API responses properly
|
|
- Implement Core Data for persistence
|
|
- Test on multiple iOS versions
|
|
- Use dependency injection
|
|
- Follow Swift style guidelines
|
|
|
|
### ❌ DON'T
|
|
|
|
- Store tokens in UserDefaults
|
|
- Make network calls on main thread
|
|
- Use deprecated UIKit patterns
|
|
- Ignore memory leaks
|
|
- Skip error handling
|
|
- Use force unwrapping (!)
|
|
- Store passwords in code
|
|
- Ignore accessibility
|
|
- Deploy untested code
|
|
- Use hardcoded API URLs
|