agentleFS
markmhendricksonmarkmhendrickson/neotoma/.claude/skills/setup-commands/SKILL.md

setup-commands

Skill38 starsChanged 2 months agoMITView on GitHub

Setup Commands (Legacy)

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Run or direct them to run setup-cursor-copies to refresh .claude/rules/ and .cursor/skills/.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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
<!-- Source: foundation/.cursor/skills/setup-commands/SKILL.md -->

name: setup-commands description: Legacy setup for .claude/skills; foundation uses skills instead. Prefer setup-cursor-copies. triggers:

  • setup commands
  • /setup_commands
  • setup-commands

Setup Commands (Legacy)

Foundation workflows have been replaced by skills. There is no longer a foundation/agent_instructions/cursor_commands/ directory; workflows live in foundation/agent_instructions/cursor_skills/{slug}/SKILL.md.

What to do instead

  1. Use setup-cursor-copies — Run ./foundation/scriptsscripts/setup_claude_instructions.sh.sh (or the setup-cursor-copies skill). It copies foundation rules into .claude/rules/ and foundation skills into .cursor/skills/.
  2. Load skills by trigger — When a trigger matches (e.g. commit, pull, push, fix-feature-bug), load the corresponding skill from .cursor/skills/{slug}/SKILL.md per the router rule.

When this skill is invoked

  • Tell the user that foundation no longer installs into .claude/skills/.
  • Run or direct them to run setup-cursor-copies to refresh .claude/rules/ and .cursor/skills/.
  • Repository-specific command files in docs/*_command.md (if any) may still be installed by setup into .claude/skills/ when configured in the manifest; foundation workflows are only in .cursor/skills/.

Related

  • setup-cursor-copies skill — Copies foundation rules and skills into .cursor/.
  • Foundation skills source: foundation/agent_instructions/cursor_skills/

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.