Files
jhonny-editor/CLAUDE.md
T
João Henrique b541f502ba feat: initial commit - Jhonny Editor
- Adicionado estrutura completa do projeto
- Configurado MCP server para Premiere Pro
- Adicionado documentação e skills
- Configurado Gitignore para o projeto
2026-09-08 09:59:31 -04:00

2.1 KiB

CLAUDE.md

Project Context

This is a software engineering project that uses mattpocock/skills for code quality and organization.

Code Search: use the RAG first

This project has a code RAG at rag/ (see rag/README.md), already indexed and kept in sync automatically (a PostToolUse hook reindexes any edited file). Before grepping or reading whole files to find something in code/, run:

rag/search_jhonny.sh "your query in natural language"

This returns exact file:line-range hits instead of forcing a full read of large files — much cheaper in tokens. Use --snippet or --full when you need to see the matched code, --map for a file inventory, and --path/ --ext to scope the search. Fall back to Grep/Glob only when the RAG has no tunnel available (rag/ensure_tunnel.sh failed) or for exact-string searches it isn't built for (e.g. searching non-code config not indexed).

Available Skills

The following skills are available in this project (located in .agents/skills/):

Code Quality & Architecture

  • /improve-codebase-architecture - Scan codebase for deepening opportunities
  • /codebase-design - Design deep modules with simple interfaces
  • /domain-modeling - Build shared vocabulary and domain model

Testing & Code Review

  • /tdd - Test-driven development with red-green-refactor loop
  • /code-review - Two-axis review: Standards + Spec
  • /diagnosing-bugs - Disciplined bug diagnosis loop
  • /resolving-merge-conflicts - Resolve git conflicts hunk by hunk

Global Skills (available via ~/.agents/skills/)

  • 29 additional skills for engineering and productivity

Usage

When working on this project, use these skills to:

  1. Improve architecture: Run /improve-codebase-architecture to scan for improvements
  2. Design modules: Use /codebase-design when creating new modules
  3. Model domain: Use /domain-modeling to build shared vocabulary

Code Standards

  • Follow existing code conventions
  • Use shared domain vocabulary from CONTEXT.md
  • Write tests before code (TDD)
  • Review code changes with /code-review