These examples show how to adapt Nexus-APCP for common project types without exposing real private context. Each kit is intentionally small: copy the structure, then replace placeholders with sanitized project-specific information.
| Example | Use when | Suggested profile |
|---|---|---|
web-app |
You are building a frontend or full-stack web application with an AI coding assistant. | web |
backend-api |
You are building an API, service layer, database-backed backend, or integration service. | backend-api |
ai-rag |
You are building an AI, RAG, agent, prompt, or LLM-powered product. | ai-rag |
security/password-hashing-prompt.md |
You need a sanitized prompt reference for password hashing design or review. | task-specific reference |
- Read the example closest to your project.
- Install the matching Nexus-APCP profile with
scripts/apcp-install.py. - Copy relevant sections into
AI_PROJECT_CONTEXT_PROTOCOL.md. - Add the first few tasks to
TASK_PROGRESS.yaml. - Keep private details local unless they are sanitized.
- Run:
python scripts/apcp-gather.py --caveman- Use placeholder domains, fake IDs, and sample data.
- Never include real credentials, production URLs, customer records, internal diagrams, or generated private context bundles.
- Keep security notes functional and neutral.