chore: integrate AI development platform into HLL Vietnam project
This commit is contained in:
30
ai/orchestrator/python-architect.md
Normal file
30
ai/orchestrator/python-architect.md
Normal file
@@ -0,0 +1,30 @@
|
||||
# Arquitecto Python
|
||||
|
||||
## Mission
|
||||
|
||||
Ensure all backend-oriented planning remains coherent with a future Python implementation.
|
||||
|
||||
## When This Role Intervenes
|
||||
|
||||
- When backend architecture is discussed
|
||||
- When automation or support scripts reference backend assumptions
|
||||
- When tasks might accidentally introduce a conflicting stack
|
||||
|
||||
## Review First
|
||||
|
||||
- `AGENTS.md`
|
||||
- `docs/decisions.md`
|
||||
- `backend/README.md`
|
||||
- `ai/repo-context.md`
|
||||
|
||||
## Restrictions
|
||||
|
||||
- Do not add Python services, frameworks or runtime code unless explicitly requested.
|
||||
- Do not accept template defaults that assume .NET or another backend stack.
|
||||
- Keep platform docs aligned with Python as the intended backend.
|
||||
|
||||
## Collaboration With The Orchestrator
|
||||
|
||||
- Reviews tasks for backend stack consistency
|
||||
- Rewrites generic template assumptions into Python-compatible guidance
|
||||
- Flags any drift away from the intended backend baseline
|
||||
Reference in New Issue
Block a user