| name | alembic-recipes |
| description | This project has a local Alembic knowledge base. Use Alembic Recipes, Guard context, and knowledge search proactively for this project when coding or answering project-standard questions. |
Alembic Recipe Context (Project Context)
This project has a local Alembic knowledge base. Use Alembic Recipes, Guard context, and knowledge search proactively for this project when coding or answering project-standard questions.
This skill provides the agent with this project's context from Alembic Recipes. Recipes are the project's standard knowledge base: code patterns, usage guides, and structured relations.
Knowledge Base Overview
| Part | Location | Purpose |
|---|
| Recipes | Alembic/recipes/*.md | Standard code patterns + usage guides; used for AI context, Guard, search |
| Snippets | Alembic/snippets/*.json | Code snippets synced to IDE via alembic install |
| Candidates | Alembic/.asd/candidates.json | AI-scanned candidates; review in Dashboard then approve |
| Context index | Alembic/.asd/context/ | Vector index built by alembic embed; semantic search via alembic_search(mode=semantic) |
Recipe = one .md file = one specific usage pattern or code snippet. kind: rule (Guard enforced) / pattern (best practice) / fact (structural knowledge). Recipe over project code: When both exist, prefer Recipe as curated standard.
Agent Permission Boundary
| Allowed | Forbidden |
|---|
Submit candidates (alembic_submit_knowledge / _batch) | Directly create/modify Recipes |
Search/get/expand compact context (alembic_search) | Publish/deprecate/delete |
Use returned detailRefs for follow-up context | Write to Alembic/recipes/ |
How to Find Recipes
- In-context index: Read
references/project-recipes-context.md in this skill folder
- MCP search:
alembic_search(operation=search, query=...) with kind/language/category filters
- MCP get/expand:
alembic_search(operation=get|expand, refId=...) for bounded follow-up context
- MCP search modes: keep
mode=auto unless exact keyword (keyword) or concept-level semantic retrieval (semantic) is needed
- Terminal:
alembic search <keyword>
Recipe over code search: When both find matches, prefer Recipe as source of truth. Cite Recipe title.
Use the clean structuredContent fields returned by alembic_prime and alembic_search as the Recipe context contract. Runtime diagnostics such as resident route, pure-local route, or vector availability belong in alembic_status (use aspect: "runtime" or aspect: "knowledge" when needed), not in ordinary Recipe guidance.
How to Use This Context
- Project standards/Guard: Use Recipe content as source of truth
- "How we do X here": Base answer on Recipe content
- Suggesting code: Cite Recipe's code snippet, not raw search results
- Guard/Audit:
// as:audit or MCP alembic_code_guard with explicit files, inline code, or current workRef scope — all use Recipes as standard
- Adoption evidence: mention the Recipe/detail ref in the work summary; default Codex MCP does not record adoption through a separate public usage tool
Auto-Extracting Headers for New Candidates
- From code (Recommended): Extract all import statements from user's code
- From existing Recipes: Search matching modules, then use
alembic_search(operation=get|expand, refId=...) for bounded context
- Via semantic search:
alembic_search(operation=search, mode=semantic, query="import ModuleName")
Related Skills
- alembic-create: Submit knowledge candidates (V3 fields, validation, lifecycle)
- alembic-guard: Code compliance checking against Recipe standards
- alembic-structure: Project structure, recipe_map navigation, and ProjectContext graph
