setup

Configure Praxis by auto-detecting stack and generating CLAUDE.md and ARCHITECTURE.md.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Angel1104/praxis-core --skill setup-angel1104
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/Angel1104/praxis-core/tree/main/skills/setup
Command: npx skills add https://github.com/Angel1104/praxis-core --skill setup-angel1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures the Praxis skills pack for an existing project, scanning the codebase to detect the stack and project size, and writes CLAUDE.md and ARCHITECTURE.md so all lifecycle skills have full context without re-scanning on every CR. Works with any language, framework, or project type.

Core Features & Use Cases

  • Auto-detects stack and project size.
  • Writes CLAUDE.md and ARCHITECTURE.md to centralize context for all lifecycle skills.
  • Eliminates re-scans on every CR by storing context in architecture artifacts.

Quick Start

Run /setup on your repository to auto-detect the stack and generate architecture context.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I auto-detect my project stack and generate architecture documentation?

You can auto-detect stack and project size by running /setup on your repository, which scans the codebase and generates architecture context files without manual configuration.

How do I stop scanning my codebase on every code review?

To stop re-scanning on every code review, generate centralized context files like CLAUDE.md and ARCHITECTURE.md once, storing the environment, gates, and source layout for lifecycle skills.

Does project configuration work with any programming language and framework?

Yes, project configuration works across any language, framework, or project type, detecting the stack and applying settings universally to support all lifecycle skills.

What is the best way to centralize project context for lifecycle skills?

The best way to centralize project context is writing CLAUDE.md and ARCHITECTURE.md files, capturing test commands, environment details, and source layout to provide full context.

What specific details does a codebase scan capture for project setup?

A codebase scan captures the project stack, project size, environment variables, gates, test commands, and source layout, writing these details into context files.

Why do I need architecture artifacts for my existing repository?

You need architecture artifacts to provide full context to all lifecycle skills, eliminating redundant scans and ensuring environment and source layout details persist across code reviews.