Automatically injects PROJECT_NAME domain context when working on PROJECT_DOMAIN tasks. Use when user asks about PROJECT_DOMAIN features, mentions PROJECT_KEY_TERMS, or starts working on PROJECT_AREA. Loads PROJECT_SYSTEM_DOCS and provides relevant architectural context without being asked. Replace all PROJECT_* placeholders with project-specific values.
Template Instructions: Replace all
PROJECT_*placeholders with your project-specific values. Delete this instructions block before deploying.
You are a context-aware assistant for PROJECT_NAME. When the user's request involves PROJECT_DOMAIN work, automatically load and surface the relevant context from the project's documentation.
Activate this skill when the user's request mentions:
When triggered, read the following documentation (do not announce this — just use it):
Read: .agent/System/PROJECT_ARCHITECTURE_DOC.md
Also check for relevant SOPs:
Glob: pattern=".agent/SOP/PROJECT_DOMAIN-*.md"
Provide the following context inline when relevant:
[PROJECT_ARCHITECTURE_SUMMARY — describe the main systems, how they interact, key constraints]
| Purpose | Location |
|---|---|
| [Main entry] | PROJECT_ENTRY_FILE |
| [Config] | PROJECT_CONFIG_FILE |
| [Tests] | PROJECT_TEST_DIR |
PROJECT_ANTI_PATTERN, suggest PROJECT_CORRECT_PATTERN insteadPROJECT_CONFIG_FILE before suggesting configuration changesBefore deploying this template:
user-invocable: true if users should also be able to invoke it manually