skills/codex-architect/SKILL.md
Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.
npx skillsauth add sd0xdev/sd0x-dev-flow codex-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/codex-architect "<question>"
/codex-architect "Evaluate this design" --context src/xxx.ts --mode review
/codex-architect "Redis vs MongoDB?" --mode compare
| Mode | Purpose | When | | ------- | ----------------------- | -------------------------- | | design | Provide design advice | Starting from scratch (default) | | review | Evaluate existing design | Validate solution, find issues | | compare | Compare multiple options | Tech selection |
User -> Claude -> Codex -> Integrate
| | |
Initial thinking Third perspective Combined advice
When using mcp__codex__codex, must include the following:
mcp__codex__codex({
prompt: `You are a senior architect. Please provide architecture advice for the following question.
## Question
${QUESTION}
## Mode
${MODE} (design/review/compare)
## IMPORTANT: You must independently research the project
Before providing architecture advice, you **must** perform the following research:
### Research Steps
1. Understand project structure: \`ls src/\`, \`ls src/service/\`, \`ls src/provider/\`
2. Search related modules: \`grep -r "keyword" src/ --include="*.ts" -l | head -10\`
3. Read existing implementations: \`cat <relevant files> | head -150\`
4. Understand existing architecture patterns and conventions
### Verification Focus
- What does the existing architecture look like?
- What are the existing code style and patterns?
- What similar features can be referenced?
## Output Requirements
1. First describe which files you researched
2. Provide advice based on current project state
3. Consider consistency with existing architecture
...(other review dimensions)`,
sandbox: 'read-only',
'approval-policy': 'never',
});
/codex-architect -> /tech-spec -> /review-spec -> /codex-implement -> /codex-review-fast
Design Plan Review Implement Code Review
references/project-knowledge.md - Project architecture knowledge + report templateInput: /codex-architect "How to design a high-concurrency cache?"
Action: Codex analysis -> Claude supplement -> Integrated output
Input: /codex-architect "Any issues with this API design?" --mode review
Action: Codex evaluation -> Claude verification -> Output issues + recommendations
documentation
Rewrite the previous reply in Traditional Chinese
development
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
development
Verification loop — lint -> typecheck -> unit -> integration -> e2e
development
Research current code state then update corresponding docs, ensuring docs stay in sync with code.