agentleFS
redhat-community-ai-toolsredhat-community-ai-tools/UnifAI/.cursor/skills/codebase/SKILL.md

codebase-overview

Skill45 starsChanged 4 months agoApache-2.0View on GitHub

Project overview and domain routing table for the UnifAI monorepo. Each domain has its own skill with `paths` scoping for auto-surfacing when editing relevant files.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. erikediner/skills★ 1same name
    2. lyh843/AgentSkills★ 1same name
    3. husnain067/codebase-knowledge-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

Files
SKILL.md

UnifAI Codebase Overview

UnifAI is a multi-service platform for building and running AI agent workflows. The monorepo contains backend services (Python/Flask), a frontend (React/TypeScript), shared libraries, and infrastructure tooling.

Domain Routing Table

Path prefixDomainSkill
multi-agent/Multi-Agent System (MAS)domains/multi-agent/SKILL.md
rag/RAG Pipelinedomains/rag/SKILL.md
shared-resources/identity/Identity & Authdomains/identity/SKILL.md
ui/client/src/Frontend UIdomains/ui/SKILL.md
global_utils/Global Utilitiesdomains/global-utils/SKILL.md
backend/Platform Backenddomains/backend/SKILL.md
rag/infrastructure/celery/Celery Workersdomains/celery/SKILL.md
temporal-worker/Temporal Workersdomains/temporal-worker/SKILL.md
helm/Helm / Deploy Chartsdomains/helm/SKILL.md

Domain skills are auto-surfaced via paths when editing files in their scope.

Service Architecture Summary

ServiceRoleTech StackPort
multi-agentAI agent orchestration enginePython, Flask, MongoDB, Redis, LangGraph5001
ragDocument ingestion & retrievalPython, Flask, MongoDB, Qdrant, Celery5002
identityAuth, teams, SSOPython, Flask, Keycloak, MongoDB5003
backend (platform)Admin config, platform APIPython, Flask, MongoDB5000
uiWeb frontendReact, TypeScript, Vite, TailwindCSS3000
global_utilsShared Python libraryPython (package)—
celeryAsync task workers for RAGPython, Celery, Redis—
temporal-workerDistributed workflow executionPython, Temporal—

Cross-Cutting Concerns

ConcernWhere it lives
Authenticationshared-resources/identity/ + global_utils/identity.py
ConfigurationEach service's config/ + global_utils/config/
MongoDB accessEach service's adapters/ or infrastructure/
Redis cachingglobal_utils/redis/ + per-service usage
Message queuesRabbitMQ via Celery (global_utils/celery_app/)
Workflow orchestrationTemporal (multi-agent/adapters/outbound/temporal/)

Dev-Guide (optional factual reference)

The .cursor/unifai-dev-guide/ directory contains service documentation with class architecture, endpoint catalogs, port abstractions, and MongoDB/Qdrant schemas. Domain SKILL.md files already contain compact versions of the most useful tables. The full dev-guide is available for deeper reference:

ResourceDescription
.cursor/unifai-dev-guide/docs/services/<service>.mdFull endpoint signatures, class graphs, collection schemas
.cursor/unifai-dev-guide/source-map.yamlMaps services → composition roots, ports, endpoints, Mongo collections
.cursor/unifai-dev-guide/topology.yamlService graph, tech stacks, runtime edges
.cursor/unifai-dev-guide/guide-index.yamlMaps code path globs → doc sections (used by gen-docs.js, CI)

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.