Skip to content

CLAUDE.md

Latest commit

 

History

History
66 lines (48 loc) · 3.69 KB

CLAUDE.md

File metadata and controls

66 lines (48 loc) · 3.69 KB
Raw

Developer Guidelines

See docs/developer-guide.md for full directory structure, compilation pipeline, and conventions.

Directory Ownership

Role Working directory
Platform Developer src/{arch}/platform/
Runtime Developer src/{arch}/runtime/
Codegen Developer examples/

Common Commands

See docs/testing.md for the full testing guide (st, pyut, cpput) and docs/ci.md for CI pipeline details.

Python environment

This repo requires pip install . to run. Always use a project-local venv created with --system-site-packages — never install into the user/global site. Applies equally to git worktrees (create .venv inside the worktree). See .claude/rules/venv-isolation.md.

python3 -m venv --system-site-packages .venv
source .venv/bin/activate
pip install .

Format C++ code

clang-format -i <file>

Important Rules

  1. Consult .claude/rules/ for conventions and working rules (ascend, ci-change-detection, codestyle, comments, discipline, doc-consistency, env-macro-gating, known-issues-tracking, project-layout, running-onboard, venv-isolation) — these are always-loaded guidelines. Consult .claude/skills/ for task-specific workflows (e.g., git-commit/ when committing, testing/ when running tests)
  2. Do not modify directories outside your assigned area unless the user explicitly requests it
  3. Create new subdirectories under your assigned directory as needed
  4. When in doubt, ask the user before making changes to other areas
  5. Avoid including private information in documentation or code such as usernames, absolute paths with usernames, or other personally identifiable information. Use relative paths or generic placeholders instead

Substantial task delivery

Use .claude/skills/develop-task/SKILL.md for goal/design alignment, internal task dependencies, parallel agents and reviewed delivery. Small changes can use the focused skills directly.

GitHub work by role

Use maintainer to maintain a selected repository, Issue, track or personal work scope, optionally filtering PR target branches. It keeps an on-demand action table and brings concrete decisions to the user. Developers and committers can use it too; scope does not grant extra authority. It routes to the focused workflows below. Ongoing monitoring requires a verified wake mechanism; a requested single inspection does not start one.

  • Maintainer: process-issue for Issue triage, ownership and closure; process-pr for review routing, merge readiness and authorized merge/Issue follow-through.
  • Assignee: fix-issue, which selects direct repair or develop-task according to the work's complexity.
  • PR author: github-pr to publish and fix-pr for feedback and CI repairs.
  • Reviewer: review-pr for technical review.

Issues carry an accountable assignee; PRs carry their author and requested reviewers. These workflows share GitHub records, not a second task queue.