agentleFS
blackbenjaminblackbenjamin/etps/CLAUDE.md

etps

CLAUDE.md1 starsChanged 11 months agoMITView on GitHub

ETPS (Enterprise-Grade Talent Positioning System) is an AI-powered resume and cover letter tailoring system that optimizes job application materials for specific positions. Tech Stack: - Backend: Python 3.13, FastAPI, SQLAlchemy, Pydantic - Frontend: Next.js + shadcn/ui (complete) - Database: SQLite (dev), PostgreSQL (prod) - Vector Store: Qdrant (semantic search) - LLMs: Claude (primary), GPT-4o (fallback), text-embedding-3-small (embeddings) Completed: Phase 1A (Sprints 1-10) + Phase 1B (Sprints 11-12) Next: Phase 1C - Sprint 13 (Portfolio Security) -> Sprint 14 (Cloud Deployment)…

The file

Show its rules and text

We split this CLAUDE.md into the rules it gives an agent

13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Security review: Use the reviewer agent to check for vulnerabilities

    line 32
  2. Distinctive:

    Update documentation: if sprint completed

    line 38
  3. Very specific:

    Update data model docs: if backend/db/models.py changed

    line 40
  4. Very specific:

    Update docs/DATA_MODEL.md with new fields/entities

    line 41
  5. Distinctive:

    Update JSON schema examples if applicable

    line 42
  6. Very specific:

    Read the sprint tasks from docs/IMPLEMENTATION_PLAN.md

    line 55
  7. Distinctive:

    Create todo list with all tasks

    line 56
  8. Distinctive:

    Write/update tests (target: all tests pass)

    line 58
  9. Distinctive:

    Commit with proper message

    line 60
  10. Very specific:

    All services in backend/services/ follow this pattern:

    line 65
  11. Very specific:

    Use pytest with pytest-asyncio

    line 73
  12. Distinctive:

    Injection: Use parameterized queries, validate all inputs

    line 94
  13. Distinctive:

    Data Exposure: No secrets in code, use env vars

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

ETPS - Claude Code Project Configuration

Project Overview

ETPS (Enterprise-Grade Talent Positioning System) is an AI-powered resume and cover letter tailoring system that optimizes job application materials for specific positions.

Tech Stack:

  • Backend: Python 3.13, FastAPI, SQLAlchemy, Pydantic
  • Frontend: Next.js + shadcn/ui (complete)
  • Database: SQLite (dev), PostgreSQL (prod)
  • Vector Store: Qdrant (semantic search)
  • LLMs: Claude (primary), GPT-4o (fallback), text-embedding-3-small (embeddings)

Key Documentation

  • ETPS_PRD.md - Product Requirements Document (source of truth)
  • docs/IMPLEMENTATION_PLAN.md - Sprint roadmap and progress
  • docs/ARCHITECTURE.md - System architecture and service map
  • docs/DATA_MODEL.md - Database schema reference (v1.4.2)
  • docs/cover_letter_style_guide.md - Writing style rules
  • backend/README.md - Backend setup and API reference

Development Workflow

Before Every Commit

  1. Run all tests:
    cd backend && python -m pytest -v --tb=short
  2. Security review: Use the reviewer agent to check for vulnerabilities
    • SQL injection, XSS, command injection
    • Input validation and bounds checking
    • Exception handling (no silent failures)
    • ReDoS in regex patterns
  3. Update documentation if sprint completed
  4. Update data model docs if backend/db/models.py changed
    • Update docs/DATA_MODEL.md with new fields/entities
    • Update JSON schema examples if applicable
    • Increment version number

Commit Convention

TypeFormatExample
Sprint completefeat(sprint-N): <summary>feat(sprint-8c): Implement pagination
Bug fixfix: <summary>fix: Resolve null pointer in critic
Docsdocs: <summary>docs: Update API reference

Sprint Implementation Pattern

  1. Read the sprint tasks from docs/IMPLEMENTATION_PLAN.md
  2. Create todo list with all tasks
  3. Implement each task, marking complete as you go
  4. Write/update tests (target: all tests pass)
  5. Run security review
  6. Commit with proper message

Code Patterns

Service Structure

All services in backend/services/ follow this pattern:

  • Config loaded from backend/config/config.yaml
  • Async functions for LLM calls
  • Pydantic schemas in backend/schemas/
  • Database models in backend/db/models.py

Testing Pattern

  • Tests in backend/tests/test_*.py
  • Use pytest with pytest-asyncio
  • Mock LLM with services/llm/mock_llm.py
  • Mock vector store with MockVectorStore

Key Services

ServicePurpose
resume_tailor.pyMain orchestrator for resume generation
cover_letter.pyCover letter generation with critic loop
critic.pyQuality evaluation (ATS, style, truthfulness)
skill_gap.pySemantic skill matching and gap analysis
pagination.pyLine budget and page layout simulation
bullet_rewriter.pyLLM-powered bullet optimization
summary_rewrite.pyProfessional summary generation
company_enrichment.pyCompany profile enrichment (industry, culture, AI maturity)
capability_extractor.pyLLM-based capability cluster extraction

Security Requirements

OWASP Top 10 Considerations

  • Injection: Use parameterized queries, validate all inputs
  • Authentication: JWT tokens (Sprint 18)
  • Data Exposure: No secrets in code, use env vars
  • Input Validation: Bounds check all parameters

Code Review Checklist

  • No hardcoded secrets or API keys
  • Input validation on all user-facing parameters
  • Specific exception handling (not bare except:)
  • Regex patterns pre-compiled and length-limited
  • Database queries use ORM (no raw SQL)

Current Status

Completed: Phase 1A (Sprints 1-10) + Phase 1B (Sprints 11-12) Next: Phase 1C - Sprint 13 (Portfolio Security) -> Sprint 14 (Cloud Deployment) Test Count: 711 passing

Phase Roadmap

Phase 1A: Core Quality (Sprints 1-10)           COMPLETE
Phase 1B: Company Enrichment (Sprints 11-12)    COMPLETE
Phase 1C: Deployment (Sprints 13-14)            TARGET
Phase 2:  Networking (Sprints 15-17)            NOT STARTED
Phase 3:  Application Tracking (Sprints 18+)    DEFERRED

Useful Commands

# Run tests
cd backend && python -m pytest -v

# Run specific test file
python -m pytest tests/test_pagination_allocation.py -v

# Check for issues
python -m pytest --tb=long  # Full tracebacks

# Start backend dev server
uvicorn main:app --reload --port 8000

# Start frontend dev server
cd ../frontend && npm run dev

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.