Skip to content

Latest commit

 

History

History
37 lines (22 loc) · 2.16 KB

File metadata and controls

37 lines (22 loc) · 2.16 KB

This is NOT the Next.js you know

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.

Additional Repository Instructions

Before making code changes, read CLAUDE.md in this repository and follow its instructions.

Before making UI/UX or visual design changes, read docs/dechive_design_notes.md and follow its direction.

Current Product Direction

The Logs section has been removed from Dechive. Do not recreate /logs, content/logs, Logs navigation items, Logs sitemap entries, Logs i18n strings, or log-generation scripts unless explicitly asked.

Multi-Agent Workflow

Codex and Claude Code may work in this repository at the same time. Before editing, check git status and avoid overwriting changes from the other agent.

Keep work ownership separate:

  • Codex: application code implementation, refactors, tests, type/lint verification, Next.js route and component changes.
  • Claude Code: content creation and editing, copywriting, design critique, planning, review, translation script runs, and Supabase embedding generation.

Claude Code owns content workflows:

  • Create or edit posts/projects inside content/.
  • Run npm run translate after new Korean posts are ready.
  • Run the embedding workflow for Supabase/RAG updates (npm run embeddings or the current project-specific embedding command).
  • Handle content submodule commits when the user asks for content commits.

Codex should not run translation or embedding generation unless explicitly asked. Codex may edit app code that consumes content, but should avoid changing content/ while Claude Code is assigned content work.

Do not edit the same files concurrently. If a task needs files currently being edited by the other agent, stop and ask for coordination instead of forcing changes.

Only commit or push when the user explicitly asks. When committing content submodule changes, commit inside content/ first, then commit the updated submodule pointer in the root repository.