45 lines
3.1 KiB
Markdown
45 lines
3.1 KiB
Markdown
# Agents
|
|
|
|
## Damus Overview
|
|
|
|
Damus is an iOS client built around a local relay model ([damus-io/damus#3204](https://github.com/damus-io/damus/pull/3204)) to keep interactions snappy and resilient. The app operates on `nostrdb` ([source](https://github.com/damus-io/damus/tree/master/nostrdb)), and agents working on Damus should maximize usage of `nostrdb` facilities whenever possible.
|
|
|
|
## Codebase Layout
|
|
|
|
- `damus/` contains the SwiftUI app. Key subdirectories: `Core` (protocol, storage, networking, nostr primitives), `Features` (feature-specific flows like Timeline, Wallet, Purple), `Shared` (reusable UI components and utilities), `Models`, and localized resources (`*.lproj`, `en-US.xcloc`).
|
|
- `nostrdb/` hosts the embedded database. Swift bindings (`Ndb.swift`, iterators) wrap a C/LMDB core; prefer these abstractions when working with persistence or queries.
|
|
- `damus-c/` bridges C helpers (e.g., WASM runner) into Swift; check `damus-Bridging-Header.h` before adding new bridges.
|
|
- `nostrscript/` contains AssemblyScript sources compiled to WASM via the top-level `Makefile`.
|
|
- Tests live in `damusTests/` (unit/snapshot coverage) and `damusUITests/` (UI smoke tests). Keep them running before submitting changes.
|
|
|
|
## Development Workflow
|
|
|
|
- Use `just build` / `just test` for simulator builds and the primary test suite (requires `xcbeautify`). Update or add `just` recipes if new repeatable workflows emerge.
|
|
- Xcode project is `damus.xcodeproj`; the main scheme is `damus`. Ensure new targets or resources integrate cleanly with this scheme.
|
|
- Rebuild WASM helpers with `make` when touching `nostrscript/` sources.
|
|
- Follow `docs/DEV_TIPS.md` for debugging (enabling Info logging, staging push notification settings) and keep tips updated when discovering new workflows.
|
|
|
|
## Testing Expectations
|
|
|
|
- Provide a concrete test report in each PR (see `.github/pull_request_template.md`). Document devices, OS versions, and scenarios exercised.
|
|
- Add or update unit tests in `damusTests/` alongside feature changes, especially when touching parsing, storage, or replay logic.
|
|
- UI regressions should include `damusUITests/` coverage or rationale when automation is impractical.
|
|
- Snapshot fixtures under `damusTests/__Snapshots__` must be regenerated deliberately; explain updates in commit messages.
|
|
|
|
## Contribution Standards
|
|
|
|
- Sign all commits (`git commit -s`) and include appropriate `Changelog-*`, `Closes:`, or `Fixes:` tags as described in `docs/CONTRIBUTING.md`.
|
|
- Keep patches scoped: one logical change per commit, ensuring the app builds and runs after each step.
|
|
- Favor Swift-first solutions that lean on `nostrdb` types (`Ndb`, `NdbNote`, iterators) before introducing new storage mechanisms.
|
|
- Update documentation when workflows change, especially this file, `README.md`, or developer notes.
|
|
|
|
## Agent Requirements
|
|
|
|
1. Code should tend toward simplicity.
|
|
2. Commits should be logically distinct.
|
|
3. Commits should be standalone.
|
|
4. Code should be human readable.
|
|
5. Code should be human reviewable.
|
|
6. Use code comments to add context.
|
|
7. Review and follow `pull_request_template.md` when creating PRs for iOS Damus.
|