Repository Guidelines
Use Node.js 18 or newer and install dependencies with `pnpm` (enforced by `preinstall`). Run `pnpm install` from the repo root to link workspace packages and set up local post-install patches via `tw-patch`.
Explore
4,988 skills indexed with the new KISS metadata standard.
Use Node.js 18 or newer and install dependencies with `pnpm` (enforced by `preinstall`). Run `pnpm install` from the repo root to link workspace packages and set up local post-install patches via `tw-patch`.
This is the **root AGENTS.md** containing universal guidelines that apply to the entire codebase. Each module can have its own `AGENTS.md` that inherits these principles and adds module-specific conventions.
- dont be detailed n readme, just put concise minimal instruction, this app is for me only
- `src/`: API and domain code
These instructions apply to the entire repository.
- **Run all tests**: `python run_tests.py`
Проект разделён на агентов, каждый из которых отвечает за свой слой:
- **Write production-quality code**: All code must be robust, efficient, and ready for use in real-world systems.
Source code lives under `src/aw_import_ical/`, with the primary entry point in `cli.py` and the package exposed via `python -m aw_import_ical` or the `aw-import-ical` console script. Supporting utilities such as virtualenv helpers and lint scripts reside in `scripts/`. Documentation belongs in `docs
You are an expert-level AI Software Development Agent. Your sole purpose is to contribute to a Python project by strictly following a Test-Driven Development (TDD) methodology. You are methodical, precise, and prioritize code quality and testing above all else. You think step-by-step and always vali
- Ensure the working directory is clean with `git status`.
This repository contains many ebuilds and workflows that are generated automatically using [arrans_overlay_workflow_builder](https://github.com/arran4/arrans_overlay_workflow_builder). When updating packages:
This guide explains how to work effectively inside the RISKEN AWS codebase. Follow these practices to keep builds green and releases predictable.
- Frontend (routes/): cd routes && pnpm dev, pnpm build, pnpm typecheck
Core source lives in `src/` with submodules for `ast`, `compiler`, `runtime`, and `utilities`; tooling entry points sit in `src/tools/`. Public headers live in `include/sif/`, and integration assets land in `src/tests/resources/`. Docs and sample scripts are under `docs/` and `examples/`, while buil
- Respeitar as **Regras do Projeto** (sem deps externas; VS2022/Win11 x64/CUDA 13; implementações completas; comentários PT‑BR; pacote + manifesto a cada entrega).
- `grammar.js`, `src/`, and `binding.gyp` contain the Tree-sitter grammar plus generated artifacts (`src/parser.c`, `src/node-types.json`). Regenerate via the CLI rather than editing generated files directly.
This file provides guidance to AI agents when working with code in this repository.
- **Repository scope:** Reusable Bicep service template. Provides the complete pipeline and test scaffolding shared by service repos so new projects start from a working baseline.
- 给出当前的 step 打分方案并写入根目录下的专门 Markdown 文件,文件需使用简体中文并辅以数学符号与伪代码描述。
This file provides guidance to Agents when working with code in this repository.
Next.js App Router drives the app. Routes live in `app/` (e.g. `app/events`, `app/signin`, `app/signup`) with shared layout in `app/layout.tsx` and global styles in `app/globals.css`. Reusable UI sits in `components/`; `components/ui` holds Radix/Tailwind primitives and `*-client.tsx` wrappers handl
Accelerate delivery of West‑Africa‑first WordPress plugins and tooling by generating secure, performant, offline‑capable code and documentation that conforms to Starisian standards.
- **Code is for humans.** Write your code with clarity and empathy—assume a