acstack 0.54.2 → 0.54.4

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "acstack",
   "description": "Agentic coding stack where planning grows only as far as needed: a map of decisions, tasks, checks, and handoffs behind a pluggable tracker.",
-  "version": "0.54.2",
+  "version": "0.54.4",
   "author": {
     "name": "ac8318740"
   },

package/README.md

@@ -55,13 +55,10 @@ Install the plugin:
 /plugin install acstack@ac-agentic-coding
 ```
 
-Then, in your project:
+Then, in your Git repository, use `/acstack:implement`, `/acstack:quick-fix`, or `/acstack:pre-commit-review` directly. Without project configuration, ACStack follows repository instructions and discovers tooling from manifests, tests, and CI.
 
-```
-/acstack:setup
-```
-
-- `/acstack:setup` detects the project type, then writes `project.yaml` with workflow settings into the project folder
+- Optional: `/acstack:setup` detects the project type and writes `project.yaml` for saved workflow settings and storage-backed features such as maps and living specs
+    - Existing configuration keeps its gates; invalid configuration or project-data conflicts require repair, not an unconfigured fallback
 - All ACStack-owned project records live in one project folder per repository, shared by all of its worktrees
     - `~/.claude/acstack/bin/acstack project-data path` prints it; by default it is `~/.acstack/projects/<key>/`, outside the repository
     - Run `acstack project-data mode tracked` to keep the records in the repository's `.acstack/` and commit them instead
@@ -69,7 +66,7 @@ Then, in your project:
 - Update installed ACStack tools before migrating an older project
     - Stop old agents and reviews, run `~/.claude/acstack/bin/acstack project-data migrate`, then restart with updated tools
     - Migration aborts on collisions without overwrites or Git index changes; tracked old paths become pending deletions
-- The SessionStart hook loads the orchestrator instructions whenever it detects an ACStack project
+- The SessionStart hook loads the orchestrator instructions in Git repositories, even without project setup
 - Your CLAUDE.md stays clean for project-specific content
 - Upgrading from a version before 0.8.0 means deleting one stale `@import` line (see [docs/migrate-0.8.md](docs/migrate-0.8.md))
 
@@ -82,7 +79,7 @@ pi install npm:@tintinweb/pi-subagents
 pi install npm:acstack
 ```
 
-Then, in your project, run `/acstack:setup`.
+Then use the general workflows in your Git repository immediately. Run `/acstack:setup` only when you want saved project settings or storage-backed features, as described above.
 
 - Every skill runs under the same name as on Claude Code, e.g. `/acstack:map`
     - `/acstack map` does the same
@@ -92,7 +89,7 @@ Then, in your project, run `/acstack:setup`.
     - The extension lists the skills in the system prompt instead, so the model still reads one when the task matches
 - `pi/extension.ts` does what the Claude Code hooks do
     - It links the CLI at `~/.claude/acstack/bin/acstack`
-    - It adds the orchestrator instructions to the system prompt in an ACStack project
+    - It adds the orchestrator instructions in Git repositories, even without project setup
     - It lists ACStack's skills in the system prompt in every session
     - It re-injects a handoff after a compaction
     - It nudges with a continuity-versus-freshness checkpoint as the context fills

package/agents/codex/frontend-verifier.toml

@@ -33,7 +33,7 @@ ACStack keeps project data in the project folder, the path `~/.claude/acstack/bi
 
 You do not read `frontend.browser.mode` or `frontend.browser.fallback`. Step 3 asks the ACStack CLI which browser mode to use, and the CLI reads both.
 
-If `<project folder>/project.yaml` has no `frontend` section, report SKIP and exit.
+If `<project folder>/project.yaml` is absent or has no `frontend` section, report SKIP (no configured frontend verification) and exit. Do not create configuration or require setup for general work. Report unreadable or invalid configuration and project-data resolution errors instead of treating them as absent.
 
 ## Step 0: Read the knowledge base
 

package/agents/codex/task-checker.toml

@@ -15,7 +15,7 @@ You are read-only: do not edit source, tests, or specs.
 ## Establish scope and ownership
 
 Read the supplied requirements, affected paths, known risks, and available command results.
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for commands, directories, environment activation, and applicable frontend gates.
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for commands, directories, environment activation, and applicable frontend gates. Without it, discover tooling from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`. Do not require setup, invent commands, or bypass invalid config or resolution errors.
 
 - Distinguish focused review from ownership of completion verification
 - If the assignment is unclear, clarify it with the delegating session before duplicating checks

package/agents/codex/task-executor.toml

@@ -17,7 +17,9 @@ Implement the assigned requirements under the shared Implementation discipline i
 
 ## Project configuration
 
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for project-specific settings:
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover settings from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup or invent commands. Report invalid config and resolution errors rather than bypassing them.
+
+Configured settings:
 
 - `directories.source` – where to write source code
 - `directories.tests` – test directory, subject to assigned ownership

package/agents/codex/test-writer.toml

@@ -26,7 +26,9 @@ You write tests from requirements and application programming interface (API) co
 
 ## Project configuration
 
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for project-specific settings:
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover settings from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup or invent commands. Report invalid config and resolution errors rather than bypassing them.
+
+Configured settings:
 
 - `directories.tests` – where to create test files
 - `directories.source` – source code root (for mirroring structure)

package/agents/frontend-verifier.md

@@ -33,7 +33,7 @@ ACStack keeps project data in the project folder, the path `~/.claude/acstack/bi
 
 You do not read `frontend.browser.mode` or `frontend.browser.fallback`. Step 3 asks the ACStack CLI which browser mode to use, and the CLI reads both.
 
-If `<project folder>/project.yaml` has no `frontend` section, report SKIP and exit.
+If `<project folder>/project.yaml` is absent or has no `frontend` section, report SKIP (no configured frontend verification) and exit. Do not create configuration or require setup for general work. Report unreadable or invalid configuration and project-data resolution errors instead of treating them as absent.
 
 ## Step 0: Read the knowledge base
 

package/agents/task-checker.md

@@ -15,7 +15,7 @@ You are read-only: do not edit source, tests, or specs.
 ## Establish scope and ownership
 
 Read the supplied requirements, affected paths, known risks, and available command results.
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for commands, directories, environment activation, and applicable frontend gates.
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for commands, directories, environment activation, and applicable frontend gates. Without it, discover tooling from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`. Do not require setup, invent commands, or bypass invalid config or resolution errors.
 
 - Distinguish focused review from ownership of completion verification
 - If the assignment is unclear, clarify it with the delegating session before duplicating checks

package/agents/task-executor.md

@@ -17,7 +17,9 @@ Implement the assigned requirements under the shared Implementation discipline i
 
 ## Project configuration
 
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for project-specific settings:
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover settings from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup or invent commands. Report invalid config and resolution errors rather than bypassing them.
+
+Configured settings:
 
 - `directories.source` – where to write source code
 - `directories.tests` – test directory, subject to assigned ownership

package/agents/test-writer.md

@@ -26,7 +26,9 @@ You write tests from requirements and application programming interface (API) co
 
 ## Project configuration
 
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for project-specific settings:
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover settings from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup or invent commands. Report invalid config and resolution errors rather than bypassing them.
+
+Configured settings:
 
 - `directories.tests` – where to create test files
 - `directories.source` – source code root (for mirroring structure)

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "acstack-cli",
-  "version": "0.54.2",
+  "version": "0.54.4",
   "description": "CLI for the ACStack agentic coding stack",
   "type": "module",
   "license": "MIT",

package/docs/config-reference.md

@@ -2,13 +2,17 @@
 
 *Every key in `project.yaml`, the values it takes, its default, and what changes when you change it.*
 
-One file, `<project folder>/project.yaml`, holds every setting that belongs to a project.
+Optional `<project folder>/project.yaml` holds saved ACStack project settings.
 The project folder is the repository's ACStack data folder, the path `~/.claude/acstack/bin/acstack project-data path` prints (section 1 explains where it lives).
 
+General implementation, investigation, and review work without setup. Without this file, agents use repository instructions, manifests, existing tests, and CI to discover commands and directories. They do not invent commands or create configuration automatically. Run `/acstack:setup` when you want saved settings or storage-backed features such as maps and living specs.
+
+Existing configuration keeps its gates. Unreadable or invalid configuration, legacy data, and project-data conflicts require the reported repair; they are not absent-config fallbacks. Orphan warnings alone do not block general work.
+
 - **It names what to run**: the test, build, lint, typecheck, and format commands
 - **It names where to look**: the source and test directories, and the frontend
 - **It configures required gates**: spec sync, frontend verification, and design review
-- **Every skill and every agent reads it** before it runs anything
+- **Agents read it when present** before running project checks
 - **A key you leave out takes the default** this document gives it
 
 Three terms first.
@@ -70,7 +74,8 @@ These commands report configuration without changing settings.
 
 - `~/.claude/acstack/bin/acstack project-data path` prints the project folder's absolute path, even before the folder exists
     - It exits non-zero outside a Git repository
-    - It exits non-zero with a message naming the fix when legacy data, an orphaned entry, or a conflict needs attention
+    - It exits non-zero with a repair message for legacy, invalid, or conflicting data
+    - Orphan warnings do not block a valid current repository or adopt the orphan's settings
     - The session-start hook states the same path in the agent's context
 - This document writes a part inside it as `<project folder>/project.yaml`, `<project folder>/specs/`, and so on
 - `/acstack:setup` creates the folder with `mkdir -p "$(~/.claude/acstack/bin/acstack project-data path)"`

package/hooks/lib/read-guard.mjs

@@ -124,6 +124,9 @@ export function decide({ toolName, toolInput, cwd, main, ledger, settings }) {
     if (!main || !ledger) return { block: false };
     const file = wholeReadTarget(toolName, toolInput, cwd);
     if (!file) return { block: false };
+    // Native image reads are attachments; shell readers still dump bytes.
+    // shortcut: use image extensions, add content detection if extensionless images need exemption.
+    if (String(toolName).toLowerCase() === 'read' && /\.(png|jpe?g|gif|webp|bmp)$/i.test(file)) return { block: false };
     // Resolved only for a whole-file read, since it costs a CLI call.
     settings ??= readGuardSettings(cwd);
     if (!settings.enabled) return { block: false };
@@ -142,7 +145,7 @@ export function blockMessage(bytes) {
   const kb = Math.round(bytes / 1024);
   const tokens = Math.round(bytes / 4 / 1000) * 1000;
   return [
-    `This file is ${kb} KB (about ${tokens.toLocaleString('en-US')} tokens), and reading all of it is usually unnecessary. Instead:`,
+    `This file is ${kb} KB (rough text estimate: ${tokens.toLocaleString('en-US')} tokens), and reading all of it is usually unnecessary. Instead:`,
     '',
     '- Search for what you need, then read only that range',
     "- Or hand the question to an investigator, as ACStack's Delegate investigation section describes",

package/hooks/session-start.sh

@@ -186,11 +186,6 @@ if ! project_folder=$(acstack_project_folder "$cli_wrapper"); then
   exit 0
 fi
 
-if [ ! -f "$project_folder/project.yaml" ]; then
-  echo 'acstack: no project config found. Run /acstack:setup to set up.' >&2
-  exit 0
-fi
-
 claude_md="${plugin_root}/orchestrator/AGENTS.md"
 
 if [ -z "$plugin_root" ] || [ ! -r "$claude_md" ]; then

package/orchestrator/AGENTS.md

@@ -102,7 +102,15 @@ ACStack runs on Claude Code, Codex, and pi. The skills name each capability once
     - Never silently migrate data or work around legacy data by creating a partial project folder
 - Never change the Git index or force-add files to track project data
 
-All project-specific commands and paths come from `<project folder>/project.yaml`. Read this file before you run any build, test or lint command. If it doesn't exist, prompt the user to run `/acstack:setup`.
+Project setup is optional for general implementation, investigation, and review. Resolve the project folder first; a prospective path or a folder without `project.yaml` is not an error.
+
+- When `<project folder>/project.yaml` exists, read it before running build, test, or lint commands and preserve its configured gates
+- Without it, use repository instructions, manifests, existing tests, and CI to discover commands, directories, and environment activation
+    - Do not invent commands, assume a profile, or create configuration automatically
+    - If no useful check is discoverable, report that limit or ask for the missing command
+- An unreadable or invalid configuration is not absent configuration. Report it and stop work that depends on it; do not bypass its gates
+- Legacy, conflicting, or invalid project-data resolution also requires the reported repair, not an unconfigured fallback. Orphan warnings alone do not block work
+- Offer `/acstack:setup` when the user wants saved project settings or storage-backed features such as maps, living specs, or configured browser verification; do not require it for general work
 
 Key fields:
 
@@ -390,7 +398,7 @@ Read-only reviewers report discrepancies to the completion owner.
 
 The verification owner gathers evidence for the final revision. Opening a PR does not require running every test locally.
 
-Read `<project folder>/project.yaml` for the available commands and inspect the project's CI configuration before relying on it:
+Use `<project folder>/project.yaml` when present, otherwise discover commands under Project configuration above. Inspect the project's CI configuration before relying on it:
 
 1. Use focused local checks by default: cover changed behavior, affected callers, and relevant integration paths
 2. Run applicable build, lint, and typecheck checks; scope them when the tooling supports it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "acstack",
-  "version": "0.54.2",
+  "version": "0.54.4",
   "private": false,
   "description": "Agentic coding stack with first-class Claude Code and pi support: skills, orchestrator instructions, and verification agents.",
   "license": "MIT",

package/pi/agents/frontend-verifier.md

@@ -39,7 +39,7 @@ ACStack keeps project data in the project folder, the path `~/.claude/acstack/bi
 
 You do not read `frontend.browser.mode` or `frontend.browser.fallback`. Step 3 asks the ACStack CLI which browser mode to use, and the CLI reads both.
 
-If `<project folder>/project.yaml` has no `frontend` section, report SKIP and exit.
+If `<project folder>/project.yaml` is absent or has no `frontend` section, report SKIP (no configured frontend verification) and exit. Do not create configuration or require setup for general work. Report unreadable or invalid configuration and project-data resolution errors instead of treating them as absent.
 
 ## Step 0: Read the knowledge base
 

package/pi/agents/task-checker.md

@@ -19,7 +19,7 @@ You are read-only: do not edit source, tests, or specs.
 ## Establish scope and ownership
 
 Read the supplied requirements, affected paths, known risks, and available command results.
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for commands, directories, environment activation, and applicable frontend gates.
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for commands, directories, environment activation, and applicable frontend gates. Without it, discover tooling from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`. Do not require setup, invent commands, or bypass invalid config or resolution errors.
 
 - Distinguish focused review from ownership of completion verification
 - If the assignment is unclear, clarify it with the delegating session before duplicating checks

package/pi/agents/task-executor.md

@@ -23,7 +23,9 @@ Implement the assigned requirements under the shared Implementation discipline i
 
 ## Project configuration
 
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for project-specific settings:
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover settings from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup or invent commands. Report invalid config and resolution errors rather than bypassing them.
+
+Configured settings:
 
 - `directories.source` – where to write source code
 - `directories.tests` – test directory, subject to assigned ownership

package/pi/agents/test-writer.md

@@ -32,7 +32,9 @@ You write tests from requirements and application programming interface (API) co
 
 ## Project configuration
 
-Read `project.yaml` in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints for project-specific settings:
+Read `project.yaml` when present in the project folder that `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover settings from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup or invent commands. Report invalid config and resolution errors rather than bypassing them.
+
+Configured settings:
 
 - `directories.tests` – where to create test files
 - `directories.source` – source code root (for mirroring structure)

package/pi/extension.ts

@@ -648,13 +648,9 @@ export default function acstack(pi: ExtensionAPI): void {
 
 	const orchestratorFile = path.join(packageRoot, "orchestrator", "AGENTS.md");
 	const styleFile = path.join(packageRoot, "output-styles", "ac-writing-style.md");
-	const isProject = (cwd: string) => {
-		const folder = projectFolder(undefined, cwd);
-		return folder !== null && fs.existsSync(path.join(folder, "project.yaml"));
-	};
 	let warnedSubagents = false;
 
-	pi.on("session_start", async (event, ctx) => {
+	pi.on("session_start", async (_event, ctx) => {
 		if (!delegated) linkClis(ctx);
 		projectFolders.delete(path.resolve(ctx.cwd));
 		if (projectFolder(ctx, ctx.cwd) === null) return;
@@ -668,10 +664,6 @@ export default function acstack(pi: ExtensionAPI): void {
 				"warning",
 			);
 		}
-
-		if (event.reason === "startup" && !isProject(ctx.cwd)) {
-			report(ctx, "acstack: no project config found. Run /acstack:setup to set up.");
-		}
 	});
 
 	// /acstack map <args> and /acstack:map <args> both run ACStack's own map
@@ -685,9 +677,10 @@ export default function acstack(pi: ExtensionAPI): void {
 		// Every session, like the plugin's skills on Claude Code.
 		if (skillsPrompt) sections["acstack-skills"] = skillsPrompt;
 
-		if (isProject(ctx.cwd)) {
+		const folder = projectFolder(undefined, ctx.cwd);
+		if (folder !== null) {
 			const orchestrator = readText(orchestratorFile);
-			if (orchestrator) sections["acstack-orchestrator"] = `${orchestratorFor(orchestrator, delegated ? "delegated" : "lead")}\n\nThis repository's ACStack project folder: ${projectFolder(undefined, ctx.cwd)}\n`;
+			if (orchestrator) sections["acstack-orchestrator"] = `${orchestratorFor(orchestrator, delegated ? "delegated" : "lead")}\n\nThis repository's ACStack project folder: ${folder}\n`;
 			else report(ctx, `acstack: could not read ${orchestratorFile}`, "warning");
 		}
 

package/skills/commit/SKILL.md

@@ -45,7 +45,7 @@ For each planned commit:
 
 **This step is non-negotiable.** After drafting the commit message but BEFORE creating the commit, spec sync runs automatically.
 
-The project folder is the path `~/.claude/acstack/bin/acstack project-data path` prints. Read `<project folder>/project.yaml` – if `workflow.spec_sync` is `true` (or not explicitly `false`), run spec sync:
+The project folder is the path `~/.claude/acstack/bin/acstack project-data path` prints. Follow Project configuration in `orchestrator/AGENTS.md` for resolution errors and invalid config. If `project.yaml` is absent, commit using repository instructions without creating ACStack records. When present, read it; if `workflow.spec_sync` is `true` (or not explicitly `false`), run spec sync:
 
 1. Read `<project folder>/domain-map.yaml` (if exists)
 2. Map staged files to spec domains
@@ -62,7 +62,7 @@ The project folder is the path `~/.claude/acstack/bin/acstack project-data path`
 
 **Skip spec sync ONLY when:**
 
-- `workflow.spec_sync` is explicitly `false` in project.yaml
+- `project.yaml` is absent, or `workflow.spec_sync` is explicitly `false`
 - No `<project folder>/domain-map.yaml` exists
 - Changed files don't match any domain
 - Changes are docs/config only (no behavioral changes)
@@ -104,4 +104,4 @@ If commit fails due to pre-commit hooks:
 - NEVER use `git add -A` or `git add .` – stage specific files
 - Always create NEW commits after hook failures
 - Prefer specific file staging over broad patterns
-- Spec sync is MANDATORY – do not skip it unless explicitly disabled in project.yaml
+- Spec sync is MANDATORY when configured project records exist, unless disabled or the skip conditions above apply

package/skills/explore/SKILL.md

@@ -91,9 +91,11 @@ You have full context of the ACStack system. Use it naturally, don't force it.
 
 ### Check for context
 
-At the start, quickly check what exists – maps on the configured tracker
-(`ls "$(~/.claude/acstack/bin/acstack project-data path)/maps/"` on the files backend) and living specs
-(`~/.claude/acstack/bin/acstack list --specs --json`).
+When project configuration exists, check existing maps on its configured tracker
+and existing living specs. Without configuration, explore from repository guidance
+and code without requiring setup or creating records. Follow Project configuration
+in `orchestrator/AGENTS.md` for resolution errors and invalid configuration;
+neither is an absent-config fallback.
 
 ### When no map exists
 

package/skills/implement/SKILL.md

@@ -21,10 +21,13 @@ $ARGUMENTS
 
 ### 1. Find the work
 
-Check the configured tracker for maps (`workflow.maps.tracker` in
-`<project folder>/project.yaml`, where the project folder is the path
-`~/.claude/acstack/bin/acstack project-data path` prints; the map skill's `trackers/` docs declare the
-operations – files backend shown below).
+Resolve the project folder with `~/.claude/acstack/bin/acstack project-data path`.
+Preserve reported resolution errors; do not treat them as missing setup.
+When `project.yaml` exists and configures `workflow.maps.tracker`, check that
+tracker for maps (the map skill's `trackers/` docs declare its operations).
+Without configuration, work directly on the request without tracker writes.
+If the request names a map, establish its storage prerequisite first rather
+than silently ignoring it.
 
 **A map exists** (or `$ARGUMENTS` names one):
 
@@ -56,7 +59,10 @@ small unit of work, and nothing has to declare it small.
 
 ### 2. Read project configuration
 
-Read `<project folder>/project.yaml` for build/test/lint commands and directory paths.
+Read `<project folder>/project.yaml` when present. Otherwise discover commands,
+directories, and environment activation from repository instructions, manifests,
+existing tests, and CI, under Project configuration in `orchestrator/AGENTS.md`.
+Do not invent commands or treat invalid configuration as absent.
 
 ### 3. Create feature branch
 

package/skills/implement/design-pass.md

@@ -32,6 +32,8 @@ Load that context before your first edit under `frontend.directory`. Load it onc
 
 **Check the design gate first**
 
+This pass requires project configuration with a `frontend` section. If configuration is absent, skip this optional pass and use discovered repository checks; do not require setup. Follow Project configuration in `orchestrator/AGENTS.md` for invalid configuration and resolution errors rather than silently skipping them.
+
 The design gate is the set of optional checks impeccable adds to acstack's pipeline. `workflow.design_review` in `<project folder>/project.yaml` turns the gate on; the project folder is the path `~/.claude/acstack/bin/acstack project-data path` prints. Ask acstack for the answer:
 
 ```bash

package/skills/map/SKILL.md

@@ -24,7 +24,11 @@ Two backends ship in this skill's directory: `trackers/github.md` for repos
 with GitHub auth, and `trackers/files.md` as the fallback.
 
 ACStack keeps project data in the project folder, the path
-`~/.claude/acstack/bin/acstack project-data path` prints.
+`~/.claude/acstack/bin/acstack project-data path` prints. If `project.yaml` is
+absent, chart in conversation without tracker writes. Before persisting a map,
+ask the user to establish its project settings through `/acstack:setup`;
+do not create configuration implicitly. Invalid configuration or resolution
+errors require repair under Project configuration in `orchestrator/AGENTS.md`.
 `workflow.maps.tracker` in `<project folder>/project.yaml` (`github` or `files`) records
 the project's choice. If the key names a backend, read the matching doc and use
 its operations. If the key is absent, pick at materialisation time – the moment
@@ -34,8 +38,8 @@ Recommend `github` when the repo qualifies, `files` otherwise. Confirm the
 choice with the user. Then write the key, so later sessions need not re-decide.
 ## Which mode
 
-One command runs two modes, and what already exists picks between them. Check
-the configured tracker for existing maps – `ls "$(~/.claude/acstack/bin/acstack project-data path)/maps/"` on the files
+One command runs two modes, and what already exists picks between them. When
+a tracker is configured, check it for existing maps – `ls "$(~/.claude/acstack/bin/acstack project-data path)/maps/"` on the files
 backend, `gh label list --search "map:" --json name` on GitHub.
 
 If `$ARGUMENTS` names a map, or exactly one exists, work its frontier – the

package/skills/pre-commit-review/SKILL.md

@@ -59,14 +59,14 @@ git status --short
 git log --oneline -3  # recent context
 ```
 
-Read `<project folder>/project.yaml` to understand the project's directory layout, commands, and conventions. ACStack keeps it in the project folder, the path `~/.claude/acstack/bin/acstack project-data path` prints.
+Read `<project folder>/project.yaml` when present to understand directories, commands, and conventions. The project folder is the path `~/.claude/acstack/bin/acstack project-data path` prints. Without configuration, discover these from repository instructions, manifests, existing tests, and CI under Project configuration in `orchestrator/AGENTS.md`; do not require setup. Report resolution errors or invalid config rather than treating them as absent.
 
-Categorize changed files into scopes using the project configuration:
+Categorize changed files using configured or discovered directories:
 
-- **source**: files under `directories.source` from project.yaml
-- **frontend**: files under `frontend.directory` from project.yaml (if configured)
+- **source**: files under configured `directories.source`, or discovered source directories
+- **frontend**: files under configured `frontend.directory`, or discovered frontend directories
 - **config**: `*.yaml`, `*.toml`, `*.json`, config files, etc.
-- **tests**: files under `directories.tests` from project.yaml
+- **tests**: files under configured `directories.tests`, or discovered test directories
 - **other**: everything else
 
 Judge changes by effect, including behavior changed through config, assets, or shipped guidance.
@@ -85,7 +85,7 @@ Read `../../output-styles/ac-writing-style.md` relative to this skill directory;
 **Living specs and architecture:**
 
 ```
-Read the living specs relevant to this change:
+Read existing living specs relevant to this change; skip if none exist:
 - Check the <project folder>/specs/ directory listing
 - Read spec.md files for domains touched by the changed files
   (use <project folder>/domain-map.yaml to map files -> domains)

package/skills/quick-fix/SKILL.md

@@ -95,9 +95,11 @@ Apply the shared policy to the minimal fix.
 ## Step 6: Verify
 
 Use focused regression checks while fixing. One verification owner gathers the
-required final checks from `project.yaml` in the project folder, the path `~/.claude/acstack/bin/acstack project-data path` prints, under Build verification in
-`orchestrator/AGENTS.md`, reusing valid evidence rather than rerunning commands
-for every fix or handoff.
+required final checks under Build verification in `orchestrator/AGENTS.md`,
+using `project.yaml` when present or discovered repository tooling when absent.
+Follow its Project configuration policy for resolution errors and invalid config;
+do not require setup for a general fix. Reuse valid evidence rather than rerunning
+commands for every fix or handoff.
 
 Preserve configured frontend gates. Do not claim completion with failed or blocked
 required checks or unverified configured browser behavior.

package/skills/test-conventions/SKILL.md

@@ -7,7 +7,7 @@ description: Test placement rules and framework conventions. Invoke before writi
 
 ## Decision Tree: Where Does My Test Go?
 
-Read `<project folder>/project.yaml` for `directories.source`, `directories.tests`, and `frontend` config. The project folder is the path `~/.claude/acstack/bin/acstack project-data path` prints.
+Read `<project folder>/project.yaml` when present for `directories.source`, `directories.tests`, and `frontend`. The project folder is the path `~/.claude/acstack/bin/acstack project-data path` prints. Without config, follow repository instructions and existing tests for placement and runner commands; use the examples below only where they fit that project. Follow Project configuration in `orchestrator/AGENTS.md` for invalid config or resolution errors, not a silent fallback.
 
 ```
 Backend code?             → <tests-dir>/<mirror-source-path>/test_<module>.py
@@ -32,7 +32,7 @@ Mirror the source directory structure. Example: `src/auth/sessions.py` → `test
 Colocated with source. Example: `src/hooks/useAuth.ts` → `src/hooks/__tests__/useAuth.test.ts`.
 
 - Components: `.test.tsx`, pure functions: `.test.ts`
-- Run with `frontend.commands.test` from project.yaml
+- Run with configured `frontend.commands.test`, or the discovered repository test command
 
 ## Layer 3: E2E Tests (Browser)