setup

Configure the Praxis skills pack by detecting project stack and writing CLAUDE.md and ARCHITECTURE.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures the Praxis skills pack for an existing project by scanning the codebase, detecting the stack and project size automatically, asking proportional questions, and writing ARCHITECTURE.md so all lifecycle skills have full context without re-scanning on every CR. It works with any language, framework, or project type.

Core Features & Use Cases

  • Automatic stack and size detection to tailor the setup
  • Generation of CLAUDE.md and ARCHITECTURE.md to preserve lifecycle context
  • Scopes across existing projects to enable consistent readiness for CRs

Quick Start

Run /setup on an existing project to auto-detect its stack and generate CLAUDE.md and ARCHITECTURE.md.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I configure an existing codebase for automated project lifecycle management?

To configure an existing codebase, you can run a setup process that scans your project, detects the stack, and writes configuration files like CLAUDE.md and ARCHITECTURE.md for lifecycle context. This prevents re-scanning on future code reviews.

How does project stack detection work for auto-configuring an existing codebase?

Project stack detection works by scanning the codebase to identify languages, frameworks, and project size automatically. It then asks proportional questions to tailor the setup and generate architecture artifacts without manual input.

What's the best way to preserve architecture context for future code reviews?

The best way to preserve context is by generating CLAUDE.md and ARCHITECTURE.md files during setup. This ensures all lifecycle skills have full project context without needing to re-scan the codebase on every code review.

Do I need to manually specify my project framework to generate architecture artifacts?

No, you do not need to manually specify your framework. The setup process auto-detects the project stack and size, asks proportional questions, and coordinates the workflow to generate architecture artifacts automatically.

Why does my project configuration require scanning the codebase before writing architecture files?

Scanning the codebase is required to accurately detect the project stack and size. This initial scan writes the necessary architecture files so downstream lifecycle skills have full context without repetitive scanning.