nightwire / rules
HackingDave/nightwire/.cursor/rules/post-change-verification.mdc
Run verification after code edits; before prod deploy only when deploy is part of the same agent task
The rules real projects give Cursor's agent, from .cursor/rules.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
HackingDave/nightwire/.cursor/rules/post-change-verification.mdc
Run verification after code edits; before prod deploy only when deploy is part of the same agent task
alkoleft/mcp-bsl-platform-context/.cursor/rules/isolation_rules/main.mdc
main rule
eng-accelerator/outskill-ai-lab/.cursor/rules/agentic_design_patterns.mdc
Core agentic design rules distilled from Agentic Design Patterns for building robust AI agents
coddy-project/coddy-agent/.cursor/rules/docs-translation.mdc
The Russian documentation tree (docs/ru), what moves with an English page, the stamp, and the writing rules for Russian and English documentation
coddy-project/coddy-agent/.cursor/rules/workflow.mdc
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge
PGshen/thinking-map/.cursor/rules/project-rule.mdc
ignore test failures - Don't forget to update documentation - Don't ignore code review feedback - Don't forget to implement proper error handling ## Development Environment ### Prerequisites - Go 1.24+ - Node.js
robotostudio/turbo-start-sanity/.cursor/rules/ultracite-migration.mdc
Guide for migrating from ESLint/Prettier to Ultracite
SeloSlav/2d-multiplayer-survival-mmorpg/.cursor/rules/spacetimedb.mdc
SpacetimeDB reference: reducers, tables, subscriptions, scheduling, and RLS patterns. Apply when implementing or reviewing server module logic, schema changes, generated bindings impacts, or client callback/dataflow behavior tied to SpacetimeDB.
UiPath/skills/.cursor/rules/skill-review.mdc
Strict skill audit/review framework — use when user asks to review, audit, grade, or compare skills, or when reviewing PRs that add or substantially modify a skill
Use-Tusk/drift-node-sdk/.cursor/rules/general-gotchas.mdc
description: globs: alwaysApply: false --- General gotchas to look for when reviewing code. Gotchas marked with "POTENTIAL BUG" have a high likelihood of causing a bug if not followed. Check
redhat-developer/rhdh/.cursor/rules/ci-e2e-testing.mdc
dependencies (prettier, prettier-plugin-sh, shellcheck). **Purpose**: This package provides essential tooling for maintaining code quality in the CI infrastructure, ensuring consistent formatting and shell script best practices across
redhat-developer/rhdh/.cursor/rules/e2e-fix-workflow.mdc
Verify Fix** (`e2e-verify-fix`) — Run the test multiple times and check code quality 7. **Submit and Review** (`e2e-submit-and-review`) — Create PR, trigger review, monitor CI **Critical rule
redhat-developer/rhdh/.cursor/rules/github-workflows-security.mdc
edit $PR_NUMBER --add-label "needs-review" ``` ### Preferred Pattern: pull_request + workflow_run When you need to run untrusted PR code AND access secrets/write permissions, split into two workflows: **Step
redhat-developer/rhdh/.cursor/rules/managing-ai-rules.mdc
frontmatter) ├── skills/ # One directory per skill, containing SKILL.md └── README.md # Documentation ``` `rulesync.jsonc` configures Cursor, Claude Code, and OpenCode, with the `rules`, `commands`, and `skills` features enabled. Use `yarn rulesync:generate
NexusGPU/tensor-fusion/.cursor/rules/requirement.mdc
driven, USE Ginkgo to write test cases, don't write native golang unit test, review codes and refactor until test works - When the task introduce some new memory state, consider
AniBullet/BsKeyTools/.cursor/rules/superpowers.md
when facing 2+ independent tasks that can be worked on without shared state. ### Code Review & Completion Skills - **superpowers/requesting-code-review** - Use when completing tasks, implementing major features, or before merging. - **superpowers/receiving-code-review
allthingslinux/tux/.cursor/rules/docs/docs.mdc
Master guide for AI agents working with Tux documentation rules and workflows
allthingslinux/tux/.cursor/rules/docs/patterns.mdc
Practical examples, documentation templates, and decision guides for common scenarios
allthingslinux/tux/.cursor/rules/docs/structure.mdc
Documentation organization, navigation structure, and content hierarchy guidelines
allthingslinux/tux/.cursor/rules/docs/zensical.mdc
Zensical setup, configuration, extensions, theme customization, and deployment workflows
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.