### Interactive GitHub App Setup for Claude

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

This bash command initiates an interactive setup process for integrating the Claude GitHub App into a local repository. It guides the user through installation and secret configuration.

```bash
cd /path/to/your/repo
claude

> /install-github-app
[Follow prompts to install app and configure secrets]
```

--------------------------------

### Starting Claude Code CLI

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Demonstrates how to launch the Claude Code CLI from different directories and with various flags to customize its behavior, such as setting permission modes or specifying the model.

```bash
# From any directory (not recommended)
claude

# From project directory (recommended)
cd /path/to/your/project
claude

# With specific flags
claude --permission-mode acceptEdits
claude --model opus
claude -p "What does this project do?"  # Print mode (non-interactive)
```

--------------------------------

### Install Dependencies and Start Server

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/04_dev_env/02_github/readme.md

Commands to install project dependencies and start the development server. Assumes Node.js and npm are installed.

```bash
npm install
npm start
```

--------------------------------

### Example Workflow: Ticket-Driven Development

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Illustrates a typical workflow using MCP for ticket-driven development, starting from authentication, viewing tickets, explaining requirements, implementing, updating, and creating a pull request.

```bash
> /mcp
[Authenticate with Linear]

> show me all my assigned tickets
> explain the requirements for LINEAR-123
> implement the feature described in LINEAR-123
> update LINEAR-123 with implementation notes
> create a PR linked to LINEAR-123
```

--------------------------------

### Example Workflow: Design Implementation

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Shows a workflow for implementing UI designs using MCP, involving authentication with Figma, retrieving designs, implementing based on a design frame, and comparing the implementation to the design.

```bash
> /mcp
[Authenticate with Figma]

> show me the designs for the user profile page
> implement the design from @figma:frame://abc123
> compare my implementation to @figma:frame://abc123
```

--------------------------------

### Codex CLI Setup and Help

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/03_codex/readme.md

This snippet demonstrates the initial setup and verification for the Codex CLI. It involves installing the CLI, authenticating, and checking the help command to ensure proper installation and access.

```bash
codex --help
```

--------------------------------

### Native Installation Script for Claude Code

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Installs Claude Code using a shell script. This is the recommended method for macOS, Linux, and WSL. It fetches the latest version of the installation script and executes it.

```bash
curl -fsSL https://claude.ai/install.sh | bash
```

--------------------------------

### Project-Level MCP Configuration File (.mcp.json)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Provides an example of the `.mcp.json` file used for project-scoped MCP server configurations. It defines commands, arguments, and environment variables for services like Linear and Postgres.

```json
{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["-y", "@linear/mcp-server"],
      "env": {
        "LINEAR_API_KEY": "${LINEAR_API_KEY}"
      }
    },
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "POSTGRES_URL": "${POSTGRES_URL}"
      }
    }
  }
}
```

--------------------------------

### Install Qwen Code CLI

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/01_big_free_tiers/02_qwen_code/01_hello_qwen/README.md

Installs the Qwen Code CLI globally using npm and verifies the installation by checking the version and help output.

```bash
npm install -g @qwen-code@latest

qwen --version
# verify
qwen --help
```

--------------------------------

### Example: Create and Verify Project Setup (Python)

Source: https://context7.com/panaversity/spec-kit-plus/llms.txt

Demonstrates a complete workflow: checking tools, initializing a project, and verifying its directory structure. This example utilizes `check_tools`, `init_project`, and Python's `Path` for file system checks. It ensures the project is set up correctly.

```python
if __name__ == "__main__":
    # Check tools first
    tools = check_tools()
    print("Available tools:", tools["stdout"])

    # Initialize project with Claude Code
    project_name = "my-sdd-project"
    result = init_project(project_name, ai_agent="claude")
    print(f"Project {project_name} initialized")

    # Verify project structure
    project_path = Path(project_name)
    expected_dirs = [".specify", "memory", "templates"]
    for dir_name in expected_dirs:
        assert (project_path / dir_name).exists(), f"Missing: {dir_name}"

    print("Project structure verified successfully")
```

--------------------------------

### Verify Claude Code Installation

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Commands to check the health of your Claude Code installation and to start the Claude Code interactive terminal session. Ensure you are in your project directory before starting.

```bash
# Check installation health
claude doctor

# Start Claude Code
cd /path/to/your/project
claude
```

--------------------------------

### Run Development Server

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/06_core_commands/07_implementation/readme.md

Start the local development server to run the application. This allows for manual interaction and visual inspection of the implemented feature in a browser.

```bash
npm run dev
```

--------------------------------

### Context Engineering: Adding to Project Memory

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Syntax for quickly adding information to the CLAUDE.md file. Lines starting with '#' are appended, allowing for rapid updates to project context.

```markdown
# Always ask before committing to GitHub
```

--------------------------------

### Initialize Project with AI Agent (Bash)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/spec-driven-development-analysis.md

Demonstrates how to initialize a new project using Spec Kit and specify an AI agent. It also shows how to initialize in an existing directory and check detected tools. These commands are essential for setting up the development environment.

```bash
# Initialize new project with Spec Kit
specify init my-project --ai claude

# Or in existing directory
specify init . --ai gemini --force

# Check detected tools
specify --check-tools
```

--------------------------------

### Project Structure for Claude Code

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Illustrates a recommended project directory structure for use with Claude Code, including locations for project memory, configuration files, custom agents, commands, output styles, hooks, and source code.

```bash
my-project/
├── CLAUDE.md                   # Project memory (created by `init`)
├── .claude/
│   ├── agents/                 # Custom subagents
│   ├── commands/               # Custom slash commands
│   ├── output-styles/          # Custom output styles
│   ├── hooks/                  # Custom hooks
│   └── settings.local.json     # Local settings
├── .mcp.json                   # MCP server config (team-shared)
├── src/                        # Your code
├── tests/                      # Your tests
└── docs/                       # Documentation
```

--------------------------------

### Simple Git Commit with Claude

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Example of how to create a simple Git commit using Claude. Claude analyzes the changes and automatically writes conventional commits based on the provided message.

```shell
> commit my changes with a descriptive message
```

--------------------------------

### Project Hook Example: Format TypeScript Files

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

A project-level hook configuration for 'PostToolUse' events. It targets 'Write' tool usage, checks for TypeScript files, and formats them using prettier.

```json
{
  "PostToolUse": [
    {
      "matchers": ["Write"],
      "hooks": [
        {
          "command": "prettier --write $(jq -r '.tool_input.path')"
        }
      ]
    }
  ]
}
```

--------------------------------

### Install and Initialize Spec Kit Plus (Bash)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/spec-driven-development-analysis.md

This snippet shows how to install the Spec Kit using pip and initialize a new pilot project. It specifies the AI model to be used for the project. The `specify init` command sets up the basic structure for a new project, and the `--ai` flag allows selection of a compatible AI.

```bash
# Install Spec Kit
pip install specify

# Initialize pilot project
specify init pilot-project --ai claude

# Configure constitution
# Edit memory/constitution.md with org standards
```

--------------------------------

### Project Hook Example: Block Production File Writes

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

A project-level hook configuration. It intercepts 'Write' tool usage, checks if the path targets 'src/production/', and exits with an error if it does, preventing modification.

```json
{
  "PreToolUse": [
    {
      "matchers": ["Write"],
      "hooks": [
        {
          "command": "jq -r '.tool_input.path' | grep -q 'src/production/' && echo 'Cannot modify production files' && exit 1"
        }
      ]
    }
  ]
}
```

--------------------------------

### Using MCP Tools Directly

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Demonstrates how Claude can automatically leverage installed MCP tools based on natural language requests, such as creating issues, searching Slack, or querying databases.

```bash
> create a Linear issue for this bug
> search Slack for conversations about the Q4 roadmap
> query the database for user signup trends
> update the Jira ticket with these findings
> send a message to #engineering channel
```

--------------------------------

### README.md Content

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/01_big_free_tiers/02_qwen_code/01_hello_qwen/prompts/0001-init-project.prompt.md

A standard README file for the 'hello-world-qwen' project. It typically includes a project description, installation instructions, usage examples, and contribution guidelines.

```markdown
# hello-world-qwen

This is a sample Python project initialized with uv, demonstrating a colorful 'Hello, World!' application.

## Features

- Initializes project with uv.
- Uses the `rich` library for colorful terminal output.
- Includes pytest for testing.
- Configured with pre-commit hooks (black, flake8) for code quality.

## Installation

1. Clone the repository:
   ```bash
   git clone <repository-url>
   cd hello-world-qwen
   ```
2. Install dependencies:
   ```bash
   uv install
   ```
3. Install pre-commit hooks:
   ```bash
   pre-commit install
   ```

## Usage

Run the main script:

```bash
python main.py
```

The application will prompt you to enter your name and then display a personalized greeting.

## Testing

Run tests using pytest:

```bash
pytest
```

## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details.
```

--------------------------------

### Backend Setup Instructions (Bash)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/03_natural_language_programming/markdown-tutorial-for-developers.md

Commands to set up the Python backend environment. This includes creating a virtual environment, activating it, and installing dependencies from requirements files. It assumes the user is in the 'backend' directory.

```bash
cd backend
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -r requirements.txt
pip install -r requirements-dev.txt  # Development dependencies
```

--------------------------------

### PreToolUse Hook Example: Log Bash Command Path

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

A user-level hook configuration in JSON format. It specifies a 'PreToolUse' event, matches the 'Bash' tool, and executes a jq command to log the tool's input command to a file.

```json
{
  "PreToolUse": [
    {
      "matchers": ["Bash"],
      "hooks": [
        {
          "command": "jq -r '.tool_input.command' >> ~/.claude/bash-log.txt"
        }
      ]
    }
  ]
}
```

--------------------------------

### Managing MCP Servers (List, Remove, Import)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Details commands for managing installed MCP servers: listing them, removing specific servers, and importing configurations from Claude Desktop.

```bash
# List installed servers:
claude mcp list

# Remove server:
claude mcp remove server-name

# Import from Claude Desktop:
claude mcp import-from-claude-desktop
[Select which servers to import]
[Choose scope: user or project]
```

--------------------------------

### Example GitHub Actions Workflow for Claude

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

This YAML file defines a GitHub Actions workflow that triggers on issue comments, pull request review comments, and issue openings. It checks if the Claude bot is mentioned and then runs the Claude Code action to process the request.

```yaml
name: Claude Code

on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  issues:
    types: [opened]

jobs:
  claude:
    runs-on: ubuntu-latest
    if: contains(github.event.comment.body, '@claude') || github.event_name == 'issues'
    
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0  # Full history for better context
      
      - name: Run Claude Code
        uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
          github_token: ${{ secrets.GITHUB_TOKEN }}
```

--------------------------------

### Install SpecifyPlus CLI

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/06_core_commands/00_setup/readme.md

Installs the SpecifyPlus CLI tool. It can be installed persistently from PyPI or using uv tools. An alternative one-off installation method using uvx is also provided.

```bash
pip install specifyplus
```

```bash
uv tool install specifyplus
```

```bash
uvx specifyplus --help
```

```bash
uvx specifyplus init <PROJECT_NAME>
```

```bash
uvx sp init <PROJECT_NAME>
```

--------------------------------

### Configure Context7 MCP Server

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/04_dev_env/05_ai_pair_programming/readme.md

A prompt to guide the setup of Context7 MCP server integration with Qwen Code. It specifies that Context7 should provide documentation for UV, pytest, and Git, and requests step-by-step instructions and execution for the user's platform.

```text
Help me set up Context7 MCP server integration with Qwen Code.
Context7 should provide access to documentation for:
- UV (Python package manager)
- pytest (testing framework)
- Git (version control)

Provide step-by-step instructions for my platform and execute them.
```

--------------------------------

### Install Pre-commit Hooks

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/01_big_free_tiers/02_qwen_code/01_hello_qwen/prompts/0001-init-project.prompt.md

Installs the pre-commit hooks for the 'hello-world-qwen' project. This command configures the project to run specified tools (like black and flake8) automatically before each commit.

```bash
cd hello-world-qwen && pre-commit install
```

--------------------------------

### Schedule Daily Security Scan with Cron

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

This example shows how to configure a cron job to run a daily security scan using the Claude CLI. The job is scheduled for 2 AM daily and executes a security audit command, saving the JSON output to a dated log file.

```bash
# crontab -e
# Run security scan daily at 2 AM
0 2 * * * cd /path/to/project && /usr/local/bin/claude -p "Run security audit on all code. Report any vulnerabilities." --output-format json > /var/log/claude-security-$(date +%Y%m%d).json
```

--------------------------------

### Add MCP Server with Environment Variables

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Demonstrates adding an MCP server (ClickUp in this case) using environment variables for sensitive information like API keys and team IDs. It utilizes npx for execution.

```bash
claude mcp add clickup \
  --env CLICKUP_API_KEY=your_key \
  --env CLICKUP_TEAM_ID=your_id \
  -- npx -y @hauptsache.net/clickup-mcp
```

--------------------------------

### Install Specific Version of Claude Code (macOS/Linux)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Installs a specific version of Claude Code on macOS or Linux systems using the native installation script. Replace '1.0.58' with the desired version number.

```bash
curl -fsSL https://claude.ai/install.sh | bash -s 1.0.58
```

--------------------------------

### Frontend Setup Instructions (Bash)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/03_natural_language_programming/markdown-tutorial-for-developers.md

Command to install Node.js dependencies for the React frontend. This is typically run after navigating to the 'frontend' directory.

```bash
cd frontend
npm install
```

--------------------------------

### Native Installation Script for Claude Code on Windows

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Installs Claude Code using a PowerShell script. This method is suitable for Windows users, including those using WSL. It downloads and executes the installation script.

```powershell
irm https://claude.ai/install.ps1 | iex
```

--------------------------------

### Executing Claude Commands with File Context and Output Redirection

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Demonstrates how to execute Claude commands with specific file contexts and redirecting output to a file. This is useful for tasks like explaining code within a project or generating documentation.

```bash
# With file context
cd /path/to/project
claude -p "Explain the authentication flow"

# Output to file
claude -p "Generate API documentation" > docs/api.md
```

--------------------------------

### Database Setup and Migration (Bash)

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/03_natural_language_programming/markdown-tutorial-for-developers.md

Instructions for setting up and managing the PostgreSQL database. This involves starting the database using Docker Compose, running Alembic migrations to update the schema, and optionally seeding test data.

```bash
# Start PostgreSQL via Docker
docker-compose up -d postgres

# Run migrations
cd backend
alembic upgrade head

# Seed test data (optional)
python scripts/seed_db.py
```

--------------------------------

### Install Zed IDE on Linux

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/04_dev_env/03_zed/readme.md

Installs the Zed IDE on Linux systems by downloading and executing the official installation script. This method is suitable for most Linux distributions.

```bash
# Download and install Zed
curl -f https://zed.dev/install.sh | sh
```

--------------------------------

### Querying Files with Claude Code

Source: https://github.com/panaversity/spec-kit-plus/blob/main/docs-plus/01a_ai_cli/02_paid_professional/01_claude_code/readme.md

Demonstrates various methods for querying files and code within a project using Claude Code, including automatic file discovery, specific questions about code functionality, and referencing files directly using the '@' symbol.

```bash
# Automatic file discovery:
> what does this project do?

# Specific questions:
> what files handle authentication?
> explain how the API routing works
> show me where database migrations are defined

# File references with @:
> explain @src/auth/login.ts
> compare @src/api/v1.ts and @src/api/v2.ts
> review @src/components/ for best practices
```