Results for “rule”

Review Markdown prose against agent-style's 21 rules. `/style-review FILE` audits the file and (on user confirm) writes a polished copy at `FILE.reviewed.md`. `/style-review A.md B.md` A/B-compares two drafts and emits a per-rule delta table. Complements the generation-time rules installed via `agent-style enable <tool>`.

Scans legacy codebases to extract implicit coding conventions across architecture dimensions, resolves conflicts interactively, and generates an enforceable style rules file.

Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.

Defines scope, objectives, rules of engagement, threat model selection, and operational timelines for red team engagements before any offensive testing begins.

Initializes or optimizes git-agent configuration, regenerates commit scopes from git history, and re-derives .gitignore rules.

Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.

Plans parallel agents or worktrees with isolated ownership, validation lanes, and merge rules. Use only for safely separable work.

Generates speech from text using ElevenLabs TTS with local playback, supporting voice selection, pronunciation rules, and audio tags.

`task-agent`: use for repository methods, query behavior, record mapping, visibility, errors, or transaction participation; skip schema, migration, DTO, and domain-rule work.

Records Clean Room initialization preferences, separated artifact locations, model policy, schema profile, and clean-safe rule defaults before a clean-room run starts or resumes.

Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.

`analysis-agent`/`task-agent`/`review-agent`: use when logic, rules, invariants, branches, edges, or failure paths need isolated tests; skip without a unit-test decision.

Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2) graduating a pattern from notes to enforced rules, (3) turning a debugging solution into a skill, (4) checking memory health and capacity.

`analysis-agent`/`task-agent`: use when a use case coordinates authorization, domain work, transactions, or external effects; skip transport, storage, and rule-only work.

`analysis-agent`/`task-agent`/`review-agent`: use when fixtures, factories, seeds, isolation, cleanup, or sensitive test-data rules change; skip when test data is unaffected.

The current Pencil MCP tool surface, `execute` idiom catalog, transport table, and document-discipline rules. Read before any Pencil call, in either `cli-app` or `editor` mode.

Trigger: security rules, credential leaks, auth tokens, input sanitization, threat model. Scope: Software security guidelines, threat prevention, secure data handling. Boundary: Excludes client-side web browser vulnerabilities.

Never show the user a first draft. Run every writing task through a self-critique loop — draft, attack the draft as the harshest reviewer in the room, rewrite, and repeat until a full review pass finds zero flags — then return only the final plus a change log. Use for any writing the user actually cares about: emails, LinkedIn posts, newsletters, docs, announcements, client messages. Trigger whenever the user says 'run the loop', 'self-critique this', 'make it bulletproof', 'don't give me a first draft', 'be brutal', or hands over a task where quality matters more than speed. This is a single-agent loop; for the three-agent version use the-team.

Route a task to the most fitting skill or agent. Parses user intent, checks installed-skill inventory, and picks the best match (single skill or chain).

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Scores generated text for morphosyntactic well-formedness by measuring how closely it adheres to language-specific dependency rules extracted from treebanks.

Interactive installer for Everything Codex — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

Filters and prioritizes compound libraries in drug discovery using drug-likeness rules, structural alerts, complexity metrics, and a query language.

Trigger: sitemap, navigation, menu structure, wayfinding, labeling, search facets, routing links. Scope: Visual hierarchies, wayfinding, navigation model, sitemaps. Boundary: Excludes backend route handlers or page performance tuning.

Expert in Cursor AI IDE - the leading AI-powered code editor. Covers Rules files for project-specific AI behavior, Plan Mode for structured development, Background Agents for parallel work, and advanced features like voice mode and browser integration. Essential for developers maximizing AI-assisted coding productivity. Use when "cursor ai, cursor rules, .cursorrules, cursor composer, cursor agent, plan mode, background agent, cursor tips, cursor, ide, ai-coding, editor, productivity, agent, developer-tools" mentioned.

Seven-role depersonalised panel review of framework artefacts (KUD, criterion bank, LT definition, crosswalk, scope-and-sequence) in sequential-isolation mode. Gate rule mean>=88 AND no role<70.

Legacy/migration guidance for v1 StateMachine entities. In v2, lifecycle rules are implementation contracts owned by MCP servers, not first-class records to create during normal project work.

Design a lead routing and SLA model someone can actually implement. The assignment rules, the round-robin or account-based logic, the SLA timers, and the fallbacks when a rep is out or a lead has no owner. Built for B2B RevOps teams, customizable to your CRM and your team shape. Trigger on "design lead routing", "who should get this lead", "build our SLA", "round robin rules", "leads are falling through", or any routing diagnostic.

Use when writing or reviewing tests, or when asked how to write a good single test. Encodes the per-test rules behind the "test the contract / responsibility, not the implementation" principle — name and structure one behavior per `it`, drive through the public surface, stub only true external boundaries, control time and config via documented knobs, and keep tests clear, isolated, and refactor-resilient. The same rules drive both authoring (write mode) and auditing existing tests (review mode).

Optimizes agent context setup by structuring rules, specs, source files, error output, and conversation history to improve output quality.