Archeon Project Configuration

Configure Aider to work with projects using the Archeon glyph notation system, which enforces structured documentation through file headers, section markers, and synchronized indexing.

What This Skill Does

This skill configures Aider to:

Instructions

Follow these steps when working in an Archeon project:

1. **Load Required Context Files**

- Always include these files in your context:

- `archeon/ARCHEON.arcon` (main feature specification)

- `archeon/ARCHEON.index.json` (file and section index)

- `archeon/templates/_config/ai-rules.md` (complete notation rules)

- `.archeonrc` (project configuration)

2. **Read Before Writing**

- ALWAYS read `archeon/ARCHEON.arcon` before generating any code

- If a feature doesn't exist in ARCHEON.arcon, write a new chain definition there FIRST

3. **File Header Requirements**

- EVERY file MUST have `@archeon:file` headers at the top containing:

- `@glyph` - unique identifier for the file

- `@intent` - description of the file's purpose

- `@chain` - the feature chain this file belongs to

4. **Section Markers**

- EVERY file MUST use `@archeon:section` and `@archeon:endsection` markers to delimit logical code sections

- Each section should have a clear purpose and glyph identifier

5. **Index Synchronization**

- ALWAYS update `archeon/ARCHEON.index.json` when:

- Creating new files

- Adding new sections to existing files

- Modifying file glyphs or chains

- The index MUST stay in sync with the actual code structure

6. **Validation**

- After implementation, run `arc validate` to verify:

- All headers are present and correctly formatted

- All sections are properly marked

- The index matches the actual file structure

7. **Commit Review**

- Auto-commits are disabled by default

- Review all changes to ensure Archeon compliance before committing

- Verify headers, sections, and index updates are correct

Example File Structure

```javascript

// @archeon:file

// @glyph: components/UserProfile

// @intent: Display user profile information with avatar and bio

// @chain: user-management

// @archeon:section:imports

// @glyph: components/UserProfile/imports

import React from 'react';

import { Avatar } from './Avatar';

// @archeon:endsection

// @archeon:section:component

// @glyph: components/UserProfile/component

export const UserProfile = ({ user }) => {

return (

<div className="profile">

<Avatar src={user.avatar} />

<h2>{user.name}</h2>

<p>{user.bio}</p>

</div>

);

};

// @archeon:endsection

```

Aider Configuration

Create a `.aider.conf.yml` file in your project root:

```yaml

read:

- archeon/ARCHEON.arcon

- archeon/ARCHEON.index.json

- archeon/templates/_config/ai-rules.md

- .archeonrc

auto-commits: false

model-settings-yaml: |

extra_params:

system: |

This project uses Archeon glyph notation.

Read archeon/templates/_config/ai-rules.md for the complete rules.

Key rules:

- Always read archeon/ARCHEON.arcon before generating code

- If a feature doesn't exist, write a new chain to ARCHEON.arcon first

- EVERY file MUST have @archeon:file headers at top with @glyph, @intent, @chain

- EVERY file MUST use @archeon:section / @archeon:endsection markers

- ALWAYS update archeon/ARCHEON.index.json when creating files or adding sections

- The index MUST stay in sync with the code

- Run arc validate after implementation

```

Important Notes