agentleFS
AkaraChenAkaraChen/luna/.agents/skills/grill-with-docs/SKILL.md

grill-with-docs

Skill4 starsChanged 6 months agoNo licenceView on GitHub

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

226 other projects use a version of this, 34 of them edited; 26 of 34 edited versions we compared changed its rules; 3 new projects in the last 4 weeks, against 3 the 4 before.

How people change it

26 of 34 edited versions changed its rules, and some changes recur.

Of the 34 edited versions we compared: 8 keep every rule, 26 made changes of their own.

Rules people drop

  1. If a question can be answered by exploring the codebase, explore the codebase instead.dropped by 5 of 26
  2. If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:dropped by 3 of 26
  3. When a term is resolved, update CONTEXT.md right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).dropped by 3 of 26
  4. Only offer to create an ADR when all three are true:dropped by 3 of 26
  5. If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).dropped by 3 of 26
  6. Create files lazily — only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.dropped by 2 of 26
  7. When the user uses a term that conflicts with the existing language in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"dropped by 2 of 26
  8. When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."dropped by 2 of 26

Rules people add

  1. Don't couple CONTEXT.md to implementation details. Only include terms that are meaningful to domain experts.added by 19 of 26
  2. If a *fact* can be found by exploring the environment (filesystem, tools, codebase), look it up rather than asking me. The *decisions*, though, are mine — put each one to me and wait for my answer.added by 4 of 26
  3. Do not act on the plan until I confirm we have reached a shared understanding.added by 4 of 26
  4. A rule we can't quote: its licence doesn't allow itadded by 2 of 26
  5. A rule we can't quote: its licence doesn't allow itadded by 2 of 26
  6. A rule we can't quote: its licence doesn't allow itadded by 2 of 26
  7. A rule we can't quote: its licence doesn't allow itadded by 2 of 26
  8. A rule we can't quote: its licence doesn't allow itadded by 2 of 26

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 3 new projects took it in the last 4 weeks, 1× the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 1 new projectWeek of Nov 1: 1 new projectWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 6 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use decision-mapping, writing-beats and 9 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.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 9 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 65 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 67 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 63 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 56 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 160 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 160 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.

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.