Index of every page on this site: llms.txt
All skills
suleyman avatar

/fullstack-architect

@920a44a
Run it yourself

Coordinates system-level decisions for production applications built with Next.js, FastAPI, PostgreSQL/PostGIS, Expo, and native iOS, and delegates layer details to the nextjs-frontend, python-fastapi, postgresql, expo-react-native, and swift-ios skills. Use when starting a new product or a feature that spans more than one layer, designing an architecture, choosing how web and mobile share an API, or deciding on authentication, authorization, API contracts, validation, caching, pagination, background jobs, file uploads, observability, migrations, deployment, environments, secrets, scaling, or security.

Use this Skill: https://skilld.dev/gh/suleyman/fullstack-agent-skills/fullstack-architect

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesarchitecture-template.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Architecture proposal template

Use this structure for every new product or cross-layer feature. Keep it short enough that people read it, and specific enough that someone else could implement it. Replace the guidance in italics. Delete sections that genuinely don't apply, and say why in one line.


<Product or feature> — Architecture

Status: Draft | Accepted | Superseded by <link>
Date: YYYY-MM-DD
Owners: <names or roles>

1. Context and goals

What problem this solves and for whom. The 3–5 critical user flows, as one line each ("An attendee reserves two tickets and sees them in the app seconds after paying").

2. Assumptions and non-goals

Scale (MAU, peak requests/s, writes/s, data growth per month), supported platforms and OS versions, regions, compliance constraints. Name what's explicitly out of scope for this version.

3. Stack decisions

Layer Choice Why (constraint it satisfies) Skill
Web/admin nextjs-frontend
Mobile expo-react-native
iOS (native) only if needed, with a reason swift-ios
API python-fastapi
Database postgresql
Jobs python-fastapi
Files
Auth
Hosting

Any deviation from the default stack names the constraint that forces it.

4. System diagram

Plain text or Mermaid. Show clients, BFF, API, workers, database, object storage/CDN, third parties (push, email, payments, IdP), and which component talks to which. Mark trust boundaries.

[Expo app] ──HTTPS/Bearer──▶ [FastAPI] ──▶ [PostgreSQL]
[Next.js admin] ─(BFF)─────▶     │   └──▶ [jobs table] ◀── [worker] ──▶ Expo Push / email
                                 └──▶ presign ──▶ [object storage] ──▶ [CDN]

5. Domain model

Tables with key columns, constraints, and the indexes that serve named queries. Mark sensitive columns.

Table Key columns Constraints Indexes (→ query served)

6. API surface

Endpoints grouped by resource. For each: method + path, auth requirement (public / user / role), request and response schema names, pagination style. Note idempotency keys and rate limits where relevant.

Method Path Auth Request → Response Notes

7. Authentication and authorization

Identity source. Token lifecycle per client (web cookie via BFF, mobile SecureStore/Keychain). Roles. Object-level rules per resource ("buyers see only their own orders; organizers see orders for events they own"). Admin audit logging.

8. Cross-cutting decisions

  • Errors: Problem Details codes introduced by this design.
  • Validation: rules that need database constraints.
  • Caching: what is cached, where, and how each entry is invalidated.
  • Pagination: cursor key per list.
  • Background jobs: job kinds, dedupe keys, retry policy.
  • Uploads: purposes, allowed types, size limits, processing.
  • Notifications: triggers, payload (route + id), opt-out.
  • Observability: key metrics, alerts, dashboards.

9. Data lifecycle and privacy

PII inventory, sensitive data (payments, health, location), retention periods, account deletion behavior across the database, storage, analytics, and push. Store privacy labels this implies.

10. Environments and deployment

Environments and their isolation. Pipeline steps (build → migrate → deploy → smoke test). Release order across layers. Rollback per component. Mobile: build profiles, channels, minimum supported version policy.

11. Performance and scaling

Budgets (e.g. p95 per critical endpoint). Expected load. The first bottleneck you expect, and the planned response when it arrives.

12. Risks and open questions

Risk / question Impact Mitigation / owner

13. Delivery plan

Vertical slices in order. Each one is shippable and covers DB → API → generated types → UI → tests.

  1. Slice 1: auth, /me, app config, minimum-version gate
  2. Slice 2: …

Decision log

Date Decision Alternatives considered Reason

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill provides a comprehensive architectural framework for building full-stack applications with a focus on security best practices, such as OAuth/OIDC integration, token rotation, and secure file handling. No malicious patterns or security risks were identified.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 920a44a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
metadata
{
  "author": "suleyman",
  "version": "1.0.0"
}

README badge

README badge for suleyman/fullstack-agent-skills/fullstack-architect