andreferraroandCursor
5307e2a9fa
sonar / sonar (push) Skipped
sonar / sonar (pull_request) Successful in 41s
Add Spec Kit (cursor-agent), Constitution 1.0.1, Cursor skills/rules, and tooling docs so workshop agents follow Plane-backed SDD with versioned agent assets. Co-authored-by: Cursor <cursoragent@cursor.com>
22 lines
1.3 KiB
Plaintext
22 lines
1.3 KiB
Plaintext
---
|
|
description: graphify knowledge graph context
|
|
alwaysApply: true
|
|
---
|
|
|
|
This project has a graphify knowledge graph at graphify-out/.
|
|
|
|
**MANDATORY: Before using Read, Grep, Glob, or Bash to explore the codebase, you MUST run graphify first:**
|
|
- `graphify query "<question>"` — scoped subgraph for any codebase or architecture question
|
|
- `graphify path "<A>" "<B>"` — dependency path between two symbols
|
|
- `graphify explain "<concept>"` — all nodes related to a concept
|
|
|
|
This applies to YOU and to every subagent you spawn. Include this rule explicitly in every subagent prompt that involves code exploration. Do not skip graphify because files are "already known" or because you are executing a plan — the graph surfaces cross-file dependencies and INFERRED edges that grep and Read cannot find.
|
|
|
|
Only use Read/Grep/Glob directly when:
|
|
1. graphify has already oriented you and you need to modify or debug specific lines
|
|
2. `graphify-out/graph.json` does not exist yet
|
|
|
|
- If `graphify-out/wiki/index.md` exists, navigate it instead of reading raw files
|
|
- Read `graphify-out/GRAPH_REPORT.md` only for broad architecture review when query/path/explain do not surface enough context
|
|
- After modifying code files, run `graphify update .` to keep the graph current (AST-only, no API cost)
|