👋 New contributors: start here #1237

Welcome! This issue stays pinned so the first thing you see is how to find something you can actually do.

Two workflows, one sentence each

• DARC (Document / Assess / Research / Code) drives one feature — an operator, a metric, a kernel. A feature is one parent issue (tracking darc) plus small, skill-labelled sub-issues you can claim on their own.
• SKEEP records one architectural decision — public API, DSL, storage, runtime/compiler integration, compatibility — as a numbered proposal under docs/modules/skeep/, coordinated through a skeep tracking issue.

Find a task (every one names the file to copy from and the exact Gradle task to run):

• 🟣 All open good first issues
• ⏱️ Under an hour · a few hours
• 🧠 By what you already know, no SKaiNET knowledge assumed: Kotlin · PyTorch / NumPy, no Kotlin · Android · iOS · JS / Wasm · Kotlin/Native · writing docs
• 🗺️ The big picture: open DARC features · open SKEEP proposals

Claim it: comment on the sub-issue; a maintainer assigns it. Branch from develop, keep the PR to that one sub-issue, link it with Closes #NNN.

Read more: Getting started as a contributor · Issue taxonomy (labels & title prefixes) · Worked example: F1Score via DARC · a live example feature: #1222

Questions? Ask right here in the comments.