|
| 1 | +<!-- Priority: P0 --> |
| 2 | +<!-- Status: Not Started --> |
| 3 | +# S-0008-AI-Context-Manifest-and-Nuke-StartAI |
| 4 | + |
| 5 | +**User Story** |
| 6 | +As a developer using GitHub Copilot (or any AI agent), I want a single source of project context and a unified Nuke command to bootstrap AI context, so that Copilot can instantly understand the project's architecture, conventions, and goals, without manual explanation, and all team members have a consistent onboarding and daily AI experience. |
| 7 | + |
| 8 | +**Acceptance Criteria** |
| 9 | +- An `ai-manifest.yaml` (or `ai-manifest.json`) file exists in the project root, describing project overview, architecture, directory/naming rules, roadmap, and glossary. |
| 10 | +- A Nuke target `StartAI` is available. Running `nuke StartAI` outputs the latest project manifest and key context files in a format suitable for Copilot/AI agent ingestion. |
| 11 | +- The command supports parameters (e.g., `--role Frontend`) to filter context for different roles. |
| 12 | +- Pre-commit and CI checks ensure the manifest is updated with any structural or convention changes. |
| 13 | +- The onboarding/contribution guide instructs new members to use `nuke StartAI` for AI context injection. |
| 14 | +- Team members can use `/sync`, `/roadmap`, `/why <file>` commands in Copilot Chat to quickly access project context (by referencing manifest sections). |
| 15 | +- Every new Story must be provided in both English and Chinese versions, as part of the AI context documentation standard. |
| 16 | + |
| 17 | +**Technical Tasks** |
| 18 | +- [ ] Draft and maintain `ai-manifest.yaml` in the root directory, including: |
| 19 | + - Project Overview (vision, features, tech stack) |
| 20 | + - Architecture (modules, DI, plugin system, data flow) |
| 21 | + - Directory & Naming Rules |
| 22 | + - Roadmap / Milestones |
| 23 | + - Glossary & FAQ |
| 24 | +- [ ] Add `StartAI` target to Nuke build script. |
| 25 | +- [ ] Implement logic to aggregate manifest, README, and progress reports for output. |
| 26 | +- [ ] Support context filtering by role (e.g., `nuke StartAI --role Backend`). |
| 27 | +- [ ] Add pre-commit and CI checks for manifest consistency. |
| 28 | +- [ ] Update onboarding/contribution docs with Copilot/AI context instructions. |
| 29 | +- [ ] (Optional) Implement ManifestSync CLI for auto-updating manifest from codebase. |
| 30 | +- [ ] Enforce the rule: every new Story must have both English and Chinese versions. |
| 31 | + |
| 32 | +**Notes** |
| 33 | +- This ensures all Copilot/AI agent users have consistent, up-to-date project context, maximizing AI-assisted development efficiency. |
| 34 | +- The solution is vendor-agnostic and can be extended to other AI agents. |
| 35 | +- The manifest and Nuke integration provide a single source of truth and a unified developer experience. |
| 36 | +- Bilingual Story documentation is now a required part of the AI context standard. |
0 commit comments