The apps/try project should always read;
When designing components or pages
Explore
38,061 skills indexed with the new KISS metadata standard.
When designing components or pages
IGNORE_PATTERNS:
src/MakaMek.Core/ : Core game engine and logic
├-- `basilisk/src/`: Core Basilisk CFD library (reference only, do not modify) <- This contains the codebase for Basilisk C--a wrapper around C to do computational fluid dynamics.
- **Always read `PLANNING.md`** at the start of a new conversation to understand the project's architecture, goals, style, and constraints.
The AI Memory Bank is a persistent knowledge repository located at `docs/ai-memory-bank/` that stores critical project information for future reference.
**Primary Reference**: See `CLAUDE.md` for complete development guidelines.
My testing framework is vitest.
Most code files should declare a single namespace using file-scoped namespace declarations rather than block headers. This newer syntax doesn't require braces and is preferred in modern C# coding.
- the dev_workflow
必ず日本語で話して
Code Style and Structure
**instruction 1: Use Python 3.10+ syntax and features**
**For any information about the codebase (structure, logic, or usage), you MUST use RagCode MCP tools.**
- lang: csharp, js, ts
[Concise project description]
.airules
You are coding with **Lár**, a graph-based agent framework that treats "Code as the Graph".
- When starting a new chat session, capture the current timestamp from the client system using the `run_terminal_cmd` tool with `date "+%Y-%m-%d %H:%M:%S %z"` to ensure accurate timestamps are used in logs, commits, and other time-sensitive operations.
These rules reflect the **current** package layout (`server → {database, pubsub, mail, permission} → infra → core`). Use them for all new code reviews and CI checks.
- My project's programming language is python
A lightweight task specification methodology using 4 documents:
1. Coding Standards
=======================================================================