infer-conventions

Detect Laravel project conventions and record them as path-scoped rules.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/F41541/koperasi-app --skill infer-conventions-f41541
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: infer-conventions
Source: https://github.com/F41541/koperasi-app/tree/main/.agents/skills/infer-conventions
Command: npx skills add https://github.com/F41541/koperasi-app --skill infer-conventions-f41541

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents and new teammates often write code that clashes with a project's established style because conventions live only in the codebase, not in documentation. This Skill systematically analyzes how a Laravel application is actually written and records those conventions as durable, path-scoped rules in .ai/rules that other agents read. ## Core Features & Use Cases - Systematic Convention Sweep: Evaluates roughly 49 Laravel convention dimensions across validation, controllers, Eloquent models, architecture, frontend, database, testing, and responses using a structured checklist with grep hints. - Architecture Discovery: Maps non-default app/ directories (Actions, Services, DTOs, Queries, domain modules) and records structural patterns and deliberate absences like "no repository layer". - Conflict and Default Filtering: Distinguishes genuine conventions from framework defaults, tooling-owned formats (Pint, Rector), and unresolved mixed patterns, requiring at least 3 consistent examples before recording. - Use Case: When onboarding an AI coding agent to an existing Laravel app, run this Skill to detect that the project uses legacy magic-method accessors and inline validation, then record those as rules so the agent matches the codebase instead of imposing modern defaults. ## Quick Start Analyze this Laravel project's coding conventions and record them as rules in .ai/rules using the record-rule tool.

Frequently Asked Questions about infer-conventions

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

FAQPage Schema
How do I document coding conventions in a Laravel project?▼

Run a systematic sweep of the codebase across dimensions like validation style, model patterns, and architecture, then record each confirmed convention as a path-scoped rule in .ai/rules. This Skill uses a 49-dimension checklist with grep hints and requires at least 3 consistent examples per convention.

How to make AI coding agents follow my Laravel project style?▼

Record your project's actual conventions as rules in .ai/rules using the Boost record-rule MCP tool, scoped to the paths where they apply. Agents reading those rules will match existing patterns like legacy accessors or inline validation instead of applying framework defaults.

What happens when my codebase has conflicting patterns?▼

Conflicts are reported with counts and example files but never recorded as rules, since that would describe an aspiration rather than reality. Recording only proceeds if you identify a stable path or context boundary that explains both styles.

Does this work if the record-rule tool is unavailable?▼

Yes, detection is read-only so the analysis steps still run without the tool. The full rule text is reported so you can enable BOOST_RULES_ENABLED or add the rules to .ai/rules manually.

When should I not use convention inference?▼

Skip it for one-off code reviews, formatting already handled by Pint or Rector, and fresh apps with too little code to show patterns. Framework defaults like anonymous migrations and ShouldQueue jobs are also excluded since agents write them unprompted.