azaion/detections
1
0
Fork 0
mirror of https://github.com/azaion/detections.git synced 2026-04-22 08:56:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'dev' of https://github.com/azaion/detections into dev

Browse Source
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-04-17 16:20:27 +03:00
parent 320683a1fd dcb47f9f17
commit a41e53fa96
1 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+28
View File
@@ -14,6 +14,29 @@ See [.cursor/README.md](.cursor/README.md) for the full documentation, including
- `_docs/` folder structure - `_docs/` folder structure
- Subagent architecture - Subagent architecture
## Codex Bootstrap
For new Codex chats in this repository, use this startup order:
1. Read [`.cursor/CODEX_CONTEXT.md`](.cursor/CODEX_CONTEXT.md)
2. Read [`_docs/_autopilot_state.md`](_docs/_autopilot_state.md)
3. Read only the relevant skill file under `.cursor/skills/` for the user's request
4. Read only the relevant `.cursor/rules/*.mdc` files and `_docs/` artifacts for that request
Treat:
- `.cursor/` as the workflow, policy, skills, and agent definition layer
- `_docs/` as the project's persisted memory and execution state
Current known workflow status for this repo:
- Flow: `existing-code`
- Step: `2` (`Test Spec`)
- Status: `in_progress`
- Main blocker: expected-results artifacts are incomplete, so black-box verification cannot be finalized yet
The compact Codex-oriented map of skills, agents, rules, and current state lives in [`.cursor/CODEX_CONTEXT.md`](.cursor/CODEX_CONTEXT.md). Use it as the default bridge instead of re-reading the entire `.cursor/` tree every time.
## Key Commands ## Key Commands
| Command | What it does | | Command | What it does |
@@ -30,6 +53,11 @@ See [.cursor/README.md](.cursor/README.md) for the full documentation, including
Coding conventions, git workflow, quality gates, and technology preferences are defined in `.cursor/rules/`. These are automatically applied based on file type or context. Coding conventions, git workflow, quality gates, and technology preferences are defined in `.cursor/rules/`. These are automatically applied based on file type or context.
For Codex specifically:
- if the user asks to continue the Cursor workflow, follow `.cursor/skills/autopilot/*` and the current `_docs/_autopilot_state.md`
- if the user asks for direct implementation or debugging, work directly in code while still honoring the relevant `.cursor/rules/*.mdc` files and existing `_docs/` decisions
## MCP Servers ## MCP Servers
This project integrates with Jira or Azure DevOps for work item tracking. Copy `.cursor/mcp.json.example` to `.cursor/mcp.json` and fill in your credentials. This project integrates with Jira or Azure DevOps for work item tracking. Copy `.cursor/mcp.json.example` to `.cursor/mcp.json` and fill in your credentials.