Codex Project Organizer

🧭

Project Brief Builder

Complete the fields. The Markdown updates automatically.

🎯

Project Goal

What are you building? What should success look like?

👥

Target User

Who is this for? What do they need to do without coding knowledge?

🧱

Project Type

Choose the closest format.

🎨

Design Requirements

Describe visual style, branding, accessibility, and layout needs.

☑️

Features to Include

List must-have features first. Keep nice-to-haves separate.

🛡️

Data & Privacy

Codex should know what data is used and what must be protected.

No user accounts required Keep data in the browser when possible Student data may be involved Avoid paid services or new dependencies

⚙️

Workflow Rules for Codex

These rules reduce confusion and keep the project moving safely.

⬇ Download .md

Live Markdown Preview

● Updates automatically

💬

Use plain languageExplain the tool like you are talking to a friend.

⭐

One feature at a timeFocus on one change that delivers value.

🛡️

Small safe changesPrefer edits that are easy to test and undo.

✅

Always testKnow what to click and what result should appear.

🔒

Protect privacyDo not expose sensitive or student data.

⛰️

Keep it simpleAvoid complexity unless it clearly helps.

🧩

Quick Templates

Select a template to fill the organizer with a starter brief.

Single HTML Tool

Best for simple classroom utilities that run offline or on GitHub Pages.

WordPress Embed

Best for WordPress.com Custom HTML blocks with no scripting dependencies.

Data Dashboard

Best for CSV, Markdown, or Google Sheet-powered visual summaries.

Messy Project Cleanup

Best when a vibe-coded project has become confusing or fragile.

📚

Prompt Library

Copy these into Codex when you need a narrower task.

# Inspect First
Inspect this project and summarize what it does. Do not edit files yet. Identify the important files, how to run it, and the safest first improvement.

# New Feature
Add this feature using the existing project style. Make the smallest working version first. Do not add dependencies unless necessary. After editing, give me click-by-click test steps.

# Bug Fix
Find the root cause of this bug. Fix it with the smallest safe change. Do not rewrite unrelated files. Explain how to verify the fix manually.

# Cleanup
This project has become confusing. Inspect the files, identify duplicate or unused code, and suggest a cleanup plan in small steps. Do not change behavior unless I approve it.

# Pre-Publish Check
Check that this project opens correctly, has no missing files, works on mobile and desktop, protects privacy, and has clear instructions. Do not add new features.

❔

How This Helps

The goal is to give Codex better context before coding starts.

This website turns a vague project idea into a structured Markdown brief. Non-coders can use it to explain goals, users, features, privacy limits, and workflow rules before asking Codex to inspect or change files.

The recommended workflow is: Define → Inspect → Plan → Build Small → Test → Report. This prevents large accidental rewrites and makes it easier to understand what changed.

Best first instruction for Codex: “Start by inspecting the project. Do not edit files yet.”