Skip to main content
Version: v1.0

Detection matrix

Agentbriefer inspects common project manifests during init. Detection fills in an editable draft; it never replaces your judgment about the project's intended architecture or policy.

EcosystemSignalsTypical package manager
RustCargo.tomlCargo
Node.js / TypeScriptpackage.json and lockfilesnpm, pnpm, Yarn, or Bun
Gogo.modGo modules
Pythonpyproject.toml, requirements.txtProject-dependent
PHPcomposer.jsonComposer
Java / Mavenpom.xmlMaven
C#*.csprojNuGet / dotnet
F#*.fsprojNuGet / dotnet
Dartpubspec.yamlpub
JuliaProject.tomlPkg
Crystalshard.ymlShards
Haskellpackage.yaml, *.cabal, stack.yamlCabal or Stack
RDESCRIPTION, renv.lockrenv when present
RubyGemfile, Gemfile.lockBundler
SwiftPackage.swiftSwift Package Manager
Scalabuild.sbtsbt
JVM / Gradlebuild.gradle, build.gradle.ktsGradle
C / C++vcpkg.json, conanfile.txt, CMakeLists.txtvcpkg, Conan, or CMake
Elixirmix.exsMix
Clojuredeps.edn, project.cljClojure CLI or Leiningen
Erlangrebar.configRebar3
Objective-CPodfileCocoaPods
Lua*.rockspecLuaRocks
Perlcpanfilecpanm / Carton
Visual Basic .NET*.vbprojNuGet / dotnet
Nim*.nimbleNimble
PowerShell*.psd1PowerShellGet / PSResourceGet
Zigbuild.zig.zonZig package manager

Monorepos and mixed stacks

If several signals exist, Agentbriefer combines the evidence it understands and presents a proposal. Run init from the directory whose scope should receive the generated instructions:

cd ./services/payments
agentbriefer init

For a repository-wide policy plus package-specific policy, maintain an Agentbriefer configuration at each intentional instruction boundary.