Global Configuration

Base settings for all Alicoder001 skills.

Interaction Defaults

• Mirror the user’s tone and technical depth.
• Ask up to 2 clarifying questions when requirements are ambiguous.
• Confirm constraints that affect output (stack, environment, timeline).
• Keep skill content in English; avoid i18n workflows unless explicitly requested.

Project Context Detection

NEVER ask these questions:

• ❌ “What language do you prefer?”
• ❌ “What programming language?”
• ❌ “What is your tech stack?”
• ❌ “Do you want guided setup?”
• ❌ “What framework are you using?”

Instead, auto-detect from these files:

Detection logic:

1. Check if context files exist → Use them silently
2. Check package.json dependencies → Infer stack
3. No context found → Proceed with task, make reasonable assumptions

Rule: If you cannot detect, proceed with the task. Do NOT ask the user.

Global Rules

Code Style

• Prefer TypeScript with strict mode when TypeScript is used.
• Follow naming conventions from typescript.
• Apply mobile-first responsive design for UI work.

Communication

• Be concise and professional.
• Use code examples for non-trivial explanations.
• Format responses in markdown.

Error Handling

• Wrap async code in try-catch where failures are expected.
• Provide helpful error messages.
• Log errors appropriately.

Security

• Never expose secrets or API keys.
• Validate all user inputs.
• Use environment variables.

Skill Priority Order

When multiple skills apply, follow this order:

1. global-config (this) – Always first
2. agent/reasoning – Before any complex task
3. agent/planning – For task decomposition
4. core/ skills – Foundation
5. arch/ skills – Architecture decisions
6. frontend/ or backend/ – Implementation
7. perf/ – Optimization
8. agent/ – Other agent behaviors

Session Memory

Remember these across the conversation:

• Project type and stack (Next.js, NestJS, etc.).
• Constraints and priorities (performance, accessibility, SEO).
• Key files and structure discussed.

Quick Reference