Skip to Content

Projects

Create a project, give CodeLynq the context it needs about your code, and let it fill that context in from your repository.

A project groups the tasks, repositories and settings that belong to one product or codebase. Everything CodeLynq writes for a project - specs and code - is shaped by the project's context.

Create a project

  1. Go to Projects and click New Project (or use New Project on the Dashboard).
  2. Choose what you are starting from:
    • An existing codebase - connect a repository; CodeLynq reads your conventions and works within them.
    • Something new - answer a few questions, make the architectural calls, and CodeLynq builds it into an empty repository. See Start a new application.
  3. Enter a Project name and a Description, then click Create Project.

You are taken to the project's settings: Repositories for an existing codebase, Build from scratch for something new. Any member of the organization can create a project, within the number of projects your plan allows. Whoever creates a project becomes its owner.

Inside a project

A project has these tabs:

  • Tasks - the project's tasks, with New Task for a quick task. See Tasks.
  • Backlog - AI-assisted prioritization of open tasks. See Backlog grooming.
  • Epics - larger goals split into tasks. See Epics.
  • Delivered - what the project shipped in the last 7, 30 or 90 days, and what it cost.
  • Notes - meeting notes turned into tasks. See Meeting notes.
  • Settings - everything below.

Settings is divided into two groups:

Changing project settings requires being an organization admin or the project's owner.

Context & conventions

This context is given to the AI whenever it writes a spec or code for this project. The more specific it is, the better the results fit your codebase.

  • Architecture Principles - the patterns and structure the project follows.
  • Coding Conventions - naming, code style, patterns to follow or avoid.
  • Testing Strategy - which tests you expect, and how they are run.
  • Domain Knowledge - business context and terminology.
  • Constraints - technical limits, compliance requirements, things that must not change.

Below these fields you find the Verification gate and the other checks every run goes through. See Quality gates.

Click Save Settings to save your changes.

Fill it in from your repository

You do not have to write the context from scratch. Once a repository is connected:

  1. Under Fill this in from your repository, click Analyse repository. CodeLynq reads your manifests, configuration and README (Reading repository…).
  2. A Proposed from your repository panel appears with a confidence level, the files it was based on, the detected tech stack and proposed text for architecture, conventions, testing, constraints and the verify command.
  3. Click Use this to copy the proposal into the fields, or Discard to ignore it.
  4. Review and adjust the fields, then click Save Settings. Nothing is saved before that.

Delete a project

At the bottom of Context & conventions, under Delete this project, type the project name and click Delete project. This removes the project and everything in it - tasks, epics, runs, specs, connected repositories and everything CodeLynq has learned about the codebase. Your repositories in your git host are not touched. This cannot be undone.

Test it on a task from your own backlog

Send us one real task. We run CodeLynq on your repository and you review the pull request. Free, within 5 working days of approving the spec.