Skip to content

Quick Start

This guide will have you up and running with Cortex TMS in under 5 minutes.

  • Node.js 18+ installed
  • A project directory (new or existing)
  • (Optional) Claude Code or GitHub Copilot for AI assistance
  1. Install Cortex TMS

    Choose your preferred installation method:

    Terminal window
    npm install -g cortex-tms@latest
  2. Initialize your project

    Navigate to your project directory and run:

    Terminal window
    cd your-project
    cortex init
    # Or: cortex-tms init (both commands work identically)

    You’ll be prompted to choose:

    • Project type: Basic, Full, or Custom
    • Features: ADRs, Patterns, Glossary, etc.
  3. Review generated files

    Cortex TMS creates this structure:

    • Directoryyour-project/
      • CLAUDE.md AI agent instructions
      • NEXT-TASKS.md Current objectives
      • CHANGELOG.md Version history
      • Directorydocs/
        • Directorycore/
          • PATTERNS.md Code conventions
          • GLOSSARY.md Terminology
        • Directoryadr/
          • 0001-example-adr.md
      • Directory.github/
        • copilot-instructions.md
  4. Customize for your project

    Open CLAUDE.md and update:

    • Role: Your AI assistant’s persona
    • CLI Commands: Add your test/build commands
    • Operational Loop: Modify the workflow if needed

    Example customization:

    ## 💻 CLI Commands
    - **Test**: `npm test` or `pytest`
    - **Lint**: `npm run lint`
    - **Build**: `npm run build`
  5. Test with Claude Code (if installed)

    Open your project in Claude Code:

    Terminal window
    claude-code your-project

    Claude will automatically read CLAUDE.md and follow your instructions!

    Try asking: “What’s the current task?” — Claude will read NEXT-TASKS.md.

Run the validation command to ensure everything is configured correctly:

Terminal window
cortex validate --strict
# Or: cortex-tms validate --strict

You should see:

✓ CLAUDE.md exists and is valid
✓ NEXT-TASKS.md exists and is well-formed
✓ All ADRs follow naming convention
✓ No dead links in documentation
Project health: EXCELLENT

Edit NEXT-TASKS.md to add your first real task:

## Current Objective
Implement user authentication using JWT tokens.
**Why**: We need secure API access for the mobile app.
**Acceptance Criteria**:
- [ ] JWT token generation on login
- [ ] Token validation middleware
- [ ] Refresh token rotation
- [ ] Tests for auth flow

When you make an architectural decision, document it:

Terminal window
cortex adr new "Use PostgreSQL for user data storage"

This creates docs/adr/0002-use-postgresql-for-user-data-storage.md with a template.

Edit docs/core/PATTERNS.md to add conventions:

## File Naming
- React components: `PascalCase.tsx`
- Utility functions: `camelCase.ts`
- Test files: `*.test.ts`

Claude Code reads CLAUDE.md automatically. Just open your project:

Terminal window
claude-code .

Happy scaffolding! 🚀