find-rules

Locates and summarizes applicable coding standards and guidelines for your current task.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/leonanpereirapinto/ai-utils --skill find-rules-leonanpereirapinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-rules
Source: https://github.com/leonanpereirapinto/ai-utils/tree/main/.agents/skills/find-rules
Command: npx skills add https://github.com/leonanpereirapinto/ai-utils --skill find-rules-leonanpereirapinto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and understand the specific rules, conventions, and guidelines that apply to your current task. It systematically explores project documentation to ensure compliance with project standards.

Core Features & Use Cases

  • Systematically locate relevant rule files across multiple sources (technology-specific and general guidelines).
  • Read, categorize, and prioritize rules by domain (Architecture, Testing, Security, Performance, Styling, etc.) and enforcement level (CRITICAL, MANDATORY, RECOMMENDED, SUGGESTED).
  • Present clear, actionable findings to guide development decisions and maintain project compliance.

Quick Start

Analyze the task context, locate rule files with Glob and Grep, and summarize applicable guidelines to proceed with compliant implementation.

Frequently Asked Questions about find-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover project rules and conventions before starting feature implementation?

To find architectural guidelines before coding, the Skill systematically locates rule files using Glob and Grep across multiple sources. It reads and categorizes these conventions by domain—such as Architecture, Testing, and Security—and enforcement level to ensure compliance before feature work begins.

Can I use this to check compliance for React, Elysia, and Tailwind projects?

Yes, you can check compliance for React, Elysia, and Tailwind projects. The discovery process locates technology-specific and general guideline files, categorizing rules by domain and enforcement level to present actionable findings tailored to your stack.

What is the best way to categorize project rules by enforcement level?

The best way to categorize project rules by enforcement level is to synthesize located documentation into distinct tiers: CRITICAL, MANDATORY, RECOMMENDED, and SUGGESTED. This prioritization guides development decisions by highlighting strict architectural constraints first.

How do I locate rule files across multiple sources systematically?

To locate rule files across multiple sources systematically, analyze the task context and apply Glob and Grep search strategies. This process identifies both technology-specific and general guidelines to summarize applicable standards for compliant implementation.

Does this work for discovering rules during refactoring and bug fixes?

Yes, this works for discovering rules during refactoring and bug fixes. The process applies to tasks spanning PRD creation, Technical Specs, Feature Implementation, Refactoring, and Bug Fixes, ensuring all modifications align with existing project standards.