38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
# Codex Working Rules
|
|
|
|
This file defines repo-specific rules that CODEX AI and future helpers should follow.
|
|
|
|
## Product Rules
|
|
|
|
- Preserve the planner identity as a `10-minute planner diary`.
|
|
- Keep the default primary experience as `1 page + right-side information panel`.
|
|
- Keep `2 page spread` mode available unless the user explicitly removes it.
|
|
- Prefer calm paper-like layouts over generic dashboard styling.
|
|
|
|
## Technical Rules
|
|
|
|
- Use Vue for implementation.
|
|
- Use TailwindCSS for styling.
|
|
- Prefer reusable Vue components over large monolithic templates.
|
|
- Keep mock data easy to replace with real data sources later.
|
|
- Preserve responsive behavior for desktop and mobile.
|
|
|
|
## Workflow Rules
|
|
|
|
- Use local Git versioning continuously during development.
|
|
- Record meaningful product or technical notes in `HANDOFF.md`.
|
|
- Do not remove user-authored notes from `HANDOFF.md` unless they are outdated and replaced.
|
|
- When a major change is made, update both code and handoff context together.
|
|
|
|
## Commit Rules
|
|
|
|
- Use semantic version style commits starting from `v0.0.1` when the user asks for versioned checkpoints.
|
|
- Prefer small, understandable checkpoints over large ambiguous commits.
|
|
|
|
## Design Implementation Rules
|
|
|
|
- Use the provided Figma files as the visual source of truth.
|
|
- Match the overall proportions, line rhythm, and typography feel of the diary layout.
|
|
- Add new UI around the planner only when it clearly supports navigation, planning, or review.
|
|
|