Project setup

Apply one baseline to every repository, then add the rules for each stack the repository uses. The target repository owns the result: it pins its own tool versions and installs its own skills. This skill only says what to install and where to get it.

Modes

• Setup applies the baseline to a new repository, or to an existing one when the user asks for the change.
• Audit reports the differences between the repository and the baseline, with file references and a proposed change for each. An audit does not install, generate, format, or move files.

State the mode before you start. If the request is not clear, run an audit.

New and existing repositories

The stack choices in this skill (Vite+, TypeScript 7, TanStack Query, Effect, golangci-lint, PostgreSQL) are defaults for new projects. In an existing repository, keep the established stack, package manager, and documentation layout. Report a stack migration as a proposal; do it only when the user puts it in scope. Read the ADRs and data-ownership rules before you interpret leftover configuration.

Procedure

1. Inspect. Read the existing agent instructions, git status, and the manifests (package.json, go.mod, mise.toml, prek.toml, dprint.json). Identify the stacks. Record any user edits in the working tree and preserve them.

   Complete when you know the stacks and which baseline parts already exist.

2. Lay out instructions. Follow layout. Create the root AGENTS.md index and the .agents/rules/ files. Keep existing rules that still apply; move them into the matching rule file. When the repository writes documents, also write docs/AGENTS.md from docs-agents and link it from the index.
3. Install the common tooling and rules. Follow these for every repository:
   • tooling: mise and .mise/tasks, prek, dprint, documd, and e2e.
   • testing: test policy, tiers, coverage, and enforcement.
   • documentation: document layout, the docs/AGENTS.md standard, figures, and Fumadocs for public docs.
   • github: commits, issues, PRs, CI, and Dependabot.
4. Apply each stack. Read only the matching references:
   • Go service: go.
   • Go service with a web UI: go, typescript, and web.
   • TypeScript full stack: typescript, web, and ts-fullstack.
   • The application owns relational data: database. Persistent data alone does not require PostgreSQL; a file store or an external system of record may own it.
5. Install skills. Add each upstream skill to the skills:install task and to .agents/skills/.gitignore, then run mise run skills:install. Do not copy skill content into this skill or write it from memory. See skill sources.
6. Bootstrap. Run mise install, the locked dependency install (mise run install), mise run skills:install, mise run hooks:install, and the browser install for e2e when the repository has one.
7. Verify. After an initial setup, run prek validate-config prek.toml, mise run format, and mise run check. After an incremental change, run the checks for the changed area, and widen them for shared contracts. Report each check that you did not run and why.

Before you add a tool, ask if the repository needs it now. Skip parts that do not apply. For example, do not add PostgreSQL when the application owns no relational data, do not add e2e to a library without a user interface, and do not add Fumadocs without public documentation.

Skill sources

Skills live in .agents/skills/ at project scope. There are two kinds:

• Upstream skills come from a GitHub repository (see the table). Do not commit them, because they can be large and the upstream owns them. List each one in .agents/skills/.gitignore, and install it with the skills:install task.
• Local skills exist only in this repository. Commit them.

The task pins each upstream skill to a tag or a commit SHA, so every checkout gets the same content. --force lets the task run again over an existing install. To update a skill, change its pin and run the task again.

#!/bin/bash
#MISE description="Install the pinned upstream agent skills into .agents/skills"
set -euo pipefail

# Upstream skills are not committed; .agents/skills/.gitignore lists them.
# To update one, change its pin here and run this task again.
install() {
	gh skill install "$1" "$2" --pin "$3" --dir .agents/skills --force
}

install tester-army/e2e e2e <tag-or-sha>

# Upstream skills. `mise run skills:install` installs them at pinned versions.
e2e/

When you add a skill, pin the latest release tag. If the repository has no release, pin the head commit SHA of the default branch. Do not pin a branch name. Review the skill content before you add it to the task. A skill with many files installs slowly, because gh downloads each file separately.

install-anti-slop is a one-time installer. Run it from its upstream copy during setup; do not keep it in the repository unless the team updates anti-slop often.