agentleFS
Sign inStart free
nearmapnearmap/shipyard/skills/standards/SKILL.md

standards

Skill1 starsChanged 21 days agoMITView on GitHub

Resolve authoritative repository engineering policy for implementation, or run a cited conformance review. Loads only the mode-specific procedure and relevant rules.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use design.

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.
  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    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 8 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:

    If mode is omitted: /sy:spec and /sy:ship normally mean resolve.

    line 20
  2. Distinctive:

    Keep returns compact and source-pointed.

    line 24
  3. Very specific:

    Every subagent dispatch resolves its model and effort from config and passes them as the Agent invocation's actual model and effort …

    line 26

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

Resolve policy without inventing or duplicating it.

$ARGUMENTS

Choose one mode, then load only its reference:

resolve <scope> → references/resolve.md
review <scope>  → references/review.md

If mode is omitted: /sy:spec and /sy:ship normally mean resolve; sy:gate means review.

Authority order is always: dedicated repo standards skill → repository-maintained standards docs/rules → Shipyard fallback. Lower authority never overrides higher authority.

Keep returns compact and source-pointed. Human-facing plans may explain unusual constraints clearly; agent-facing standards contracts contain only task-relevant rules, primitives, lenses, and conflicts.

Every subagent dispatch resolves its model and effort from config and passes them as the Agent invocation's actual model and effort parameters, per ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/model-dispatch.md; a nested dispatch inherits nothing and must resolve again.

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