Site Platform Architecture

Use for Site Building work when Codex should choose site architecture, rendering, hosting, CMS, integrations, and performance boundaries from product evidence.

srednoff888-art 7de1a83 2 files · 1.5 KB Updated 1 repo stars

File contents

site platform architecture

Workflow

  1. Confirm the business outcome, owner, source data, constraints, and success metric.
  2. Inspect the project and available account or analytics evidence before proposing changes.
  3. Use official documentation for current platform behavior and retain source provenance.
  4. Produce an evidence-backed plan with assumptions, dependencies, and measurable validation.
  5. Run only read-only diagnostics by default; gate external, paid, production, or publishing actions behind explicit approval.

Domain Focus

choose site architecture, rendering, hosting, CMS, integrations, and performance boundaries from product evidence.

Official Sources

https://web.dev/learn/ | https://www.w3.org/WAI/standards-guidelines/wcag/

Guardrails

  • Preserve existing design and content conventions unless the task calls for a redesign.
  • Review external code, assets, and components for provenance, license, accessibility, performance, and dependency cost.
  • Require explicit approval for production deployment, DNS, publishing, or irreversible migrations.

srednoff888-art/srednoff-os/tree/main/.codex/skills/site-platform-architecture commit 7de1a83b40

Frequently asked questions

npx skillmds add srednoff888-art/site-platform-architecture