Run any Skill in Manus with one click

$pwd:

ad-bootstrap

Name: Ad Bootstrap
Author: alexandremendoncaalvaro

// Generate AGENTS.md at the repo root by scanning the codebase first, pre-filling placeholders from observed signals, and asking only the genuine gaps. Use whenever the user wants to bootstrap, scaffold, generate, create, set up, or audit AGENTS.md / CLAUDE.md / agents.md (the operational guide for agents working on this project).

Run Skill in Manus

$ git log --oneline --stat

stars:667

forks:14

updated:May 22, 2026 at 04:49

File Explorer

2 files

SKILL.md

readonly

name	ad-bootstrap
description	Generate AGENTS.md at the repo root by scanning the codebase first, pre-filling placeholders from observed signals, and asking only the genuine gaps. Use whenever the user wants to bootstrap, scaffold, generate, create, set up, or audit AGENTS.md / CLAUDE.md / agents.md (the operational guide for agents working on this project).
summary	Generate or audit `AGENTS.md` at the repo root.

<background_information> Produces AGENTS.md at the repo root, ≤150 lines, every line operational. Generic agent behavior (think-before-coding, verify-before-claiming-done, etc.) does NOT belong here — that lives in the ad-philosophy skill.

Three modes, detected from filesystem state:

AGENTS.md exists at the repo root → audit (do not rewrite, output drift list only)
AGENTS.md absent and only trivial files present (.git, node_modules, .gitignore, .gitattributes, .DS_Store, .env*, .idea, .vscode, LICENSE*, README.md) → greenfield (interview by placeholder, no scan)
AGENTS.md absent and meaningful code present → brownfield (scan first, pre-fill, ask only gaps) </background_information>

Step 0 — detect mode from the filesystem state above. Skip Step 1 unless the mode is brownfield.

Step 1 — scan (brownfield only). Read in this order, taking the first that exists for each category:

Manifests: package.json, pyproject.toml, Cargo.toml, go.mod, Gemfile, composer.json, pubspec.yaml.
README.md, plus any doc/ or docs/ directory.
Top-level directory listing.
doc/adr/ — binding decisions; read every ADR.
GUIDELINES.md at repo root — if present, the AGENTS.md sections that have a corresponding GUIDELINES.md section (Code Style → §2; Quality Gates → §8; Commit & PR → §10; Security & Privacy → §12) emit as pointer stubs instead of inline rules' ' reciprocity and ADR-0030 §1.
.claude/, .cursor/, .openai/, .agents/ — existing agent config.
Hook configs: .husky/, .pre-commit-config.yaml, .github/workflows/, .gitlab-ci.yml, .circleci/.
Lockfiles: package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock, Cargo.lock.
git remote -v for the repo URL.

Build a model of: stack (languages and versions), entry points, build / test / lint commands, conventions, quality gates, security boundaries, gotchas confirmed by code.

Step 2 — pre-fill. For every <placeholder> in the template, fill from observed signals. No fabrication. If a section has no signal, write <TODO: not yet wired> in one line and move on. Do not write meta-prose explaining the gap.

Step 3 — show only the gaps. Print to the user:

(a) placeholders that could not be filled from repo signals;
(b) signals that conflict (two test commands, two style configs, README contradicts code, etc.).

One question per gap. Skip everything filled confidently. Do NOT ask philosophical questions ("is this doc for agents or humans?", "what is the most important quality bar?") — those are decisions, not interview material.

Step 4 — write the file. On user confirmation, write AGENTS.md at the repo root. Cut every line that does not change agent behavior. No "External Resources" section (URLs are derivable from git remote and the manifest). No appended Universal Agent Behavior block. No marketing prose.

Audit-mode override: do NOT write the file. Produce a drift list. Format each line as: [file or section]: spec says X, code says Y. Suggested resolution: change spec / change code / discuss.

If something the user says contradicts what the code shows, surface the conflict. Don't silently trust the user; don't silently trust the code.

<output_contract> A single AGENTS.md at the repo root, ≤150 lines, every line operational. No "External Resources" section. No appended Universal Agent Behavior block — that lives in the ad-philosophy skill. No meta-prose explaining gaps. In audit mode: a drift list, no file written.

AGENTS.md is a narrative document, so the Documentation Discipline rules in WORKFLOW.md §2 apply at write time:

No emoji anywhere in the file.
No dates, version stamps, DRAFT markers, or changelog blocks. Stack versions are facts (Node ≥18); release timelines are not.
Project Overview is the business-context-first paragraph — why the project exists before what it does.
One scope: this file is the operational guide for agents. Do not duplicate ARCHITECTURE.md patterns or ADR rationale here; link instead.
No speculation. If a section has no signal, write <TODO: not yet wired> once; do not narrate "this could be added later". </output_contract>

In team / mature: run /ad-architecture once load-bearing patterns emerge in the code.
When you scope a product (multi-feature, target user, success metrics): /ad-prd (Layer 3 of the six-layer artifact stack; excluded from poc).
When you start your first feature: /ad-spec (Layer 4 of the six-layer artifact stack; references parent PRD for product-scope inheritance).
Skip both above in poc / solo until the project genuinely needs them — the WORKFLOW §1 prune principle applies.
ad-philosophy auto-loads on non-trivial work.

related-skills.json

same repository

ad-review.md

from "alexandremendoncaalvaro/CorridorKey-Runtime"

Run this skill when the user explicitly invokes `/ad-review` or names it ("run ad-review", "use the ad-review skill"), or when the user asks for a code review with an explicit scope ("review this branch", "review main..HEAD", "revisa esse diff <range>"). Auto-trigger note: `allow_implicit_invocation: true` is set so review-language can fire the skill, but this also means broad review-adjacent conversation may auto-invoke a multi-step file-writing workflow. If a request is ambiguous, ask the user to confirm scope before invoking. Mechanical shape: ONE pass in the current session. The skill assembles the diff plus the relevant context, then produces a single review with findings grouped under `## Standards Findings` and `## Spec Findings` — two axes, one session. Standards = does the diff conform to AGENTS.md / ARCHITECTURE.md / GUIDELINES.md / CONTEXT.md / accepted ADRs? Spec = does the diff match the originating task / spec / PRD? The two-axis structure exists so neither axis masks the other. No `/clear`. No

2026-05-25667

ad-audit.md

from "alexandremendoncaalvaro/CorridorKey-Runtime"

Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, and ADR statuses against what the code actually does. Outputs a drift list, never writes files. Use when the user wants to audit, review for drift, sanity-check, or report inconsistencies between the repo's docs and its code.

2026-05-22667

ad-guidelines.md

from "alexandremendoncaalvaro/CorridorKey-Runtime"

Draft or update `GUIDELINES.md` at the repo root — the project's full engineering reference. Layer 1 Constitution trinity member (alongside `WORKFLOW.md` universal philosophy and `AGENTS.md` distilled rules). Covers Clean Architecture binding, SOLID application, Object Calisthenics tier (loose / moderate / strict per Bay 2008), naming conventions, error handling, complexity discipline, API rules, performance standards, build system, static analysis, quality gates, testing strategy, git workflow, documentation, and security. Scan-first — reads language toolchain, existing test/lint/format config, and existing AGENTS.md sections, pre-fills every placeholder it can verify, then asks only the genuine gaps and preference questions. Use when the user wants to draft, scaffold, audit, or update engineering guidelines / code standards / coding conventions / SOLID adoption / Object Calisthenics / testing strategy / security policy / build conventions for the project. Skill is lazy — file only exists when the project ne

2026-05-22667

ad-handoff.md

from "alexandremendoncaalvaro/CorridorKey-Runtime"

Compact the current session into a handoff document a fresh agent can pick up from. Saves to the OS temp dir (never the repo). Captures live state — current branch, open artifacts, unresolved decisions, in-progress diff, recent errors — references existing artifacts (PRD / spec / task / ADR) by path instead of duplicating them, and lists suggested next skills. Redacts secrets before writing. Triggers on "handoff", "hand off this session", "compact this conversation", "save context for next session", "pass to another agent", "wrap up the session", "context exhausted", "/clear", "/ad-handoff".

2026-05-22667

ad-next.md

from "alexandremendoncaalvaro/CorridorKey-Runtime"

Survey the project's state across the six-layer artifact stack and recommend prioritized next actions, modeled on `flutter doctor`. Use when the user asks "what's next", "next step", "where am I", "project status", "doctor", "what should I do", "audit my workflow". Read-only; complements `ad-audit` (drift detection, a different question). Profile-aware — `poc` suppresses Layer 3/4/5 noise, `team`/`mature` run the full survey.

2026-05-22667

ad-philosophy.md

from "alexandremendoncaalvaro/CorridorKey-Runtime"

Universal agent behavior and documentation discipline — think before coding, ground in real patterns, prefer simplicity, make surgical changes, define verifiable goals, verify before claiming done, and write documentation that captures only definitions and decisions. Auto-invokes on non-trivial changes, refactors, debugging, "think before coding", "ground before coding", "verify done", "before implementing", on documentation work — "writing docs", "writing readme", "writing architecture", "writing adr", "writing task", "audit docs" — or whenever the task is ambiguous enough that guardrails matter.

2026-05-22667

package.json

"author": "alexandremendoncaalvaro"

"repository": "alexandremendoncaalvaro/CorridorKey-Runtime"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

name	ad-bootstrap
description	Generate AGENTS.md at the repo root by scanning the codebase first, pre-filling placeholders from observed signals, and asking only the genuine gaps. Use whenever the user wants to bootstrap, scaffold, generate, create, set up, or audit AGENTS.md / CLAUDE.md / agents.md (the operational guide for agents working on this project).
summary	Generate or audit `AGENTS.md` at the repo root.

Three modes, detected from filesystem state:

AGENTS.md exists at the repo root → audit (do not rewrite, output drift list only)
AGENTS.md absent and only trivial files present (.git, node_modules, .gitignore, .gitattributes, .DS_Store, .env*, .idea, .vscode, LICENSE*, README.md) → greenfield (interview by placeholder, no scan)
AGENTS.md absent and meaningful code present → brownfield (scan first, pre-fill, ask only gaps) </background_information>

Step 0 — detect mode from the filesystem state above. Skip Step 1 unless the mode is brownfield.

Step 1 — scan (brownfield only). Read in this order, taking the first that exists for each category:

Manifests: package.json, pyproject.toml, Cargo.toml, go.mod, Gemfile, composer.json, pubspec.yaml.
README.md, plus any doc/ or docs/ directory.
Top-level directory listing.
doc/adr/ — binding decisions; read every ADR.
GUIDELINES.md at repo root — if present, the AGENTS.md sections that have a corresponding GUIDELINES.md section (Code Style → §2; Quality Gates → §8; Commit & PR → §10; Security & Privacy → §12) emit as pointer stubs instead of inline rules' ' reciprocity and ADR-0030 §1.
.claude/, .cursor/, .openai/, .agents/ — existing agent config.
Hook configs: .husky/, .pre-commit-config.yaml, .github/workflows/, .gitlab-ci.yml, .circleci/.
Lockfiles: package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock, Cargo.lock.
git remote -v for the repo URL.

Build a model of: stack (languages and versions), entry points, build / test / lint commands, conventions, quality gates, security boundaries, gotchas confirmed by code.

Step 3 — show only the gaps. Print to the user:

(a) placeholders that could not be filled from repo signals;
(b) signals that conflict (two test commands, two style configs, README contradicts code, etc.).

Audit-mode override: do NOT write the file. Produce a drift list. Format each line as: [file or section]: spec says X, code says Y. Suggested resolution: change spec / change code / discuss.

If something the user says contradicts what the code shows, surface the conflict. Don't silently trust the user; don't silently trust the code.

AGENTS.md is a narrative document, so the Documentation Discipline rules in WORKFLOW.md §2 apply at write time:

No emoji anywhere in the file.
No dates, version stamps, DRAFT markers, or changelog blocks. Stack versions are facts (Node ≥18); release timelines are not.
Project Overview is the business-context-first paragraph — why the project exists before what it does.
One scope: this file is the operational guide for agents. Do not duplicate ARCHITECTURE.md patterns or ADR rationale here; link instead.
No speculation. If a section has no signal, write <TODO: not yet wired> once; do not narrate "this could be added later". </output_contract>

In team / mature: run /ad-architecture once load-bearing patterns emerge in the code.
When you scope a product (multi-feature, target user, success metrics): /ad-prd (Layer 3 of the six-layer artifact stack; excluded from poc).
When you start your first feature: /ad-spec (Layer 4 of the six-layer artifact stack; references parent PRD for product-scope inheritance).
Skip both above in poc / solo until the project genuinely needs them — the WORKFLOW §1 prune principle applies.
ad-philosophy auto-loads on non-trivial work.

ad-bootstrap

Next

Next

ad-bootstrap

Next

More from this repository

More from this repository

Next