wwwroot Codex Start — Project Onboarding & Workspace Initialization Skill
The entry point for starting work on any workspace, onboarding a codebase, or initiating a new task.
Overview
codex-start transforms general requests into structured, high-context engineering sessions. It automatically inspects the workspace, identifies programming languages, frameworks, and architecture patterns, maps them to the appropriate AI Codex Edition (skills/codex/<edition>), and creates structured, timestamped artifacts in codex-drive/.
When to Trigger
- User runs
/codex-start(e.g.,/codex-start add new theme color,/codex-start onboard project,/codex-start build auth service) - Opening a new repository or workspace where context is needed
- Initiating any new feature, refactor, or complex task
Execution Workflow
┌────────────────────────────────────────────────────────┐
│ 0. CHECK PERSISTENT BRAIN MEMORY │
│ Scan codex-drive/brains/ for recent session context.│
└──────────────────────────┬─────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 1. DISCOVER & DETECT TECH STACK │
│ Scan root markers, configuration files & manifests. │
└──────────────────────────┬─────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 2. MAP TO AI CODEX EDITION │
│ Load domain rules from skills/codex/<edition>/. │
└──────────────────────────┬─────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 3. PARSE INTENT & DEFINE SCOPE │
│ Decompose the user request into concrete goals. │
└──────────────────────────┬─────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 4. GENERATE TIMESTAMPED ARTIFACTS IN CODEX-DRIVE │
│ Create codex-drive/specs/YYYY-MM-DD-<slug>.spec.md │
│ Create codex-drive/plans/YYYY-MM-DD-<slug>.plan.md │
└──────────────────────────┬─────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 5. RECOMMEND NEXT WORKFLOW STEP │
│ Provide clickable links and suggest next command. │
└────────────────────────────────────────────────────────┘
Step 1: Technology Stack Auto-Detection Protocol
Inspect the root directory and subdirectories for project manifests to determine the active stack:
| Detected Manifest / File | Primary Technology | Target AI Codex Edition |
|---|---|---|
Cargo.toml, Cargo.lock |
Rust | skills/codex/rust/ |
go.mod, go.sum |
Go | skills/codex/go/ |
mix.exs |
Elixir / OTP | skills/codex/elixir/ |
build.zig, build.zig.zon |
Zig (Systems / Toolchains) | skills/codex/zig/ |
pyproject.toml, requirements.txt, Pipfile |
Python | skills/codex/python/ |
package.json (React, Next.js, Vite, Vue, Svelte) |
TypeScript / React / Web | skills/codex/typescript-react/ |
composer.json, artisan |
PHP (Laravel / Symfony) | skills/codex/php/ |
pom.xml, build.gradle, build.gradle.kts |
Java / Kotlin (Spring / Android) | skills/codex/java-kotlin/ |
CMakeLists.txt, Makefile, meson.build |
C / C++ | skills/codex/c-cpp/ |
Package.swift, *.xcodeproj, *.xcworkspace |
Swift (iOS, macOS, visionOS) | skills/codex/swift/ |
*.sln, *.csproj, Directory.Build.props |
C# / .NET (ASP.NET, Unity, Godot) | skills/codex/csharp-dotnet/ |
schema.sql, migrations/, drizzle.config.*, prisma/ |
SQL & Database Engineering (Postgres, MySQL) | skills/codex/sql-database/ |
foundry.toml, hardhat.config.*, contracts/*.sol |
Solidity & Web3 Systems (Ethereum / EVM) | skills/codex/solidity-web3/ |
pubspec.yaml, pubspec.lock |
Flutter & Dart (Cross-Platform / Mobile) | skills/codex/flutter-dart/ |
| CSS design tokens, Figma exports, Tailwind configs | UI/UX Design Systems | skills/codex/ui-ux-design/ |
Step 2: Artifact Creation in codex-drive/
Every file generated by codex-start MUST be a Markdown (.md) file located inside codex-drive/ with explicit date-time metadata.
1. Specification Artifact: codex-drive/specs/YYYY-MM-DD-<slug>.spec.md
2. Implementation Plan Artifact: codex-drive/plans/YYYY-MM-DD-<slug>.plan.md
Standard Header Template for all codex-drive/ files:
# [Project / Feature Title] Specification
> **Created At**: YYYY-MM-DD HH:MM:SS (Local Time)
> **Detected Stack**: [e.g., TypeScript / Next.js 15 / React 19]
> **Active Codex Edition**: [`skills/codex/<edition>/`](file:///...)
> **Status**: DRAFT | IN_PROGRESS | COMPLETED
---
## 1. Executive Summary & Objective
[Concise summary of what is being built or analyzed]
## 2. Workspace & Architecture Baseline
- **Root Directory**: `...`
- **Detected Package Manager & Tools**: `...`
- **Key Architectural Boundaries**: `...`
## 3. Scope & Requirements
- **Functional Requirements**:
- [ ] Requirement 1
- [ ] Requirement 2
- **Non-Functional Requirements** (Performance, Memory, Safety):
- [ ] Constraint 1
## 4. Recommended AI Codex Files to Load
- `skills/codex/<edition>/01-core-identity.md` (Always)
- `skills/codex/<edition>/02-languages-standards.md` (Code rules)
- `skills/codex/<edition>/04-domains-knowledge.md` (Domain patterns)
## 5. Next Steps
- Run `/codex-plans` to generate full technical task decomposition.
- Run `/codex-architecture` to model domain boundaries and state machines.
Step 3: Response Protocol
When codex-start finishes execution:
- Announce the detected technology stack and active Codex edition.
- Provide clickable file links to the newly generated artifacts in
codex-drive/specs/andcodex-drive/plans/. - Provide a concise summary of immediate actionable recommendations.
- Suggest the logical next command (e.g.,
/codex-plansor/codex-architecture).