agentleFS
Sign inStart free
amkiskoamkisko/prayers/.agents/skills/infer-conventions/SKILL.md

infer-conventions

Skill2 starsChanged 9 days agoMITView on GitHub

Learn how a repository actually writes, then encode genuine forks as executable checks. Use when the user wants to detect, infer, or standardize project conventions, resolve mixed patterns, or stop agents from inventing a second style. Documents reality by making the majority fail a command when violated. Do not use for one-off code review, to enforce formatting a project tool already owns, or to write agent convention markdown.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cashier-stripe-development, passport-development and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • whisper-moneySkill

    cashier-stripe-development

    Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling. Triggered when a user mentions Cashier, Billable, IncompletePayment, stripe_id, newSubscription, Stripe subscriptions, or billing. Also applies when setting up webhooks, handling SCA/3DS payment failures, testing with Stripe test cards, or troubleshooting incomplete subscriptions, CSRF webhook errors, or migration publish issues.

    Also in 5 projects that use this

  • datashamanSkill

    passport-development

    Develops OAuth2 API authentication with Laravel Passport. Activates when installing or configuring Passport; setting up OAuth2 grants (authorization code, client credentials, personal access tokens, device authorization); managing OAuth clients; protecting API routes with token authentication; defining or checking token scopes; configuring SPA cookie authentication; handling token lifetimes and refresh tokens; or when the user mentions Passport, OAuth2, API tokens, bearer tokens, or API authentication. Make sure to use this skill whenever the user works with OAuth2, API tokens, or third-party API access, even if they don't explicitly mention Passport.

    Also in 5 projects that use this

  • m3ueSkill

    ai-sdk-development

    TRIGGER when working with ai-sdk which is Laravel official first-party AI SDK. Activate when building, editing AI agents, chatbots, text generation, image generation, audio/TTS, transcription/STT, embeddings, RAG, vector stores, reranking, structured output, streaming, conversation memory, tools, queueing, broadcasting, and provider failover across OpenAI, Anthropic, Gemini, Azure, Groq, xAI, DeepSeek, Mistral, Ollama, ElevenLabs, Cohere, Jina, and VoyageAI. Invoke when the user references ai-sdk, the `Laravel\Ai\` namespace, or this project's AI features — not for Prism PHP or other AI packages used directly.

    Also in 6 projects that use this

  • gdarkoSkill

    fortify-development

    ACTIVATE when the user works on authentication in Laravel. This includes login, registration, password reset, email verification, two-factor authentication (2FA/TOTP/QR codes/recovery codes), profile updates, password confirmation, or any auth-related routes and controllers. Activate when the user mentions Fortify, auth, authentication, login, register, signup, forgot password, verify email, 2FA, or references app/Actions/Fortify/, CreateNewUser, UpdateUserProfileInformation, FortifyServiceProvider, config/fortify.php, or auth guards. Fortify is the frontend-agnostic authentication backend for Laravel that registers all auth routes and controllers. Also activate when building SPA or headless authentication, customizing login redirects, overriding response contracts like LoginResponse, or configuring login throttling. Do NOT activate for Laravel Passport (OAuth2 API tokens), Socialite (OAuth social login), or non-auth Laravel features.

    Also in 6 projects that use this

  • felipeArnoldSkill

    pennant-development

    Use when working with Laravel Pennant the official Laravel feature flag package. Trigger whenever the query mentions Pennant by name or involves feature flags or feature toggles in a Laravel project. Tasks include defining feature flags checking whether features are active creating class based features in `app/Features` using Blade `@feature` directives scoping flags to users or teams building custom Pennant storage drivers protecting routes with feature flags testing feature flags with Pest or PHPUnit and implementing A B testing or gradual rollouts with feature flags. Do not trigger for generic Laravel configuration authorization policies authentication or non Pennant feature management systems.

    Also in 3 projects that use this

  • gdarkoSkill

    medialibrary-development

    Build and work with spatie/laravel-medialibrary features including associating files with Eloquent models, defining media collections and conversions, generating responsive images, and retrieving media URLs and paths.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read infer-conventions.md in this skill directory for ground rules, steps, verdicts, how to choose a check, and edge cases.

    line 15
  2. Distinctive:

    Default is confirm: encode only what the person approves.

    line 27
  3. Very specific:

    Do not write convention files under .agents/conventions/ or restated bullets in AGENTS.md.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Infer conventions

Read infer-conventions.md in this skill directory for ground rules, steps, verdicts, how to choose a check, and edge cases.

You are encoding how this tree writes. You are not improving it. A convention that matters fails a command.

Quick reference

orient -> genuine-fork sweep -> architecture and house pass -> confirm -> add the check that fails on violation -> summarize

Default is confirm: encode only what the person approves. Encode without asking only when the invocation said to. Mixed styles still go to the person.

Do not write convention files under .agents/conventions/ or restated bullets in AGENTS.md.

Related

working-rules covers tests for a new check. minimal-implementation keeps the check small. dependency-policy applies before adding a new tool. engineering-audit reviews defects; this skill does not judge.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

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.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free