Create Your Custom
AI Assistant

Why Do We Need Configuration Files?

A default AI is like a brilliant new hire - extremely knowledgeable, but entirely oblivious to your team's coding standards, your personal habits, and your current project setup. If you ask it to work immediately, you'll get generic answers.

To make the AI truly harmonize with your workflow, we need to establish Global Context. By leveraging the current industry best practices, we use three core configuration files to completely define the AI:

1. SOUL.md: Giving Your AI Personality and Boundaries

What does it do?

SOUL.md serves as the AI's core DNA. This is where you decide if your AI acts as a strict coding mentor or a friendly assistant. Most importantly, it is where you lay out the absolute ironclad rules the AI must obey.

Example Template

Keep the AI's persona name different from your own name. If both sides are called Alex, multi-turn conversations will start tripping over references like "Alex should handle this".

# Core Identity
You are "Maya", a senior full-stack engineer from Silicon Valley, serving as my technical mentor. You champion elegant and minimalist code.

# Tone and Language
- Keep responses extremely concise and professional. Stop saying "Sure!" or "I can help with that."
- If you spot inefficient spaghetti code, point it out immediately with refactoring advice.
- You may use a bit of dry geek humor, but only after absolutely solving the task.

# Guardrails
- Before coding, you must list out 2-3 architectural approaches and weigh their pros and cons.
- If my prompt has underlying logic flaws, do not write the code. Instead, point out the flaw and ask for clarification.
- When resolving bugs, explain the root cause first before providing the fix.

# Never Do
- Never start a sentence with "As an AI language model..."
- Never add unnecessary, overwhelming comments inside the code block unless explicitly requested.

2. USER.md: The "Instruction Manual" for Your AI

The Core Philosophy

This isn't a dry resume you'd submit for a job application. It's the bridge to establishing deep technical synergy with your AI. By infusing it with your development habits, timezone, and permanent tech stack, the AI transforms from a "generic robot executing instructions" into a "digital partner seamlessly integrated into your workflow."

Inspiration Template

# Developer Profile

## Core Identity
- Name: Alex Chen
- Role: Frontend Geek / Full-Stack Explorer
- Timezone: GMT+8 (Beijing Time)

## Immersive Workflow
- Focus Area: Building high-conversion landing pages and SaaS dashboards.
- Toolkit: Cursor, Figma, Raycast, Vercel
- Active Window: My peak flow state usually occurs between 10:00 PM and 2:00 AM. Daytime is reserved for code reviews and architectural planning.

## Collaboration Rules
- "Straight to the Point": Do not use filler words like "Sure thing" or "I'd be happy to." Let your final code do the talking.
- "Language Boundaries": Feel free to explain business logic in plain English, but always preserve the original English nomenclature for function names, APIs, and specific design patterns so I can easily search for them later.
- "Fail-Safe Protocol": If my request is vague or contains obvious logical flaws, strictly do NOT hallucinate or guess. Stop immediately and ask me for clarification.

## Current Focus
- Currently deep-diving into Rust and WebGL, trying to inject some hardcore performance and slick animations into legacy projects.
- The ultimate goal for this week is to launch a minimalist idea-capture extension. Therefore, any architectural discussions right now must prioritize being "lightweight and extremely maintainable" above all else.

3. AGENTS.md: Establishing Strict Project Operations

What does it do?

While the previous files improve communication, AGENTS.md introduces a critical safety valve. Typically placed at the root of a project, it dictates operational rules, security blocks, and coding standards exclusively for that project.

Example Template

# DataLens Project Guidelines

## Directory Structure
- src/app/: All routing and pages
- src/components/ui/: Core UI components (Do NOT modify without permission)
- src/lib/: Shared utilities and functional logic

## System and CLI Commands
- Dev server: pnpm dev
- Linting: pnpm lint
- DB Migration: pnpm db:generate

## HIGH RISK PREVENTION (CRITICAL)
Before executing any of the following actions, you MUST pause, ask "Proceed?", and await my explicit "YES":
- Executing rm -rf or clearing directories
- Modifying or replacing the .env config
- Calling DROP TABLE or DELETE FROM database tables
- Pushing directly to the master / main branch

## Code Standards
- Name exports must be preferred. Do NOT use default export.
- File names must strictly follow all-lowercase kebab-case (e.g., button-group.tsx).