agentleFS
steepy-itsteepy-it/steepy-apex/.agents/skills/steepy-apex-bootstrap/SKILL.md

steepy-apex-bootstrap

Skill14 starsChanged 40 days agoApache-2.0View on GitHub

Project entry point for steepy-apex. Loads the root instructions and routes work through the governed hub.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before working on the project.

    line 10
  2. Distinctive:

    Read AGENTS.md in full for the project overview, development commands, and confirmed surfaces.

    line 14
  3. Very specific:

    Read .apex/_INDEX.md in full for the routing table and semantic knowledge map.

    line 15
  4. Very specific:

    When a Steepy workflow is needed, invoke it by its semantic skill name as listed in .apex/_INDEX.md.

    line 18
  5. Distinctive:

    Run the owning surface's test command and the hub coherence gate before reporting completion.

    line 19
  6. Very specific:

    Do not ordinarily enumerate, search, or read under .apex/work/.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
<!-- steepy:generated:steepy-apex-bootstrap:v1 -->

steepy-apex bootstrap

Use this skill before working on the project.

Procedure

  1. Read AGENTS.md in full for the project overview, development commands, and confirmed surfaces.
  2. Read .apex/_INDEX.md in full for the routing table and semantic knowledge map.
  3. Match the task to the owning surface and read only the minimum documents named by its routing row.
  4. State the owning surface and specialist agent before changing files.
  5. When a Steepy workflow is needed, invoke it by its semantic skill name as listed in .apex/_INDEX.md.
  6. Run the owning surface's test command and the hub coherence gate before reporting completion.

Work-artifact boundary

Do not ordinarily enumerate, search, or read under .apex/work/**.

A workflow phase may consume only the exact work inputs named by an accepted handoff. A pathless workflow invocation may perform only bounded workflow-header recovery discovery. Exact paths or a broader work-area scope are permitted only when the user explicitly delimits them. This applies transitively to child agents: only the phase orchestrator interprets a handoff.

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.