platform-architect
Platform Architect
Use this skill to route broad platform work into the correct web, native, backend, and tooling lanes without redoing the same repo preflight every turn.
Workflow
- Read the repo
AGENTS.mdfirst for local constraints and canonical commands. - Run
/home/bjorn/.codex/skill-support/bin/repo-inventory detect --cwd <repo> --out <json>. - Run
/home/bjorn/.codex/skill-support/bin/repo-inventory matrix --input <json> --format md. - Choose the active lane:
- Next.js / React web -> read
references/next-web.md - Expo / React Native -> read
references/expo-native.md - Mixed full-stack or monorepo coordination -> read
references/fullstack-platform.md
- Next.js / React web -> read
- Read
references/tooling-and-verification.mdbefore running checks or changing commands. - If the task narrows into a specialized domain, explicitly invoke the right downstream skill:
- Convex architecture or audits ->
$convex-auditor$convex-feature-spec - General web UI review -> repo-local
$web-design-guidelineswhen installed - React/Next performance or render-quality review -> repo-local
$vercel-react-best-practiceswhen installed - Dash callback or Dash UI review ->
$dash-audit - Design/build work ->
$frontend-design - Docs sync ->
$docs-align - Dependency work ->
$gh-deps-intel
- Convex architecture or audits ->
Use When
- The user asks for platform architecture, stack-wide planning, or implementation across web/native/backend boundaries.
- The repo shape is unclear and you need a deterministic platform inventory first.
- The work touches Next.js, Expo, Convex, Bun/pnpm, Turbo, or mixed platform concerns together.
Do Not Use When
- The task is only a dependency-upgrade workflow.
- The task is only PR/comment remediation.
- The task is only a docs drift pass.
- The task is only a narrow UI audit with no platform decisions.
- The task is a Dash-only audit with no cross-platform architecture work.
Outputs
- A short lane selection summary.
- A concrete implementation or review plan tied to the detected stack.
- Repo-native verification commands, not invented commands.
- Explicit downstream skill routing when the task narrows into UI, review, docs, or dependency work.
Resources
- Inventory wrapper:
scripts/platform_inventory.py - Web guidance:
references/next-web.md - Native guidance:
references/expo-native.md - Cross-stack guidance:
references/fullstack-platform.md - Verification policy:
references/tooling-and-verification.md
More from bjornmelin/dev-skills
streamdown
|
13zod-v4
Expert guidance for Zod v4 schema validation in TypeScript. Use when designing schemas, migrating from Zod 3, handling validation errors, generating JSON Schema/OpenAPI, using codecs/transforms, or integrating with React Hook Form, tRPC, Hono, or Next.js. Covers all Zod v4 APIs including top-level string formats, strictObject/looseObject, metadata, registries, branded types, and recursive schemas.
9vitest-dev
World-class Vitest QA/test engineer for TypeScript + Next.js (local + CI performance focused)
8docker-architect
SOTA Docker/Compose architecture, implementation, refactor, and security hardening. Use when working on containerization tasks such as creating or rewriting Dockerfiles, docker-compose files, buildx/bake configs, .dockerignore, and CI pipelines for build/test/scan/publish; auditing existing container setups for security, correctness, size/perf, and best practices (least privilege, non-root, minimal images, pinned base images, BuildKit secrets, healthchecks); debugging Docker build/run issues; or designing dev vs prod compose workflows across services (DB/cache/queues) with correct networking, volumes, secrets, and resource limits.
6notebook-ml-architect
>
5ai-sdk-ui
|
5