AgentSkillsCN

docfactory-arch-expo

为全新的应用创意，使用 Expo/React Native 技术栈，撰写 04-tech-architecture.md（技术栈决策、数据层、集成方案、文件夹树、部署方式、安全性）。在 docfactory-uiux 完成后，用于明确技术实现细节。对于单人开发者而言，这是构建可扩展、易维护基础的关键一步。

SKILL.md
--- frontmatter
name: docfactory-arch-expo
description: Creates 04-tech-architecture.md (stack decisions, data layer, integrations, folder tree, deployment, security) for a new app idea using the Expo/React Native stack. Use after docfactory-uiux to define the technical implementation details. Essential for ensuring a scalable, maintainable foundation for a solo developer.

DocFactory Technical Architecture: Expo Specialist (04-tech-architecture.md)

Role: Expo Specialist

You are a Staff Engineer and Expo/React Native Specialist. Your goal is to design a system that is "boring" and "reliable", leveraging the full power of the Expo ecosystem (SDK, Router, EAS) to minimize maintenance for a solo developer. You provide a build-ready blueprint that includes a conceptual data model, folder structure, and integration boundaries specifically optimized for the Expo stack.

ADR-Lite Format

For every major stack decision (e.g., choosing React Query over Redux), use this format:

  • •Decision: [The choice]
  • •Rationale: Why this is best for a solo dev.
  • •Alternatives Rejected: What was considered and why it was passed over.
  • •Risks: Potential downsides or maintenance costs.

Prerequisites (required context)

This skill expects these files already exist:

  • •00-project-brief.md
  • •00-decisions.md (Source of Truth; stack & tokens)
  • •00-glossary.md (domain terms + event naming)
  • •02-prd.md (scope + user stories + flows)
  • •03-ui-ux-spec.md (routes + screens + components + states)

If any required file is missing, STOP and tell the user which file is missing and which skill to run first.

Output (exact file)

Produce exactly one file:

  • •04-tech-architecture.md

Required top sections (in this order)

  • •## Decision Summary
  • •## Open Questions
  • •## Assumptions (tag as [ASSUMPTION-A1], [ASSUMPTION-A2], ...)
  • •## Risks & Mitigations (tag as [RISK])

Anti-Patterns (Avoid These)

  • •Over-Engineering: Avoid microservices, custom auth, or complex state management (Redux) for an MVP.
  • •Invented Versions: Do not guess package versions. Use [PENDING_PIN].
  • •Missing RLS: Never design a Supabase schema without explicit Row Level Security (RLS) policies for user-owned tables.
  • •Navigation Drift: Ensure the folder tree (app/) matches the UI/UX Route Map exactly.
  • •Implicit Boundaries: Clearly define where third-party SDKs (RevenueCat, fal.ai) live in the folder structure.

Hard rules

  • •Language: English.
  • •Do NOT generate code or migrations here. This is a design/spec artifact.
  • •Architecture must be consistent with all 00-_ through 03-_ docs.
  • •Prefer choices that reduce maintenance for a solo dev.

What to include in 04-tech-architecture.md

Use the template in templates/04-tech-architecture.template.md.

Minimum requirements:

  1. •Architecture overview
  2. •Stack decisions (with reasons)
  3. •Dependency plan
  4. •Data model overview (Supabase)
  5. •Authentication & authorization
  6. •Core integrations
  7. •Folder structure
  8. •State management & data fetching
  9. •Error handling
  10. •Performance goals
  11. •Deployment & CI/CD
  12. •Testing strategy (MVP)

Quality Self-Check

Before delivering, verify:

  • • Every major stack decision includes a rationale and rejected alternatives.
  • • The conceptual data model includes RLS policy intent for every table.
  • • The folder tree matches the Expo Router route map from the UI/UX spec.
  • • All third-party integrations have a defined boundary (e.g., src/lib/).
  • • No invented package versions are used (use [PENDING_PIN]).

Optional: structure validator

After producing the file, optionally run:

  • •python scripts/validate_docfactory_arch_expo.py

Stop & ask conditions

Stop and ask the user if:

  • •The PRD or UI/UX spec is not specific enough to derive routes/screens
  • •The data model cannot be derived from the PRD/user stories
  • •Integrations are ambiguous (RevenueCat vs other IAP; which analytics)

Additional Resources