Add CLAUDE.md documentation and agent skills

[ChrisPriebe]

This commit initializes a basic CLAUDE.md (points to AGENTS.md for cross agent compatibility). I need this because gitignore is blocking these files so the agents are running dumb. While I could add it locally that doesn't help for remote workspaces like https://claude.ai/code/ where I have to re-explain this is a vs code and why it exists each time.

Before you accept it

• Your .gitignore was ignoring these files meaning you may have local versions better than this. It would be better to have everyone share their files and already tested optimizations and incorporate them.

• Add root CLAUDE.md with reference to AGENTS.md

• Add AGENTS.md with comprehensive project guidelines including:

  • Build/test/lint commands
  • Architecture overview and key files
  • VS Code extension patterns
  • Coding standards and common mistakes to avoid
  • Review standards from PR history

• Add subdirectory CLAUDE.md files for major directories:

  • src/providers/ - Provider patterns
  • src/projectManager/ - Migrations and sync
  • src/tsServer/ - Language server
  • src/utils/ - Utility modules
  • webviews/codex-webviews/ - React UI patterns

• Add Claude skills in .claude/skills/:

  • add-ui-component - Adding UI elements
  • improve-llm-copilot - LLM/AI modifications
  • add-vscode-command - Command registration

• Remove CLAUDE.md and AGENTS.md from .gitignore

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[ChrisPriebe]

INITIAL PROMPT

Init claude

Create a CLAUDE.md file in the root
Standard CLAUDE.md (check web for best practices of what to put into it)
This is a vs code fork that allows, check latest web docs and include docs on how to work with VS code extensions.
Where are the most important files
How do we test it, lint it
Discern their coding practices.
Store this file as AGENTS.md and in CLAUDE.md just provide an @AGENTS.md so it is auto-included
Review their source code and find common mistakes, add a section on avoiding those
Review their PRs https://github.com/genesis-ai-dev/codex-editor and look for code review comments; what do they care about add to coding standards.
Subdirectory CLAUDE.md files don't work well yet (only loads if your cwd is there) so tell it that if it edits a file in a directory needs to check anestory tree for a CLAUDE.md it has not loaded yet and read it (this will also help other agents like cursor since it will use the AGENTS.md file and find the CLAUDE.md files)
insist on updating the documentation and the CLAUDE.md files before finishing a session
Create CLAUDE.md file in each major directory
Implement from web research of what to put in the subfolders
Focus on how to contribute to this directory
Focus on key how-tos
Create SKILLS
do web research from the official claude sites on how to develop skills.
Keep the metadata tight at the top (don't fall prey to the typical bloat)
Focus on key skills like how to add a UI element telling where the UI folders are, how the UI works with the backend files
Some potential skills
How to add a ui button/component
How to improve the copilot llm call
How to build an extension
Focus on common gotchas like what needs to be registered in package.json
Key requirements

Be very concise, use pregnant terms (terms that pack a lot of meaning as a compression algorithm, instead of explaing a code best practice like DRY just say use DRY)

[ChrisPriebe]

FOLLOW-UP PROMPT

Let's add self learning loops to it

if a skill is used at the end of the session it must review the process; what didn't work; what mistakes where made; fix the SKILL so that future runs will not run into the same problems
Likewise for all sessions if it having a hard time finding files, has to lookup how to do something, makes an error then evaluate which CLAUDE.md file will best fix it and make a fix (however don't spam the file, it must be kept short, fixes need to be generic, ignore one-offs, focus only on what will help significant future cases)
If the user tells you did something wrong or states a preference be sure to learn from that and fix your base instructions so you don't do it again.
Other things

Never put plan or summary docs in the root directory. If you make those files (not required) they must go in the /plan/{slug} directory