fearovex/project-setup

project-setup

Deploys the complete SDD architecture with engram persistence and ai-context/ memory layer in the current project.

Triggers: /project-setup, initialize project, setup sdd, configure claude project, new sdd project

---

What this skill does

When the user runs /project-setup, I analyze the current project and generate:

1. CLAUDE.md at the project root with real detected context
2. ai-context/ with the 5 memory files initialized
3. Engram project context for the SDD cycle
4. Registry of relevant skills based on the detected stack

---

Process

Step 1 — Project detection

I read and analyze:

• package.json / pyproject.toml / go.mod / Cargo.toml / pom.xml
• Folder structure (src/, app/, lib/, tests/, etc.)
• Configuration files (tsconfig, eslint, prettier, etc.)
• README.md if it exists
• Existing docs folders
• .git/ to confirm it is a repository

I infer:

• Main language and version
• Framework(s) in use
• Database / ORM
• Testing tools
• Build / bundler tools
• Detected naming conventions (camelCase, snake_case, etc.)
• Folder structure (feature-based, layer-based, monorepo, etc.)

Step 2 — Generate project CLAUDE.md

I create CLAUDE.md at the root with these sections:

# [Project Name]

## Stack

[Detected stack with versions]

## Architecture

[Explained folder structure]
[Detected architectural pattern]

## Conventions

[Detected naming conventions]
[Observed code patterns]

## Important Commands

[Scripts from package.json / Makefile / etc.]

## Project Memory

At the start of each session, read the relevant files in ai-context/:

- ai-context/stack.md — Detailed technical stack
- ai-context/architecture.md — Architecture decisions
- ai-context/conventions.md — Team conventions
- ai-context/known-issues.md — Known bugs and gotchas
- ai-context/changelog-ai.md — AI change history

After completing significant work: update the relevant files or
run /memory-update so the AI updates them.

## Active Skills

[List of relevant skills for this project]

## SDD — Spec-Driven Development

This project uses SDD.
Entry points: `/sdd-explore <topic>` (investigate first) or `/sdd-propose <change-name>` (start from proposal).
Multi-phase flows are handled by the orchestrator as meta-commands — type them directly in conversation.
Phase skills: `/sdd-explore`, `/sdd-propose`, `/sdd-spec`, `/sdd-design`, `/sdd-tasks`, `/sdd-apply`, `/sdd-verify`, `/sdd-archive`.

Step 3 — Initialize ai-context/

I create the 5 files with real content based on what was detected:

ai-context/stack.md

# Technical Stack

Last updated: [date]

## Language

- [Language]: [version]

## Main Framework

- [Framework]: [version]
- [Relevant configuration details]

## Database / ORM

- [If applicable]

## Testing

- [Testing framework]
- [Commands to run tests]

## Build / Bundler

- [Tool]: [version]
- [Build command]
- [Dev command]

## Key Dependencies

| Package | Version   | Purpose        |
| ------- | --------- | -------------- |
| [name]  | [version] | [what it does] |

ai-context/architecture.md

# Project Architecture

Last updated: [date]

## Architectural Pattern

[Detected: feature-based / layer-based / clean architecture / etc.]

## Folder Structure

[Explained tree with the purpose of each folder]

## Architecture Decisions

| Decision | Choice | Alternatives | Reason |
| -------- | ------ | ------------ | ------ |

[Inferred from existing code]

## Data Flow

[Description of the main flow]

## Entry Points

[Main entry points of the system]

ai-context/conventions.md

# Project Conventions

Last updated: [date]

## Naming

- Files: [detected]
- Variables/Functions: [detected]
- Classes/Types: [detected]
- Constants: [detected]

## File Structure

[How files of each type are organized]

## Code Patterns

[Patterns detected in existing code]

## Git

[Commit conventions if detected]
[Branch strategy if detected]

## Testing

[Where tests live]
[Test naming conventions]

ai-context/known-issues.md

# Known Issues

Last updated: [date]

## Active Bugs

[Empty at start — filled during development]

## Gotchas and Limitations

[Anything unusual detected in existing code]

## Identified Technical Debt

[Problematic patterns detected]

## Workarounds in Use

[If there are workarounds in the code, document them here]

ai-context/changelog-ai.md

# AI Changelog

This file records significant changes made by Claude.

## Entry Format

### [YYYY-MM-DD] — [Change name]

**What was done**: [description]
**Modified files**: [list]
**Decisions made**: [relevant decisions]
**Notes**: [anything important]

---

[Entries are added here chronologically]

Step 4 — Persist project context to engram

Check if Engram MCP is reachable (call mem_context):

• If reachable: save project context to engram via mem_save with topic_key: sdd-init/{project-name}. Log INFO: Engram detected — project context persisted to engram.
• If not reachable: log WARNING: Engram not available — project context not persisted. SDD artifacts will be ephemeral.

Step 5 — Final report

I present to the user:

✅ Project configured: [name]

Detected stack:
  - [language + version]
  - [framework + version]
  - [testing framework]

Files created:
  - CLAUDE.md
  - ai-context/stack.md
  - ai-context/architecture.md
  - ai-context/conventions.md
  - ai-context/known-issues.md
  - ai-context/changelog-ai.md

Next steps:
  1. Review and adjust CLAUDE.md with details I could not detect
  2. To start a change: /sdd-explore <topic> or /sdd-propose <change-name>
  3. To create project-specific skills: /skill-create <name>

---

Rules

• NEVER overwrite existing files without warning and asking for confirmation
• If CLAUDE.md already exists, I offer an intelligent merge or creating a backup
• If ai-context/ already exists, I offer to update only what is missing
• I always read real code — I never invent the stack
• If I cannot determine something with certainty, I mark it as [To confirm]
• NEVER create a .claude/commands/ directory — commands/ is a legacy mechanism; .claude/skills/ is the only supported extensibility path for new projects.