Platform Architect
- 5 installs
- 5 repo stars
- Updated August 5, 2026
- bjornmelin/dev-skills
Platform-architect is a Claude Code skill that detects a repo's stack and routes broad Next.js/Expo/Convex/monorepo platform work into the correct architecture lane.
About
Platform-architect is a Claude Code skill that routes broad full-stack platform work across Next.js, Expo, Convex, and monorepo tooling. It runs a deterministic repo inventory to detect the stack, selects the right lane (web, native, or full-stack), then routes narrow tasks to downstream specialist skills. A developer uses it when a task needs stack detection, platform-level planning, or cross-cutting architecture rather than a single narrow change.
- Routes broad platform work into web, native, backend, and tooling lanes
- Runs a deterministic repo-inventory to detect the stack before planning
- Explicitly delegates to downstream specialist skills for UI, docs, and dependency work
Platform Architect by the numbers
- 5 all-time installs (skills.sh)
- Ranked #13,065 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
platform-architect capabilities & compatibility
Free; uses repo-native inventory tooling.
- Capabilities
- stack detection · architecture planning · skill routing
- Use cases
- frontend · api development · devops
- Pricing
- Free
What platform-architect says it does
Architect and implement modern full-stack web/native platform work across Next.js, Expo, Convex, and monorepo tooling.
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.
If the task narrows into a specialized domain, explicitly invoke the right downstream skill:
npx skills add https://github.com/bjornmelin/dev-skills --skill platform-architectAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 5 |
| Last updated | August 5, 2026 |
| Repository | bjornmelin/dev-skills ↗ |
What it does
Detect a repo's stack and route platform-wide architecture work across web, native, and backend lanes.
Who is it for?
Stack detection, platform-level planning, and cross-cutting architecture across web, native, and backend boundaries.
Skip if: Narrow dependency upgrades, PR review remediation, docs-only alignment, or single narrow UI audits.
When should I use this skill?
A task needs stack detection, platform-level planning, or implementation across web/native/backend boundaries.
What you get
A lane selection summary, a stack-tied implementation plan, repo-native verification commands, and explicit downstream skill routing.
- lane selection summary
- implementation or review plan tied to the detected stack
- repo-native verification commands
By the numbers
- 4 target platforms (Next.js, Expo, Convex, monorepo tooling)
Files
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
1. Read the repo AGENTS.md first for local constraints and canonical commands. 2. Run /home/bjorn/.codex/skill-support/bin/repo-inventory detect --cwd <repo> --out <json>. 3. Run /home/bjorn/.codex/skill-support/bin/repo-inventory matrix --input <json> --format md. 4. 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
5. Read references/tooling-and-verification.md before running checks or changing commands. 6. 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
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
interface:
display_name: "Platform Architect"
short_description: "Architect modern Next, Expo, Convex, and monorepo stacks"
default_prompt: "Use $platform-architect to detect the active platform lanes, choose the correct architecture path, and route into the right repo-native skill or verification workflow."
policy:
allow_implicit_invocation: true
dependencies:
tools:
- type: "mcp"
value: "context7"
description: "Library and framework documentation"
- type: "mcp"
value: "exa"
description: "Latest platform research when official docs are not enough"
Expo Native Lane
Use this lane when Expo, EAS, or React Native concerns are primary.
Priorities
1. Preserve native UX and release safety. 2. Prefer Expo-managed workflows over custom native divergence unless the repo clearly requires otherwise. 3. Validate with Expo/EAS/native checks already defined by the repo.
Escalate To
$ui-auditfor UX and accessibility review$convex-auditwhen backend contract work is the real bottleneck
Full-Stack Platform Lane
Use this lane when the work spans web, native, backend contracts, and repo tooling together.
Priorities
1. Detect the primary execution plane first: web, native, backend, infra. 2. Avoid duplicating architecture logic across multiple downstream skills. 3. Route specialized work out once the platform boundary is clear.
Common Cases
- shared types and validation across app + backend
- monorepo workspace structure changes
- platform-wide refactors that affect verification commands or deployment flow
Next Web Lane
Use this lane when the repo inventory shows Next.js or React web concerns are primary.
Priorities
1. Keep one canonical rendering/data path. 2. Prefer server-first boundaries and explicit client islands. 3. Verify routing, caching, metadata, accessibility, and build behavior with repo-native commands.
Read Alongside
- Repo
AGENTS.md - framework docs via Context7
references/tooling-and-verification.md
Tooling and Verification
Rules
1. Use the repo-native package manager and task runner detected from the repo, not a guessed default. 2. Read AGENTS.md before choosing format, lint, typecheck, test, or build commands. 3. If command usage is unclear, run --help first. 4. Do not expand into cross-domain workflows until the platform lane is known.
Shared Preflight
- run the repo inventory first
- confirm the active lane
- only then load heavier references or specialized skills
#!/usr/bin/env python3
from __future__ import annotations
import argparse
import subprocess
from pathlib import Path
def main() -> int:
parser = argparse.ArgumentParser(description="Wrapper around the shared repo-inventory CLI.")
parser.add_argument("--cwd", default=".")
parser.add_argument("--out", required=True)
args = parser.parse_args()
cmd = [
"/home/bjorn/.codex/skill-support/bin/repo-inventory",
"detect",
"--cwd",
str(Path(args.cwd).resolve()),
"--out",
args.out,
]
return subprocess.run(cmd, check=False).returncode
if __name__ == "__main__":
raise SystemExit(main())
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What stacks does platform-architect target?
Next.js/React web, Expo/React Native, Convex, and monorepo tooling like Bun, pnpm, and Turbo.
When should I not use it?
Skip it for dependency-only upgrades, PR remediation, docs drift passes, or narrow UI audits with no platform decisions.