MRMENDEZ
SKILL.md

Atlas Contributor

Find the right package boundary and validation path for non-trivial Atlas changes.

curl -fsSL https://mrmendez.dev/install-skill.sh | sh -s -- atlas-contributor

Atlas Contributor

Use this skill for any non-trivial Atlas codebase change. Start from source truth, keep package boundaries intact, and validate the behavior at the narrowest useful layer before running repo-wide gates.

Workflow

  1. Locate ownership.

    • Apps own user-facing surfaces: apps/cli for commands and terminal output, apps/server for HTTP/OpenAPI/MCP mounting.
    • Packages own domain behavior: core contracts, config loading, source-* acquisition, topology classification, compiler Markdown artifacts, tokenizer chunks, store persistence/search, retrieval ranking/context, indexer sync/build orchestration, mcp protocol surfaces, testkit fixtures/eval.
    • Do not put package-layer logic into apps.

  2. Read the nearest docs and tests.

    • Root architecture: docs/architecture.md.
    • Package/app docs: apps/*/docs/index.md and packages/*/docs/index.md.
    • Module docs: */src/<module>/docs/index.md.
    • Tests usually live at package/app roots or beside the relevant module.

  3. Preserve contract direction.

    • @atlas/core should not depend on higher packages.
    • Source adapters implement RepoSourceAdapter; they do not classify or persist docs.
    • Indexer coordinates source, topology, compiler, tokenizer, and store.
    • Retrieval reads persisted local artifacts; it should not fetch remote source.
    • MCP adapts store/retrieval behavior to protocol tools/resources/prompts.

  4. Make scoped changes.

    • Add shared types in core only when more than one package needs the contract.
    • Add schemas at runtime boundaries: CLI args, HTTP requests, MCP tool inputs, config files.
    • Keep errors structured and diagnostics sanitized; never leak tokens.
    • Update docs when behavior, public surfaces, config, or workflow expectations change.

  5. Validate.

    • Run the narrow test first, such as bun test packages/topology or bun test apps/server.
    • Run repo gates before finalizing: bun run typecheck, bun run lint, bun test.
    • For docs/skills changes, run python skills/document-codebase/scripts/check_markdown_links.py ..

Common Skill Handoffs

  • CLI command work: use $add-cli-command.
  • HTTP route work: use $add-http-route.
  • MCP tool work: use $add-mcp-tool.
  • Build pipeline work: use $change-build-pipeline.
  • Document or skill classification work: use $change-doc-classification.