setup

Detect a repository's existing stack and record operational setup decisions.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill setup-supermalang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill setup-supermalang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a fresh or partially configured repository into a clear, runnable technical foundation by detecting what already exists, asking only for the missing decisions, and recording the stack setup in the project’s operational files.

Core Features & Use Cases

  • Stack detection: Reads manifests, lockfiles, and existing config to infer language, package manager, test runner, linting, framework, and coverage tooling.
  • Guided interview: Asks focused questions about project identity, isolation, absolute rules, commands, coverage policy, and optional forge or brand settings only when the repo cannot answer them.
  • Operational wiring: Populates the project’s stack context, command mappings, stack-profile patterns, scripts, and coverage configuration so downstream agents can work safely and consistently.
  • Greenfield guidance: Recommends a suitable stack when no implementation exists yet and records the user’s choice as a concise technical decision.

Quick Start

Ask me to configure the technical foundation for this repository and I will detect the stack, fill the missing settings, and prepare the project for discovery or planning.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a technical stack and operational foundation for a new repository?

To configure a technical stack, the setup process detects existing manifests and lockfiles to infer your package manager, test runner, and linting tools, then asks focused questions to fill any missing operational foundation settings.

What is the best way to set up project commands and coverage policy for an existing codebase?

Setting up project commands and coverage policy requires coherent mappings for thresholds and pattern targets. The configuration process reads existing project settings and records stack-specific wiring to ensure safe operation.

How do I select a stack and operational guardrails for a greenfield project?

For greenfield stack selection, the setup process recommends a suitable technical stack when no implementation exists yet, then records your choice as a concise technical decision to establish foundational guardrails.

Does the repository analysis process work with existing manifests and lockfiles?

Yes, repository analysis works with existing manifests, lockfiles, and config files to infer language, framework, and coverage tooling. It only initiates a guided interview for missing isolation rules or stack configuration details.

Why do downstream agents need stack context and isolation rules configured before operating?

Downstream agents require stack context, command mappings, and isolation rules configured beforehand to ensure they can work safely and consistently within the established operational foundation of the repository.

What stack configuration details are required before setting up project foundation scripts?

Stack configuration requires coherent mappings for the project's commands, thresholds, context files, and pattern targets before foundation scripts and coverage configuration can be safely populated for downstream agents.