agentleFS
beCyborgbeCyborg/jadlis-nupp/skills/guide/SKILL.md

guide

Skill0 starsChanged 55 days agoNo licenceView on GitHub

Standing operating principles for the rest of the session: the six NUPP principles (Nearly Universal Principles of Projects) read for agent work — evidence over habit, saved attention and tokens, proactivity, weakest link, purpose, repeatable elements — with checkpoints for taking a task, risky steps and "done", checks per kind of work, and manager rules for issuing tasks and accepting reports. Load once; it stays in force until the session ends. TRIGGER when: user says "руководствуйся NUPP", "работай по NUPP", "подключи NUPP", "включи NUPP", "придерживайся NUPов", "follow NUPP", "work by NUPP", "turn NUPP on"; or a brief or the first line of a task tells this session to load nupp:guide. DO NOT TRIGGER when: one plan, report, brief or decision must be checked (use /nupp:check); a human project is struggling or a methodology is being chosen (use /nupp:nupp).

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grill, brainstorm 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.
  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 13 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 17 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.