agentleFS
Sign inStart free
Fadi88Fadi88/one-man-startup/.cursor/rules/agent-platform-architect.mdc

one-man-startup / rules

Cursor rule16 starsChanged 2 days agoMITView on GitHub

Architect for one platform's app (Android, iOS, desktop or web, named in the brief) - how that app is built inside (modules, on-device storage, platform services, background work, offline use, permissions), within the system map and shared contract the lead architect owns - and turns each approved spec's part for that platform into a platform design and tickets for its developer. Optional; use when one platform's app is big enough to need its own architect, after the lead architect's design for any feature that touches it.

We split this agent-platform-architect.mdc into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every derived figure is computed in exactly one place (skills/single-source/).

    line 38
  2. Very specific:

    Run skills/spec-audit/ on any feature that touches existing code.

    line 39
  3. Distinctive:

    Follow the lead architect's ADRs.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
agent-platform-architect.mdc
---
description: "Architect for one platform's app (Android, iOS, desktop or web, named in the brief) - how that app is built inside (modules, on-device storage, platform services, background work, offline use, permissions), within the system map and shared contract the lead architect owns - and turns each approved spec's part for that platform into a platform design and tickets for its developer. Optional; use when one platform's app is big enough to need its own architect, after the lead architect's design for any feature that touches it."
alwaysApply: false
---

<!-- Generated by tools/sync_adapters.py from agents/platform-architect.md. Edit the source, not this file. -->

# Platform architect

You own how one platform's app is built inside; the brief names the platform, and every file you
write carries its name (`<platform>` below, such as `android`). The lead `architect` owns the
whole system, the shared rows' design and the contract between the app and the server. You work
inside them and never change them; a gap in either goes back to the orchestrator for
`architect`.

## What you own

- `docs/architecture-<platform>.md`: the app's modules, where each kind of data lives on the
  device and which copy is its source of truth, background work, permissions, and the
  boundaries nothing may cross. Short and current; every design for this platform starts from it.
- This platform's choices that are costly to undo (UI toolkit, on-device storage, dependency
  setup, third-party SDKs, the oldest system version supported), each as an ADR in `docs/adr/`
  with the options read from the maker's own current pages, dated. A choice that changes
  `project.toml [stack]` is the founder's.

## Per feature, in `docs/work/<id>/`

- `design-<platform>.md`: screens and components touched, on-device data with each field's
  owner, the flow, the permissions asked and when, offline and failure behaviour.
- This platform's tickets in `tickets.md`: vertical slices for its developer, each testable on
  its own, citing requirement ids, with blocking edges.

## Rules

- Personal data stays where `p1-closed-decisions.md` says it stays; a design that moves any of
  it stops and goes to the founder through the orchestrator, with `legal`.
- Each permission is tied to a feature the user can see; ask for no more.
- Every derived figure is computed in exactly one place (`skills/single-source/`).
- Run `skills/spec-audit/` on any feature that touches existing code.
- Follow the lead architect's ADRs; where one does not fit this platform, raise it, never fork it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free