agentleFS
Sign inStart free
randomittinrandomittin/heimdall/skills/stacks/SKILL.md

stacks

Skill5 starsChanged 38 days agoMITView on GitHub

Load stack-specific knowledge (conventions, exact lint/test/build commands, common failure patterns) onto the current role agent for the project's detected tech stack(s) — Next.js, React Native, Spring Boot, FastAPI, Django, Rust, etc. Use at the start of any task in an unfamiliar or newly-onboarded repo, or whenever acceptance criteria need a stack's exact command instead of a guess.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Endika/eskills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

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:

    Read every path it prints, then apply those conventions for the rest of the task — exact lint/format/test/build commands, directory layout, …

    line 24

≈ “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

stacks

Knowledge packs loaded onto existing role agents — never new role×stack agents. There is exactly one coder, one reviewer, one architect; a pack gives that same agent stack-specific judgment without changing its identity. Full design: skills/stacks/README.md.

Run it

bin/stack-detect [path]        # scan manifests, print detected stack id(s) as JSON
bin/stack-pack load [path]     # detect + print the pack file path(s) to read, in order

bin/stack-pack load prints, in layering order:

  1. Base pack — skills/stacks/<id>/PACK.md (cold-start scaffold, shipped with hmd).
  2. Repo refinement — any .planning/skills/*.md in the target project (learned, repo-specific notes that override the base pack where they disagree).

Read every path it prints, then apply those conventions for the rest of the task — exact lint/format/test/build commands, directory layout, runnable acceptance-criteria templates, common failure patterns + fixes. Your identity as the current role does not change; only your knowledge of this stack does.

Detection already runs for you

A SessionStart hook runs bin/stack-detect and writes the result to .planning/detected-stack.json when the project is a Heimdall project. If that file exists, read it directly instead of re-running detection, then call bin/stack-pack load (or resolve the paths yourself from the ids it lists) to get the pack(s) to read.

Supported stack ids

nextjs · react-native · react · vue · svelte · node · spring-boot · jvm · fastapi · django · flask · python · go · rust — detection rules for each: skills/stacks/README.md.

Adding a new pack

Copy STACK_PACK_TEMPLATE.md (repo root) to skills/stacks/<stack-id>/PACK.md, fill every section, and confirm bin/stack-detect already emits that <stack-id> — a pack whose id stack-detect never emits is never loaded.

Verification

  • bin/stack-detect . on a repo whose package.json depends on next prints {"stacks":["nextjs"], ...} (a signals array included).
  • bin/stack-pack load . on that same repo prints a path ending in skills/stacks/nextjs/PACK.md.
  • A repo that also has a .planning/skills/*.md file gets that path printed AFTER the base pack path — repo refinement layers on top, never instead of.
  • A repo matching none of the known stacks: bin/stack-detect . prints {"stacks":[],"signals":[]} and bin/stack-pack load . prints no pack path.

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