har-workflow
25Cursor rule Cursor
HAR harness workflow — read AGENTS.md before changing anything.
458 tagged ai-tools, measured the same way as everything else here.
Browse within: ai-assistant 102cursor-ide 69documentation 62cursor-ai 61annotation 33annotations 33chatgpt 33agents-md 28component-library 28awesome 27cursor-rules 27design-tools 25frontend-tools 25ai-assisted-development 23
Cursor rule Cursor
HAR harness workflow — read AGENTS.md before changing anything.
Cursor rule Cursor
How Infigraph's multi-repo/group mode and taint analysis work internally — HTTP contract extraction heuristics, cross-service edge linking, combined-graph merge, remote mode, plus taint's line-based tracking and sanitizer heuristic.
Cursor rule Cursor
How Infigraph turns source into a graph — adding a language (tree-sitter vs ANTLR grammar-plugin), cross-file call resolution, SCIP compiler-grade enrichment, and file-watch/reindex triage.
Cursor rule Cursor
Infigraph architecture, build/test/lint commands, and cross-cutting invariants.
Cursor rule Cursor
Rules for using AMFS (Agent Memory File System) as a persistent agent brain across coding sessions.
Cursor rule Cursor
Apply the Layr modular product quality system.
vbcherepanov/total-agent-memory
Cursor rule
You have access to a persistent cross-session memory via the memory MCP server. Knowledge survives between sessions and is shared across agents working on the same project.
Cursor rule
Cursor rule "aictx" from oldskultxo/aictx, covering aictx, priority model, default loop, inspection and advanced tools and what to record.
itxaiohanglover/mcp-codestyle-server
Cursor rule
A rule for analyzing or changing code through the project’s codestyle tools. It requires starting with a project analysis or code-context exploration before reading or editing individual code areas.
Cursor rule Cursor
GuideAntsApi.DataModel/ Models/ # Add/modify entity classes ApplicationDbContext.cs # Configure relationships.
Cursor rule Cursor
Git branch, upstream, and push safety (never push feature work to main).
Cursor rule Cursor
Cursor rule "project-rules" from Elumenotion/GuideAnts, covering guideants project rules, project structure, technology stack requirements, frontend and backend.
Cursor rule
Prefer Local MCP tools for the user's Mac apps (email, calendar, contacts, messages, files, Office). Local, no API keys.
Cursor rule Cursor
Aura is a semantic version control engine running in this repository. It tracks code at the AST level — not text lines. It catches bugs, prevents accidental deletions, and verifies your work mathematically. Use it or you will cause regressions.
Cursor rule
You have access to the aura CLI. These commands are NOT optional. Use them as described below.
Cursor rule Cursor
Use ALWAYS when asked to CREATE A RULE or UPDATE A RULE or taught a lesson from the user that should be retained as a new rule for Cursor.
Cursor rule Cursor
APPLY software development decorators WHEN coding TO improve code quality and clarity.
Cursor rule
ALWAYS use when creating or updating Architecture document to ensure consistent documentation of architectural decisions. This rule enforces standardized arch format with proper context, consequences, and status tracking.
Cursor rule Cursor
KEDA ScaledObject and ScaledJob generation rules — auth patterns, scaling safety, best practices.
Cursor rule Cursor
Platform engineering rules — applies to all files in this workspace.
Cursor rule Cursor
You are a senior platform engineer working in production-first environments. Apply platform engineering best practices for Kubernetes, Terraform, GitOps, GitHub Actions, AWS, Azure, Helm, Kyverno, OPA/Conftest, observability, and PR review.
Cursor rule
Validates skills against best practices. Use when user says 'check skill', 'skillcheck', or 'validate SKILL.md'.
Cursor rule Cursor
This rule enforces best practices and coding standards for Bash scripting to improve code quality, maintainability, and security. It covers naming conventions, formatting, error handling, security, and performance considerations.
Cursor rule Cursor
Purpose: Process enforcement and team development standards for enterprise Rust projects. Use this for team environments requiring strict quality gates, design documentation, and automated workflow enforcement.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: