objc swift ios

Other Community

Skill notes

When to use

You add or rename .h / .m files under ContentstackPersistence/, ContentstackPersistenceCoredata/, or ContentstackPersistenceRealm/ You expose symbols to Swift consumers (@import / import patterns in README) You align with existing naming and module structure

Language

Primary implementation language: Objective-C (.m / .h). Swift: Documented in README.md via module imports; keep public APIs Objective-C–friendly (NS_SWIFT_NAME only if you introduce names that need Swift polish—follow existing project style).

Layout (by folder)

Path · Role ContentstackPersistence/ · Core framework: SyncManager, PersistenceModel, protocols, umbrella ContentstackPersistence.h ContentstackPersistenceCoredata/ · Core Data store implementation ContentstackPersistenceRealm/ · Realm store implementation ContentstackPersistenceTests/ · XCTest sources

Headers and modules

Public API is driven by s.public_header_files in each podspec—new public headers must be listed there. Keep umbrella / main header includes predictable; consumers may use #import <Module/Module.h> or @import Module.

Naming and style

Match existing patterns: Objective-C naming, file names aligned with class names (e.g. SyncManager.h / SyncManager.m). Avoid drive-by reformatting unrelated code in the same change as feature work.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Objective-C / Swift & repo layout – Contentstack iOS Persistence

## When to use

- You add or rename `.h` / `.m` files under `ContentstackPersistence/`, `ContentstackPersistenceCoredata/`, or `ContentstackPersistenceRealm/`
- You expose symbols to Swift consumers (`@import` / `import` patterns in README)
- You align with existing naming and module structure

## Instructions

### Language

- **Primary implementation language:** Objective-C (`.m` / `.h`).
- **Swift:** Documented in [README.md](../../README.md) via module imports; keep public APIs Objective-C–friendly (`NS_SWIFT_NAME` only if you introduce names that need Swift polish—follow existing project style).

### Layout (by folder)

| Path | Role |
| --- | --- |
| `ContentstackPersistence/` | Core framework: `SyncManager`, `PersistenceModel`, protocols, umbrella `ContentstackPersistence.h` |
| `ContentstackPersistenceCoredata/` | Core Data store implementation |
| `ContentstackPersistenceRealm/` | Realm store implementation |
| `ContentstackPersistenceTests/` | XCTest sources |

### Headers and modules

- Public API is driven by **`s.public_header_files`** in each podspec—new public headers must be listed there.
- Keep umbrella / main header includes predictable; consumers may use `#import <Module/Module.h>` or `@import Module`.

### Naming and style

- Match existing patterns: Objective-C naming, file names aligned with class names (e.g. `SyncManager.h` / `SyncManager.m`).
- Avoid drive-by reformatting unrelated code in the same change as feature work.

## References

- [contentstack-ios-persistence-sdk](../contentstack-ios-persistence-sdk/SKILL.md)
- [testing](../testing/SKILL.md)

---
> Source: [contentstack/contentstack-ios-persistence](https://github.com/contentstack/contentstack-ios-persistence) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.