Skip to main content

Apply Path (Tier 1 Quick Start)

Use this page when you want to apply the Tier 1 Quick Start implementation immediately with the least setup overhead.

This is the execution-first companion to:

When to Use This Path

Choose Tier 1 apply if you need:

  • a greenfield starter repository with built-in guardrails
  • a small-team pilot this week
  • baseline PRD-STD controls (001, 002, 003, 004, 008)
  • a fast path before broader transformation planning

If you already have a mature repository and only want selective files, use Standalone Config Packs instead.

Quick Apply Checklist (30-90 Minutes)

1. Clone the Quick Start Repo

git clone https://github.com/AEEF-AI/aeef-quickstart.git my-project
cd my-project

2. Choose Your Language Baseline

3. Run Local Setup and Smoke Validation

Run the setup script and then execute the language-specific lint/test commands from your selected guide.

Goal: prove the starter works before customizing anything.

4. Configure Your AI Tool Rules

Verify your team is using the provided project configs (for example):

  • .cursorrules
  • .github/copilot-instructions.md
  • .claude/settings.json
  • .windsurfrules

These establish prompt and review hygiene on Day 1.

5. Enable PR Workflow Guardrails

Confirm:

  • PR template is active
  • branch protection is enabled (at least one review)
  • CI checks run on every PR

6. Make One Real AI-Assisted Change

Use a low-risk change to validate the workflow end-to-end:

  • prompt
  • code change
  • tests
  • security/lint checks
  • PR review

Use Your First AI-Governed PR if your team needs a guided rehearsal.

Brownfield Variant (Selective Apply)

If you want Tier 1 controls without adopting the template repo shape:

  1. Start with Config Packs
  2. Apply AI tool configs (Day 1)
  3. Apply CI pipeline starter (Week 1)
  4. Add branch protection and PR metadata fields
  5. Run a Level 1 standards gap check against Production Standards

Exit Criteria (Tier 1 Applied)

Tier 1 is effectively applied when you can show:

  • AI tool rules/configs are active in the repo
  • CI runs test + security/dependency checks on PRs
  • human review is required before merge
  • AI-assisted PRs produce consistent metadata and review evidence

What to Do Next